How to Monitor OutOfMemory exceptions in WebSphere logs

Some Java Application badely coded, hungs  due to full usage of java heap space in WebSphere and needs to be restarted every night to work good without OutOfMemory Errors.

So to monitor this exception we can do two things :

1-By parsing the SystemOut.log and SystemErr.log in our WebSphere searching for this reference code :

SRVE0014E

example :

[7/4/16 16:18:21:326 WET] 00000135 ServletWrappe E com.ibm.ws.webcontainer.servlet.ServletWrapper service SRVE0014E: Uncaught service() exception root cause /servelet.jsp: com.ibm.websphere.servlet.error.ServletErrorReport: java.lang.OutOfMemoryError: Java heap space

SRVE0232E

example :

[7/4/16 16:18:19:318 WET] 0000018e WebContainer  E com.ibm.ws.webcontainer.internal.WebContainer handleRequest SRVE0232E: Internal Server Error. <br> Exception Message: [java.lang.OutOfMemoryError: Java heap space

SRVE0293E

[7/4/16 16:18:16:094 WET] 0000013d webapp        E com.ibm.ws.webcontainer.webapp.WebApp logServletError SRVE0293E: [Servlet Error]-[GenericServletWrapper]: java.lang.OutOfMemoryError: Java heap space

2-By using IBM Tivoli Monitoring with ITCAM for WebSphere agent :

this can be done by defining new situation with heap size conditions

I can give more details and explanation if you send me email support@it-sysoft.com

 

Be the first to comment

Leave a Reply

Votre adresse de messagerie ne sera pas publiée.


*