Re: Editing the Java memory Heap space (805 Views)
Reply
Regular Advisor
Posts: 111
Registered: ‎12-27-2008
Message 1 of 8 (869 Views)

Editing the Java memory Heap space

Hi All,

Am getting the error In topaz.all.ejb.log

[RMI TCP Connection(50615)-3.122.210.189] (JVMSHRemoteMonitor.java:99) ERROR - failed to invoke remote monitoring.
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.OutOfMemoryError: Java heap space
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)


can somebody help me to edit the from the JMXconsole.

Regards,
Ashish

Honored Contributor
Posts: 557
Registered: ‎12-10-2008
Message 2 of 8 (869 Views)

Re: Editing the Java memory Heap space

What is the configuration of the Server running BAC (amount of memory, architecture, processor type)?
Also, could you tell whether other heavy products are running on the same box?
Honored Contributor
Posts: 1,300
Registered: ‎01-12-2009
Message 3 of 8 (869 Views)

Re: Editing the Java memory Heap space

Can you upload the db_loader.log and wde.log files?

--Regards
--Mario
Valued Contributor
Posts: 54
Registered: ‎01-21-2009
Message 4 of 8 (869 Views)

Re: Editing the Java memory Heap space

I would first check which process pot the OutOfMemoryError.
If you are using system health then check the process memory monitors.
If you are not using system health then check the jvm_statistics.log under each process and check the free memory.
Regular Advisor
Posts: 111
Registered: ‎12-27-2008
Message 5 of 8 (869 Views)

Re: Editing the Java memory Heap space

I cleared the jboss cache and it fixed the issue
Respected Contributor
Posts: 503
Registered: ‎09-01-2009
Message 6 of 8 (833 Views)

Re: Editing the Java memory Heap space

HOw did yoiu clear the cache?

Valued Contributor
Posts: 36
Registered: ‎05-02-2012
Message 7 of 8 (822 Views)

Re: Editing the Java memory Heap space

Hi,

It was not the JBOSS that fixed your problem, but the fact you restarted the BSM services in order to clean the cache. When you restart them, the JVM for the problematic service is reset as well. This means all of the allocated memory it had in your system RAM, will be released. So next time you start BSM, the problematic service will start over with clean space. Of course this will work until next time it reaches its limit, for whatever reason. Then you will experience the OOM again, when same conditions that triggerred it at first place are met.

Quite often the reason is simply related to the fact the system was not properly sized/configured. The error that you saw:
...
[RMI TCP Connection(50615)-3.122.210.189] (JVMSHRemoteMonitor.java:99) ERROR - failed to invoke remote monitoring.
java.rmi.ServerError: Error occurred in server thread; nested exception is:
java.lang.OutOfMemoryError: Java heap space
at sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:322)
...
is basically giving us nothing. You either need to provide the full topaz log file or give us additional information about the system - are you noticing interface problems, some features maybe don't work, data is not coming to BSM etc.

 

 

BR,
Stanislav

Frequent Advisor
Posts: 62
Registered: ‎01-06-2010
Message 8 of 8 (805 Views)

Re: Editing the Java memory Heap space

Don't forget jvm_statistics.log under each process log directory, It gives an idea how heap and GC memory is consumed by that process. Each process has an *.ini file under bin directory that indicate required Heap/GC when the process starts and that is adjustable depending on your sizing calculations ..

 

hth\tarif

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.