New to Java

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

report; thread deadlocked; 3 threads behaviors; please help

807597Apr 29 2005 — edited Sep 27 2007

Hi,
We had a problem where we got OEM (out of mem) error. Before i restarted the server, i took the thread and then did some analysis and came down to these threads behaviors which in my opinion looks weired.

All i wanted to know ...are these threads in deadlock situation ?

FIRST THREAD DUMP ANALYSIS STARTS HERE ---

"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=000935f8 nid=47 lwp_id=862293 runnable [0x6305a000..0x6305a4f0]
	at weblogic.socket.PosixSocketMuxer.poll(Native Method)
	at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:100)
	- locked <689ad370> (a java.lang.String)
	at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=00093490 nid=46 lwp_id=862292 waiting for monitor entry [0x630db000..0x630db4f0]
	at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:93)
	- waiting to lock <689ad370> (a java.lang.String)
	at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=00093328 nid=45 lwp_id=862291 waiting for monitor entry [0x6315c000..0x6315c4f0]
	at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:93)
	- waiting to lock <689ad370> (a java.lang.String)
	at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)


SECOND THREAD DUMP ANALYSIS STARTS HERE ---

"ExecuteThread: '2' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=000935f8 nid=47 lwp_id=862293 waiting for monitor entry [0x6305a000..0x6305a4f0]
	at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:93)
	- waiting to lock <689ad370> (a java.lang.String)
	at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

"ExecuteThread: '1' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=00093490 nid=46 lwp_id=862292 waiting for monitor entry [0x630db000..0x630db4f0]
	at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:93)
	- waiting to lock <689ad370> (a java.lang.String)
	at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

"ExecuteThread: '0' for queue: 'weblogic.socket.Muxer'" daemon prio=10 tid=00093328 nid=45 lwp_id=862291 runnable [0x6315c000..0x6315c4f0]
	at weblogic.socket.PosixSocketMuxer.poll(Native Method)
	at weblogic.socket.PosixSocketMuxer.processSockets(PosixSocketMuxer.java:100)
	- locked <689ad370> (a java.lang.String)
	at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:32)
	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:219)
	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:178)

thanks for your help, sangita

Locked Post

New comments cannot be posted to this locked post.

Locked on Oct 25 2007

Added on Apr 29 2005

9 comments

234 views