[esb-issues] [JBoss JIRA] Commented: (JBESB-1247) DB Listener does not include reconnect logic

Tom Cunningham (JIRA) jira-events at lists.jboss.org
Wed Oct 24 15:41:02 EDT 2007


    [ http://jira.jboss.com/jira/browse/JBESB-1247?page=comments#action_12384213 ] 
            
Tom Cunningham commented on JBESB-1247:
---------------------------------------

Kevin C says in the duplicate bug filed : 
"The fix shouldn't be in the listener though, it needs to be in JdbcCleanConn."

See JBESB-1245 for more details.

> DB Listener does not include reconnect logic
> --------------------------------------------
>
>                 Key: JBESB-1247
>                 URL: http://jira.jboss.com/jira/browse/JBESB-1247
>             Project: JBoss ESB
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 4.2 Milestone Release 3
>            Reporter: David Boeren
>         Assigned To: Mark Little
>            Priority: Minor
>
> What's happening is that the DB Listener seems to be getting stuck and no longer picking up new database entries.  If the appserver is bounced then it resumes normal functioning.
> There's a big string of these errors in the log:
> 2007-10-24 00:56:43,882 DEBUG [org.jboss.soa.esb.helpers.persist.JdbcCleanConn] execQueryWait() FAILED
> COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0108E  Communication link failure. SQLSTATE=40003
>    at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:254)
>    at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:418)
>    at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:396)
>    at COM.ibm.db2.jdbc.net.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java:1068)
>    at org.jboss.soa.esb.helpers.persist.JdbcCleanConn.execQueryWait(JdbcCleanConn.java:138)
>    at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.pollForCandidates(SqlTableGatewayListener.java:447)
>    at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doRun(SqlTableGatewayListener.java:149)
>    at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
>    at java.lang.Thread.run(Thread.java:595)
> 2007-10-24 00:56:43,882 DEBUG [org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener] Some triggers might not have been returned
> COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] CLI0108E  Communication link failure. SQLSTATE=40003
>    at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.throw_SQLException(SQLExceptionGenerator.java:254)
>    at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:418)
>    at COM.ibm.db2.jdbc.net.SQLExceptionGenerator.check_return_code(SQLExceptionGenerator.java:396)
>    at COM.ibm.db2.jdbc.net.DB2PreparedStatement.executeQuery(DB2PreparedStatement.java:1068)
>    at org.jboss.soa.esb.helpers.persist.JdbcCleanConn.execQueryWait(JdbcCleanConn.java:138)
>    at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.pollForCandidates(SqlTableGatewayListener.java:447)
>    at org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener.doRun(SqlTableGatewayListener.java:149)
>    at org.jboss.soa.esb.listeners.lifecycle.AbstractThreadedManagedLifecycle.run(AbstractThreadedManagedLifecycle.java:115)
>    at java.lang.Thread.run(Thread.java:595)
> 2007-10-24 00:56:43,882 DEBUG [org.jboss.soa.esb.listeners.gateway.SqlTableGatewayListener] Returning 0 rows.
> Looks like the DB connection has gone down, and the code does not contain any reconnect logic so at that point it fails.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the esb-issues mailing list