1833780 Members
2627 Online
110063 Solutions
New Discussion

Re: PROCESS DYING

 
nagendra_3
Advisor

PROCESS DYING

Hi,

One of the Process ( Java ) id dying with out any message. When i saw the syslog.log i found the following message

"Java out of memory messages are marked with pid:12068 in /var/adm/syslog/syslog.log."

Feb 28 19:23:19 hpat982 syslog: pid: 12068 TYPE AVAIL USED FREE USED LIMIT RESERVE PRI FILE NAME
Feb 28 19:23:19 hpat982 syslog: pid: 12068 dev 131072 0 131072 0.00% 0 - 1 64 (major) 2 (minor)
Feb 28 19:23:19 hpat982 syslog: pid: 12068 reserve - 452344 -452344
Feb 28 19:23:19 hpat982 syslog: pid: 12068 memory 3297061 1276803 2020258 38.73%

Suspecting this to be an Issue with the JVM(JAVA) We have upgraded to the Latest HP-UX JVM. Increased the MAXDSIZ kernal parameter to 512MB.

Can you please help in this regard, as to why our PROCESS is dying ( getting killed abruptly )

Tks,
Nag
Knowledge is Power
3 REPLIES 3
Sundar_7
Honored Contributor

Re: PROCESS DYING


I can only take a wild guess. Are the processes dying soon after they are started ?. How about downloading tusc and see where it exactly fails ?
Learn What to do ,How to do and more importantly When to do ?
RAC_1
Honored Contributor

Re: PROCESS DYING

Post swapinfo -mat.

Also look at glance -m and vmstat 5 5 output. check how much free memeory you have?
Starting JVM with large heap sizes will also cause this. You can control initial heap size and such other parameters on JVM command line. Set these to reasonable value.

You can start JVM with tusc and see, where it is failing.

Anil
There is no substitute to HARDWORK
Jeff Schussele
Honored Contributor

Re: PROCESS DYING

Nag,

ALL processes *must* be able to reserve a "table" in the "swap reservation" restaurant.
IF they can't - they won't be allowed to run.
Check swapinfo -tam & CHECK the reservation area.

Rgds,
Jeff
PERSEVERANCE -- Remember, whatever does not kill you only makes you stronger!