[jboss-user] [JBoss Messaging] - Bridge Status inconsistent when JDBC Connections are recreat

rogerdudler do-not-reply at jboss.com
Wed Dec 5 05:27:28 EST 2007


We are using JBoss Messaging 1.4.0.GA on JBoss 4.0.5 with all the prerequisites needed by JBoss Messaging. Everything works fine, except some issues on the messaging bridge, when the underlying database connections became invalid.

The source destination of the bridge is located on a remote messaging server (also JBoss Messaging 1.4.0.GA, but on JBoss 4.2.2.GA) and the destination exists locally.

If a JDBC connection becomes invalid (in the following example, during the  messaging reaper is running) and the pool creates a new one and the reaper updates properly, but after this, it seems that the Messaging Bridge has an inconsistent state. JMX Console shows that bridge is "Started", but it does not consume the remote queue anymore. After invoking "stop" and "start" on the bridge (JMX Console), the bridge begins to work as expected.

Any ideas?


  | 
  | .... before, there are connections which are unavailable, while reaper is running...
  | 
  | <->:<anonym>: 2007-12-05 09:23:33,937 [Timer-3] WARN  jboss.messaging.core.impl.JDBCSupport - SQLException caught, SQLState null code:0- assuming deadlock detected, try:22
  | org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1035, SQLSTATE: 57019, SQLERRMC: null); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1035, SQLSTATE: 57019, SQLERRMC: null))
  | 	at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:94)
  | 	at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner.execute(JDBCSupport.java:383)
  | 	at org.jboss.messaging.core.impl.JDBCSupport$JDBCTxRunner.executeWithRetry(JDBCSupport.java:407)
  | 	at org.jboss.messaging.core.impl.JDBCPersistenceManager.reapUnreferencedMessages(JDBCPersistenceManager.java:2357)
  | 	at org.jboss.messaging.core.impl.JDBCPersistenceManager.access$1000(JDBCPersistenceManager.java:78)
  | 	at org.jboss.messaging.core.impl.JDBCPersistenceManager$Reaper.run(JDBCPersistenceManager.java:2381)
  | 	at java.util.TimerThread.mainLoop(Timer.java:512)
  | 	at java.util.TimerThread.run(Timer.java:462)
  | Caused by: org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1035, SQLSTATE: 57019, SQLERRMC: null)
  | 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:179)
  | 	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.createConnectionEventListener(InternalManagedConnectionPool.java:565)
  | 	at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:250)
  | 	at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:529)
  | 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:341)
  | 	at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:301)
  | 	at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:396)
  | 	at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:842)
  | 	at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:88)
  | 	... 7 more
  | Caused by: com.ibm.db2.jcc.c.SqlException: DB2 SQL error: SQLCODE: -1035, SQLSTATE: 57019, SQLERRMC: null
  | 	at com.ibm.db2.jcc.c.p.a(p.java:3493)
  | 	at com.ibm.db2.jcc.b.hb.q(hb.java:709)
  | 	at com.ibm.db2.jcc.b.hb.p(hb.java:583)
  | 	at com.ibm.db2.jcc.b.hb.l(hb.java:408)
  | 	at com.ibm.db2.jcc.b.hb.d(hb.java:147)
  | 	at com.ibm.db2.jcc.b.b.cc(b.java:1418)
  | 	at com.ibm.db2.jcc.b.b.a(b.java:1342)
  | 	at com.ibm.db2.jcc.b.b.s(b.java:1040)
  | 	at com.ibm.db2.jcc.b.b.b(b.java:746)
  | 	at com.ibm.db2.jcc.b.b.a(b.java:732)
  | 	at com.ibm.db2.jcc.b.b.<init>(b.java:333)
  | 	at com.ibm.db2.jcc.DB2Driver.connect(DB2Driver.java:165)
  | 	at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.createManagedConnection(LocalManagedConnectionFactory.java:171)
  | 	... 15 more
  | <->:<anonym>: 2007-12-05 09:23:33,937 [Timer-3] WARN  jboss.messaging.core.impl.JDBCSupport - Trying again after a pause
  | <->:<anonym>: 2007-12-05 09:23:34,583 [Timer-3] WARN  jboss.messaging.core.impl.JDBCSupport - Update worked after retry
  | 

View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4110460#4110460

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4110460



More information about the jboss-user mailing list