HP SIM 6.3 - Java Memory Errors

[shocko]

Hi all,

After some uptime I get the following error whilst trying to log onto SIM

"An error occurred connecting to the HP Systems Insight Manager server: java.lang.NullPointerExceptionClick here to go to the sign-in page."

See attached for screen cap. I have to restart the SIM service in order to get the system up and running again. System details below:

HP Proliant BL25p G2, 12 GB RAM

Windows 2008 SE x64 SP2

[Marcus Svensson]

Hi,

I also receive this message after SIM has been running a while. What can you read out from the mxdomainmgr log? This log is located under Instalation directory \HP\System Insight Manager\logs.

How much memory and CPU is mxdomainmgr.exe consume?

How many servers are you monitoring?

I have tried to increse the java heap size but i has not resolved this issue.

Br

[shocko]

I'm monitoring about 700 systems so nothing very heavy. It seems like a memory leak to be honest

[Marcus Svensson]

Hi,

I have the same problem but i have not been able to solve it yet.

At the same time as java.lang.NullPointerException occurs I recive a heap dump log under System Insight Manager\log.

The things i have tried is:

1, increasing the java heap

2, Extended the time intervall for scheduled polling task

3, Reduced the number of "old and minor events", had more than 20 000 events.

I monitor about 4500 items with HP SIM and running SIM on a windows 2008 R2 server with 28 GRAM and the database is remote SQL.

Check how much memory mxdomainmgr.exe is consuming when you recive the java.lang.NullPointerException next time.

[shocko]

Support have advised me to increase the heap size also but my feeling is this is a leak and will only manifests itself again after a longer period of time. I'll keep this thread update with the results in case anyone else has the same problem.

[shocko · Accepted solution]

FYI guys,
The setting i added was the 'JVMMAXHEAP=2048' in the configuration file 'globalsettings.props'. I have enough RAM on my SIM server to able to do this. It seems to have sloved the issue so far.