seems like that would be easy to prove with a simple junit test. see: org.apache.activemq.transport.stomp.StompTest in activemq-core
On 26 September 2012 14:05, <[email protected]> wrote: > Hi, > > Upon some investigation I found that, stomp client uses transactions. > And when it sends ack message, message count decreases by one, and again when > "commit" is sent, message count further decreases > and becomes negative. > > What could be the problem? Please reply as we have system in production :-(. > > Thanks > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Wednesday, September 26, 2012 3:57 PM > To: [email protected] > Subject: ActiveMQ 5.5 sending message twice > > Hi, > > > We are facing an issue with ActiveMQ version 5.5 for stomp clients. > The issue is, we have a python client using stomp, which uses transactions. > Whenever there is new message, ActiveMQ tries to send two messages, and > message count is negative. > There is no exception in python side, and it does its job correctly. > > Am I missing something? > > Thanks -- http://fusesource.com http://blog.garytully.com
