Server Retries after StuckThreadMaxTime reached

Question

Hello,
Having this flow :
PS HTTP @ ALSB 2.6.1 @ WLS 9.2 ----> JPD @ WLI 8.1 @ WLS 8.1 --> ServiceProvider
And when the service provider takes between 7 and 8 minutes to answer, we are having a :
+####<08-ene-2013 15H54' ART> <Error> <WebLogicServer> <webloguat> <TPBUSAPP2> <weblogic.health.CoreHealthMonitor> <<WLS Kernel>> <> <BEA-000337> <ExecuteThread: '47' for queue: 'weblogic.kernel.Default' has been busy for "428" seconds working on the request "Http Request: /processVENTAS/tp/processes/sync/solicitud/ActivarOfertaDSA.jpd", which is more than the configured time (StuckThreadMaxTime) of "300" seconds.>+
Which is expected.
But what is not expected, is having a Retry of the JPD exactly after 300 seconds the 1st execution started, with the same message :
+[INFO] [08 ene 2013 15:42:04] [ActivarOfertaDSA_wf]: [description: Inicio de JPD [tp.processes.sync.solicitud.ActivarOfertaDSA_wf@8ad983] - Timestamp = [1357670524427]],+
+[serverName: TPBUSAPP1, consumerCode: WEBVAS, serviceCode: 20002, messageId: 311403781, conversationId: 311403781, userId: x000108],+
+[INFO] [08 ene 2013 15:47:06] [ActivarOfertaDSA_wf]: [description: Inicio de JPD [tp.processes.sync.solicitud.ActivarOfertaDSA_wf@c5c834] - Timestamp = [1357670826448]],+
+[serverName: TPBUSAPP2, consumerCode: WEBVAS, serviceCode: 20002, messageId: 311403781, conversationId: 311403781, userId: x000108],+
Another fun fact, is that the 2nds execution starts before the 1st finishes (The service provider is taking more than 300 secs to reply).
Why is it retrying?.
The 300 seconds difference has anything to do with the StuckThreadMaxTime (Which is set to 300 seconds) ?
Thanks in advance!!
Edited by: Mario Mesaglio on Jan 9, 2013 12:14 PM

Answer 1

Any thread which takes longer than StuckThreadMaxTime will be printed on logs. If you have configured StuckThreadMaxTime as 300 and a specific thread stays forever on thread pool, you will have it printed on jvm log files every 300secs. A thread only gets out of thread pool in two cases. 1- it completes all tasks it have to do, 2-jvm is restarted.
Thats why you can setup actions a jvm can take after a Stuck Thread. One of the actions is shutdown the jvm and set it as FAILED.
Kinds,
Gabriel Abelha