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 :
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.