Occasionally, after a JBoss server restart we get the following exception when we send a new message: java.sql.SQLException: ORA-00001: unique constraint (JMS_MESSAGES_PK) violated
An investigation of the JBoss source code indicates that the messageIdCounter is reset to 0 on JMS server restart. See the following JBoss files in the messaging component: JMSTopic.java JMSDestination.java If there are any persistent unprocessed messages in the queue when the server is brought down, there is the possibily of a messageid collision when the server is started. Perhaps the messageIdCounter should be initialized to "select max(messageid) from JMS_MESSAGES"? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3831616#3831616 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3831616 ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
