Stuck Thread attribute on WLS8.1 sp2

Question

There is long process that requires a DB connection to be open for 2-3 hours. But currently we have the Stuck Thread Time Out set to '7200' seconds. Will Weblogic kill a thread if that thread is designated as Stuck??? (the backend is a Sybase server we had no issue with the DB at the point)
Given below is an excerpt from the server.log file
<Sep 22, 2004 5:43:27 PM EDT> <Warning> <WebLogicServer> <BEA-000337> <ExecuteTh
read: '22' for queue: 'weblogic.kernel.Default' has been busy for "8,290" second
s working on the request "connection15.session24", which is more than the config
ured time (StuckThreadMaxTime) of "7,200" seconds.>
<Sep 22, 2004 7:43:27 PM EDT> <Warning> <WebLogicServer> <BEA-000337> <ExecuteTh
read: '22' for queue: 'weblogic.kernel.Default' has been busy for "15,490" second
s working on the request "connection15.session24", which is more than the config
ured time (StuckThreadMaxTime) of "7,200" seconds.>
####<Sep 22, 2004 9:13:19 PM EDT> <Error> <JDBC> <HOSTNAME> <SERVERNAME
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-001112> <Test "SELECT COUNT(*) FROM sysobjects" set up for pool "CRS_TDS_CONN
_POOL" failed with exception: "java.sql.SQLException: JZ0C0: Connection is alrea
dy closed.".>

Answer 1

Arvind Varma wrote:
There is long process that requires a DB connection to be open for 2-3 hours.> But currently we have the Stuck Thread Time Out set to '7200' seconds. Will
> Weblogic kill a thread if that thread is designated as Stuck??? (the backend
> is a Sybase server we had no issue with the DB at the point)
No, it's just a warning, I believe. There should be no problem with
jdbc connections staying open indefinitely, unless there's a firewall
that kills sockets after a time, or the DBMS kills idle connections
after a time. From the log below, it sounds like the pool just tested
a connection before giving it to your app, and found it was dead, and
presumably replaced it and gave you a new one. Was there any appplication
error?
Joe
PS: show me your pool definition. Your test table should not be sysobjects.
That is a huge system table. That's like testing your phone by calling 411
and asking the operator to count all the listings in the phone book for you! ;)
Joe
Given below is an excerpt from the server.log file
<Sep 22, 2004 5:43:27 PM EDT> <Warning> <WebLogicServer> <BEA-000337> <ExecuteTh
read: '22' for queue: 'weblogic.kernel.Default' has been busy for "8,290" second
s working on the request "connection15.session24", which is more than the config
ured time (StuckThreadMaxTime) of "7,200" seconds.>
<Sep 22, 2004 7:43:27 PM EDT> <Warning> <WebLogicServer> <BEA-000337> <ExecuteTh
read: '22' for queue: 'weblogic.kernel.Default' has been busy for "15,490" second
s working on the request "connection15.session24", which is more than the config
ured time (StuckThreadMaxTime) of "7,200" seconds.>
####<Sep 22, 2004 9:13:19 PM EDT> <Error> <JDBC> <HOSTNAME> <SERVERNAME
<ExecuteThread: '22' for queue: 'weblogic.kernel.Default'> <<anonymous>> <> <BEA-001112> <Test "SELECT COUNT(*) FROM sysobjects" set up for pool "CRS_TDS_CONN
_POOL" failed with exception: "java.sql.SQLException: JZ0C0: Connection is alrea
dy closed.".>