Hi Michael, it'd be great to make this work for Stomp. Any contribution is welcome. For starters, let's create a Jira issue to track this requirement.
Cheers -- Dejan Bosanac - http://twitter.com/dejanb Open Source Integration - http://fusesource.com/ ActiveMQ in Action - http://www.manning.com/snyder/ Blog - http://www.nighttale.net On Tue, Mar 9, 2010 at 5:12 PM, mjustin <michael.jus...@gmx.net> wrote: > > Hello, > > following > http://activemq.apache.org/delay-and-schedule-message-delivery.html I > tried > to delay a message using a AMQ_SCHEDULED_DELAY header property. > > The Stom frames look like this: > > send: > CONNECT > > > > received: > CONNECTED > session:ID:mj-PC-49610-1268150511998-3:10 > > > send: > SUBSCRIBE > destination:/queue/Habari > ack:auto > id:{AD4DFED5-B508-41B6-9AE2-F43E890A2522} > > > > send: > SEND > destination:/queue/Habari > AMQ_SCHEDULED_DELAY:2000 > > test msg > > -- > After the SEND message, the broker interrupts the connection. If I remove > the header property, the broker sends the message immediately as usual. So > I > guess that the Stomp code handles the new header property in an unexpected > way. If I find the time I'll have a look at the source code. > > Regards, > > > ----- > Michael Justin > SCJP, SCJA > betasoft - Software for Delphi™ and for the Java™ platform > http://www.mikejustin.com - http://www.betabeans.de > -- > View this message in context: > http://old.nabble.com/Delay-messages-with-Stomp%3A-connection-reset-tp27837862p27837862.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com. > >
