Currently we are using only one broker and at database level even if we set no row lock or lock options violation of primary key exceptions throws when server is loaded in cluster.at a shot when two users commit javax session constraint violation occurs.
-- View this message in context: http://activemq.2283324.n4.nabble.com/Activemq-Duplicate-Message-persistence-tp4668835p4668865.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.
