1 Reply Latest reply on Nov 16, 2010 3:13 AM by Wolf-Dieter Fink

    jboss Message queue

    Chammi Prasad Newbie

      Hi,

      I am using JBOSS Message Queue and I have found following error. Please help me to find this out.

       

      Jboss version : jboss-4.2.3.

       

      Thanks

       

       

      02:50:20,060 INFO  [JmsActivation] Attempting to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@f9aa66(ra=org.jboss.resource.adapter.jms.J
      msResourceAdapter@c33893 destination=queue/MCB isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 min
      Session=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null
      DLQMaxResent=5)
      02:50:20,085 ERROR [JmsActivation] Unable to reconnect org.jboss.resource.adapter.jms.inflow.JmsActivationSpec@f9aa66(ra=org.jboss.resource.adapter.jms.JmsRe
      sourceAdapter@c33893 destination=queue/MCB isTopic=false tx=true durable=false reconnect=10 provider=java:/DefaultJMSProvider user=null maxMessages=1 minSess
      ion=1 maxSession=15 keepAlive=60000 useDLQ=true DLQHandler=org.jboss.resource.adapter.jms.inflow.dlq.GenericDLQHandler DLQJndiName=queue/DLQ DLQUser=null DLQ
      MaxResent=5)
      org.jboss.mq.SpyJMSException: Could not update the message in the database: update affected 0 rows
              at org.jboss.mq.pm.jdbc2.PersistenceManager.update(PersistenceManager.java:1331)
              at org.jboss.mq.server.BasicQueue.updateRedeliveryFlags(BasicQueue.java:1212)
              at org.jboss.mq.server.BasicQueue.addReceiver(BasicQueue.java:250)
              at org.jboss.mq.server.JMSQueue.addReceiver(JMSQueue.java:122)
              at org.jboss.mq.server.ClientConsumer.setEnabled(ClientConsumer.java:107)
              at org.jboss.mq.server.JMSDestinationManager.setEnabled(JMSDestinationManager.java:150)
              at org.jboss.mq.server.JMSServerInterceptorSupport.setEnabled(JMSServerInterceptorSupport.java:146)
              at org.jboss.mq.server.TracingInterceptor.setEnabled(TracingInterceptor.java:482)
              at org.jboss.mq.server.JMSServerInvoker.setEnabled(JMSServerInvoker.java:152)
              at org.jboss.mq.il.jvm.JVMServerIL.setEnabled(JVMServerIL.java:76)
              at org.jboss.mq.Connection.start(Connection.java:657)
              at org.jboss.resource.adapter.jms.inflow.JmsActivation.setupSessionPool(JmsActivation.java:589)
              at org.jboss.resource.adapter.jms.inflow.JmsActivation.setup(JmsActivation.java:323)
              at org.jboss.resource.adapter.jms.inflow.JmsActivation.handleFailure(JmsActivation.java:259)
              at org.jboss.resource.adapter.jms.inflow.JmsActivation.onException(JmsActivation.java:278)
              at org.jboss.mq.Connection$ExceptionListenerRunnable.run(Connection.java:1356)
              at java.lang.Thread.run(Thread.java:619)

        • 1. Re: jboss Message queue
          Wolf-Dieter Fink Master

          This looks similar to the optimistic locking algorythm of the EJB2 cmp persistence manager.

          There all updates with OLock will have a version column and the update is e.g. 'UPDATE .... set ol_version=2 WHERE ol_version=1'

          and if a concurrent process has updated before a message like yours occor.

          So is the behaviour sporadicaly?

          To get mor information you should active log level TRACE for 'org.jboss.mq.pm.jdbc2'.