Thanks
That's what I suspected as well.
This
2007-02-07 22:46:41.977; WARN [DefaultMessageListenerContainer-2]
messaging.core.plugin.JDBCPersistenceManager - Trying again after a pause
| 2007-02-07 22:46:42.009; WARN [DefaultMessageListenerContainer-2]
jboss.resource.connectionmanager.TxConnectionManager - Connection error occured:
org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@1085e92[state=NORMAL
mc=org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@16de23f handles=1
lastUse=1170868600398 permit=true trackByTx=true
mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@120d254
context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@1d08960
xaResource=org.jboss.resource.adapter.jdbc.xa.XAManagedConnection@16de23f txSync=null]
| java.lang.NullPointerException
| at java.lang.System.arraycopy(Native Method)
| at com.ibm.db2.jcc.a.jc.c(jc.java:135)
| at com.ibm.db2.jcc.a.x.a(x.java:891)
| at com.ibm.db2.jcc.a.x.a(x.java:1035)
| at com.ibm.db2.jcc.a.mg.a(mg.java:1317)
| at com.ibm.db2.jcc.a.mg.nb(mg.java:3033)
| at com.ibm.db2.jcc.a.mg.d(mg.java:2096)
| at com.ibm.db2.jcc.a.mg.W(mg.java:463)
| at com.ibm.db2.jcc.a.mg.executeUpdate(mg.java:446)
| at
org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251)
| at
org.jboss.messaging.core.plugin.JDBCPersistenceManager.updateWithRetry(JDBCPersistenceManager.java:4387)
|
|
makes me think that this is what it is ...
I've opened this thread because I am about to release 1.0.1.SP4
This issue won't make it in SP4, it needs to be discussed here first.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4013427#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...