StuckThreadMaxTime

Shuangxi Xu

unread,

Feb 13, 2004, 2:22:29 PM2/13/04

to

Hi,

We are currently deploying web services on weblogic 8.1. I have seen the "StuckThreadMaxTime"
Error very often, when all the threads got stuck, the server was like "dead".

The sample thread dump shows below:

--------------------
<Feb 12, 2004 3:42:05 PM PST> <Warning> <WebLogicServer> <BEA-000337> <ExecuteThread:
'24' for queue: 'weblogic.kernel.Default' has been busy for "671" seconds working
on the request "weblogic.iiop.MuxableSocketIIOP$1@6f8d74", which is more than
the configured time (StuckThreadMaxTime) of "600" seconds.>
............

"ExecuteThread: '24' for queue: 'weblogic.kernel.Default'" daemon prio=5 tid=0x602e38
nid=0x24 in Object.wait() [e8d01000..e8d01994]
at java.lang.Object.wait(Native Method)
- waiting on <f235bba0> (a weblogic.iiop.RequestMessage)
at java.lang.Object.wait(Object.java:426)
at weblogic.iiop.SequencedRequestMessage.waitForData(SequencedRequestMessage.java:30)
- locked <f235bba0> (a weblogic.iiop.RequestMessage)
at weblogic.iiop.EndPointImpl.sendReceive(EndPointImpl.java:1129)
at weblogic.iiop.EndPointImpl.sendReceive(EndPointImpl.java:1142)
at weblogic.corba.idl.RemoteDelegateImpl.invoke(RemoteDelegateImpl.java:350)
at weblogic.corba.idl.RemoteDelegateImpl.invoke(RemoteDelegateImpl.java:310)
at weblogic.corba.idl.RemoteDelegateImpl.non_existent(RemoteDelegateImpl.java:150)
at org.omg.CORBA.portable.ObjectImpl._non_existent(ObjectImpl.java:137)
at weblogic.iiop.MuxableSocketIIOP$1.execute(MuxableSocketIIOP.java:741)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:197)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:170)
....

Do you know how to solve the problem?

thanks,
shuangxi xu

Andy Piper

unread,

Feb 13, 2004, 7:23:04 PM2/13/04

to

"Shuangxi Xu" <shua...@yahoo.com> writes:

Can you provide more details?

andy

--

Andy Piper

unread,

Feb 17, 2004, 12:20:17 PM2/17/04

to

"Shuangxi Xu" <shua...@yahoo.com> writes:

So something is not right here. You say you are using WebServices but
the error below is for IIOP. Are you using the thin client
(wlclient.jar) in your swing client? It may well be JMS related

andy

> We have swing client interact with web services deployed on weblogic 8.1. Atached
> is the config.xml file.
>
> We configured two JMS topics, one is used to between weblogic server and swing
> client, the other one is used between server side code and a message driven bean
> (deployed on the
> same server).
>
> The message:

>
> ExecuteThread: '24' for queue: 'weblogic.kernel.Default' has been busy for "671"

> seconds working on the request "weblogic.iiop.MuxableSocketIIOP$1@6f8d74"...
>
> seems to occur after the server runs for a while. We are not sure what triggered
> it. Is this
> JMS related?
>
> Any help would be appreciated.

--

Shuba Simha

unread,

Apr 21, 2004, 8:24:42 AM4/21/04

to

Hi,
I have a very similar problem with 'StuckThreadMaxTime'. The server runs fine for sometime (say 4-5 days) and then starts throwing exceptions like:
<Apr 20, 2004 7:43:28 AM EDT> <Warning> <WebLogicServer> <000337>
> <ExecuteThread: '21' for queue: 'default' has been busy for "657"

> seconds working on the request

> "com.merck.mrl.common.userprofile.UserProfileBean_i3u13i_EOImpl",

> which is more than the configured time (StuckThreadMaxTime) of "600"

> seconds.> <Apr 20, 2004 7:43:28 AM EDT> <Warning> <WebLogicServer>
> <000337>
> <ExecuteThread: '27' for queue: 'default' has been busy for "872" seconds
> working on the request "Http Request: /cdmp/login.do", which is more than

> the configured time (StuckThreadMaxTime) of "600" seconds.>

> <Apr 20, 2004 7:43:28 AM EDT> <Warning> <WebLogicServer> <000337>
> <ExecuteThread: '34' for queue: 'default' has been busy for "869" seconds
> working on the request
> "com.merck.mrl.common.security.AuthenticatorBean_p08bse_EOImpl", which is

> more than the configured time (StuckThreadMaxTime) of "600" seconds.>

Were you able to find the solution to your problem?

Thanks.
Shuba