there is no "automatic" redelivery on the client side the way activemq libraries do for openwire. that's because a STOMP client can be written by anyone and the Spec doesn't address redelivery on the client side. But, you are of course able to build in a redelivery functionality yourself.
if you don't commit an interaction that had an "ACK" for a message, or if your rollback, then the broker will not see the ack and will keep the message around. on the client side you won't see this being "redelivered" in order because ActiveMQ also uses a prefetch (as Tim mentioned). You can set prefetch to 1 to ensure things are delivered in order and AFAIK the message would be redispatched to your client On Thu, Dec 5, 2013 at 10:54 AM, Sophia Wright <sophiawrigh...@gmail.com> wrote: > Yes, that is fine. But my question is " Why there is NO message redelivery in > case of STOMP transactions (like JMS transactions have) ? > > > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Transactions-in-Stomp-tp4675080p4675211.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. -- Christian Posta http://www.christianposta.com/blog twitter: @christianposta
