1 Reply Latest reply on Mar 16, 2010 10:10 AM by adrian.brock

    Can not store message to JMS_NODE_MSGS table

    dessmith Mar 15, 2010 9:22 AM

      Hi there,

      I am using an application dcm4che.org DCM4CHEE hosted on Jboss 4.3

       

      Within the server logs the app writes a database  constraint violation.

      2010-03-11 10:53:20,468 ERROR -> (Thread-11)  org.dcm4chee.arr.listeners.udp.UDPListener Failed to schedule processing  message received from /127.0.0.1 - <85>Mar 11 10:53:20  serverhost1 dcm4chee: <AuditMessage><EventIdentification  EventActionCode="E" EventDateTime="2010-03-11T10:53:20.449Z"  EventOutcomeIndicator="0"><EventID code="110104" codeSystemName...
      org.jboss.mq.SpyJMSException: Could not store message: 2822 msg=2901  hard NOT_STORED PERSISTENT queue=QUEUE.ARRIncoming priority=4  lateClone=false hashCode=13858724; - nested throw
      able: (java.sql.SQLException: ORA-00001: unique constraint  (DCM4CHEE01.SYS_C0020440) violated
      )
      at  org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:1133)
      at  org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:58)
      at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:180)
      .. I've cut the stack trace here

      and

      2010-03-11 12:12:04,372 ERROR -> (Thread-11)  org.dcm4chee.arr.listeners.udp.UDPListener Failed to schedule processing  message received from /155.231.76.3 - <86>Mar 11 12:12:04  serverhost1
      <?xml version="1.0" encoding="utf-8"?>
      <AuditMessage>
      <EventIdentification EventActionCode="E"  EventDateTime="2010-03-11T12:12:04.336Z" EventOutcomeIndicator="0">
      ...
      org.jboss.mq.SpyJMSException: Could not store message: 2882 msg=2961  hard NOT_STORED PERSISTENT queue=QUEUE.ARRIncoming priority=4  lateClone=false hashCode=6168060; - nested throwa
      ble: (java.sql.SQLException: ORA-00001: unique constraint  (DCM4CHEE01.SYS_C0020440) violated
      )
      at  org.jboss.mq.pm.jdbc2.PersistenceManager.add(PersistenceManager.java:1133)
      at  org.jboss.mq.server.PersistentQueue.addMessage(PersistentQueue.java:58)
      at org.jboss.mq.server.JMSQueue.addMessage(JMSQueue.java:180)
      at  org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:439)
      at  org.jboss.mq.server.JMSDestinationManager.addMessage(JMSDestinationManager.java:422)
      .. I've cut the stack trace here

      The constraint DCM4CHEE01.SYS_C0020440 requires the Message ID row in  the JMS_NODE_MSGS table to be unique.

      I've rebooted the DCM4CHEE JBoss service a few weeks ago, and have  noticed these errors in the logs since the days after the reboot.
      I assume that messages to the server DCM4CHEE are trying to be written to the JMS_NODE_MSGS  table, however the message ID field in the message already exists in the JMS_NODE_MSGS table.

       

      The message provider is JBossMQ, does anyone know of a reason why this is happening, and how to resolve this?

      Des Smith