Problem with JDBC2 PM, Mysql and JBoss 3.2.4

[stephanenicoll]

Hello,

Since we moved to JBoss 3.2.4, we start having trouble with JBossMQ. We are using JDBC2 persistence manager and mysql 4.0.18

We are using the standard mysql-jdbc2-service.xml provided with the JBoss release

11:25:08,632 WARN [jboss.tm.TransactionImpl] XAException: tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=mymachine.mycompany.org//259, BranchQual=] errorCode=XAER_RMERR
org.jboss.mq.SpyXAException: - nested throwable: (org.jboss.mq.SpyTransactionRolledBackException: Transaction was rolled back.; - nested throwable: (org.jboss.mq.SpyJMSException: Could not mark the message as deleted in the database: update affected 0 rows))
 at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:88)
 at org.jboss.tm.TransactionImpl.commitResources(TransactionImpl.java:1656)
 at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:375)
 at org.jboss.tm.TxManager.commit(TxManager.java:142)
 at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:361)
 at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:871)
 at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:159)
 at org.jboss.mq.SpySession.run(SpySession.java:347)
 at org.jboss.jms.asf.StdServerSession.run0(StdServerSession.java:200)
 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
 at java.lang.Thread.run(Thread.java:534)
Caused by: org.jboss.mq.SpyTransactionRolledBackException: Transaction was rolled back.; - nested throwable: (org.jboss.mq.SpyJMSException: Could not mark the message as deleted in the database: update affected 0 rows)
 at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:447)
 at org.jboss.mq.server.JMSServerInterceptorSupport.transact(JMSServerInterceptorSupport.java:186)
 at org.jboss.mq.security.ServerSecurityInterceptor.transact(ServerSecurityInterceptor.java:182)
 at org.jboss.mq.server.TracingInterceptor.transact(TracingInterceptor.java:438)
 at org.jboss.mq.server.JMSServerInvoker.transact(JMSServerInvoker.java:186)
 at org.jboss.mq.il.jvm.JVMServerIL.transact(JVMServerIL.java:327)
 at org.jboss.mq.Connection.send(Connection.java:1206)
 at org.jboss.mq.SpyXAResourceManager.commit(SpyXAResourceManager.java:150)
 at org.jboss.mq.SpyXAResource.commit(SpyXAResource.java:84)
 ... 11 more
Caused by: org.jboss.mq.SpyJMSException: Could not mark the message as deleted in the database: update affected 0 rows
 at org.jboss.mq.pm.jdbc2.PersistenceManager.remove(PersistenceManager.java:1002)
 at org.jboss.mq.server.BasicQueue.acknowledge(BasicQueue.java:527)
 at org.jboss.mq.server.JMSTopic.acknowledge(JMSTopic.java:290)
 at org.jboss.mq.server.ClientConsumer.acknowledge(ClientConsumer.java:322)
 at org.jboss.mq.server.JMSDestinationManager.acknowledge(JMSDestinationManager.java:524)
 at org.jboss.mq.server.JMSDestinationManager.transact(JMSDestinationManager.java:436)
 ... 19 more
11:25:08,636 WARN [jboss.tm.TransactionImpl] XAException: tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=mymachine.mycompany.org//259, BranchQual=] errorCode=XAER_NOTA
javax.transaction.xa.XAException
 at org.jboss.mq.SpyXAResourceManager.rollback(SpyXAResourceManager.java:230)
 at org.jboss.mq.SpyXAResource.rollback(SpyXAResource.java:154)
 at org.jboss.tm.TransactionImpl.rollbackResources(TransactionImpl.java:1732)
 at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:405)
 at org.jboss.tm.TxManager.commit(TxManager.java:142)
 at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:361)
 at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:871)
 at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:159)
 at org.jboss.mq.SpySession.run(SpySession.java:347)
 at org.jboss.jms.asf.StdServerSession.run0(StdServerSession.java:200)
 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
 at java.lang.Thread.run(Thread.java:534)
11:25:08,638 ERROR [jms.asf.StdServerSession] failed to commit/rollback
org.jboss.tm.JBossRollbackException: Unable to commit, tx=TransactionImpl:XidImpl [FormatId=257, GlobalId=mymachine.mycompany.org//259, BranchQual=] status=STATUS_NO_TRANSACTION; - nested throwable: (javax.transaction.xa.XAException)
 at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:415)
 at org.jboss.tm.TxManager.commit(TxManager.java:142)
 at org.jboss.jms.asf.StdServerSession.onMessage(StdServerSession.java:361)
 at org.jboss.mq.SpyMessageConsumer.sessionConsumerProcessMessage(SpyMessageConsumer.java:871)
 at org.jboss.mq.SpyMessageConsumer.addMessage(SpyMessageConsumer.java:159)
 at org.jboss.mq.SpySession.run(SpySession.java:347)
 at org.jboss.jms.asf.StdServerSession.run0(StdServerSession.java:200)
 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:180)
 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
 at java.lang.Thread.run(Thread.java:534)
Caused by: javax.transaction.xa.XAException
 at org.jboss.mq.SpyXAResourceManager.rollback(SpyXAResourceManager.java:230)
 at org.jboss.mq.SpyXAResource.rollback(SpyXAResource.java:154)
 at org.jboss.tm.TransactionImpl.rollbackResources(TransactionImpl.java:1732)
 at org.jboss.tm.TransactionImpl.commit(TransactionImpl.java:405)
 ... 9 more

Any idea?

Stephane

[genman]

Take a look at:

org.jboss.mq.pm.jdbc2.PersistenceManager.remove(PersistenceManager.java:1002)

in CVS, and see if something changed between versions.

Perhaps there is an extra check to see if the data was updated? I know when I used MySQL, the driver didn't give me a row update count.

[darklord]

Well apparently there is no changes regarding that between 3.2.3 and 3.2.4, at least as far as PM is concerned.

http://cvs.sourceforge.net/viewcvs.py/jboss/jbossmq/src/main/org/jboss/mq/pm/jdbc2/PersistenceManager.java?r1=text&tr1=1.6.2.12&r2=text&tr2=1.6.2.16&diff_format=h

Regards,

Stephane

[darklord]

The weird thing is that I am porting an application from 3.2.3 to 3.2.4: I have exactly the same code, the same datamodel, the same configuration (same mysql connector 3.0.11).

The only thing I had to change in the code is a call to jmsConnection.start() if I want to receive messages (very annoying by the way, that's quite a big change!).

If I switch to 3.2.4, I suddently have those errors, on the same machine.

Any clue where I should search (because it's straight SQL calls towards the DB so I wonder how this could have changed ...)

Regards,

Stephane

[darklord]

I searched the forum, found nothing similar. I am using the mysql-jdbc-service provided with Jboss


Since 3.2.4, we have to call explicitely connection.start() if we want to receive messages (I am using java:/JmsXA) If I run the application without calling connection.start() evertime I want to receive messages, it works

Meaning, I do not receive my messages but I don't have the stactrace above.

Any clue? Will post trace logs in a few minutes.

Regards,

Stephane

[murilo_fla]

Hi
I had a similar problem. After some googling, I had a clue. I forgot to change the "Pad" attribute to true in $JBOSS_SERVER_HOME/conf/jboss-service.xml.
If tou don´t know what it is, just uncomment a line like that, in that file:

<mbean code="org.jboss.tm.XidFactory"
 name="jboss:service=XidFactory">
 <attribute name="Pad">true</attribute> -- uncomment!!
 </mbean>

Att
Murilo