25 Jan 2013
January 25, 2013

Some essential WebSphere Errors and what to do.

January 25, 2013 Blog, Errors 0 Comment

A few WebSphere Error Messages and Redial Actions

Message
Log
Message meaning
Severity
Remedial Actions
WTRN0048W: An attempt by the transaction manager to call commit on a transactional resource has resulted in an XAER_RMFAIL error. The resource was com.ibm.ws.Transaction.JTS.WSCoordinatorWrapper@78337833 SystemOut.log It may mean no transactions can be committed 1 This may mean the WebSphere tranlogs need clearing down.
Java.lang.OutOfMemoryError SystemOut.log The JVM has run out of memory. The contents of process memory will be written to disk as a heapdump, and the JVM will be restarted. Users connected to this JVM will be disconnected. 1 The heap is being exhausted. This could be because the heap size is set too low and increasing the heap will fix this. It could also be indicative of a more serious issue such as a memory leak or over allocation of objects in the application code.
HMGR0152W: CPU Starvation detected. Current thread scheduling delay is 9 seconds. SystemOut.log CPU starvation can be due to many issues. See the IBM Website for more details: http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg21236327 1
ThreadMonitor W WSVR0605W: Thread “WebContainer : 113” (000001ad) has been active for 607311 milliseconds and may be hung. There is/are 1 thread(s) in total in the server that may be hung.
Monitor: ThreadMonitor W WSVR0605W.*milliseconds and
SystemOut.log Threads in the JVM are in a hung state. This may be due to slow/hung external calls, threads locked due to a deadlock or resource contention. 2 Determine why the threads are hung. This may clear spontaneously without any remedial action or may require a clone (JVM)  restart
Facebooktwittergoogle_plusredditpinterestlinkedinmail

Leave a Reply