6 Replies Latest reply on Feb 9, 2007 6:06 AM by Ovidiu Feodorov

    DB2 persistence problem

    Ovidiu Feodorov Master

      This is a companion discussion thread to http://jira.jboss.org/jira/browse/JBMESSAGING-817

      Please add all your comments here, until we reach a conclusion.

        • 1. Re: DB2 persistence problem
          Weston M. Price Master

          Might be a DB2 driver/JCA configuration thing. I will take a look.

          • 2. Re: DB2 persistence problem
            Ovidiu Feodorov Master


            That's what I suspected as well.


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

            • 3. Re: DB2 persistence problem
              Tim Fox Master

              Well.. we don't currently support DB2.

              The config has not been tested like the other configs. If it hasn't been tested and on our roadmap, then, yes sure it's nice to have, but not something that can be in an official release, since we don't know if it works, or there are major problems that will prevent it from working.

              I am currently testing the configs for 1.2. If someone has a request for DB2 then I will *try* and fit it in, although time is short. Otherwise a feature request should be added in JIRA and we will get around to it.

              • 4. Re: DB2 persistence problem
                Ovidiu Feodorov Master

                Chances of a DB2 configuration making into release will improva a lot if whoever makes the request is also willing to contribute time to fix/test the configuration.

                • 5. Re: DB2 persistence problem
                  Tim Fox Master

                  We can't put untested configs into a distro, unless we clearly mark them as "untested" - use at your own peril..

                  As I say, I will try and get DB2 in 1.2, and if passes the test suite it should be easy to backport to 1.0.x

                  • 6. Re: DB2 persistence problem
                    Ovidiu Feodorov Master

                    We won't. The issue has been moved to SP5 even before I started this thread.