Mailing-List: contact users-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of lists@nabble.com designates
 216.139.236.158 as permitted sender)
Message-ID: <27837862.post@talk.nabble.com>
Date: Tue, 9 Mar 2010 08:12:22 -0800 (PST)
From: mjustin <michael.justin@gmx.net>
To: users@activemq.apache.org
Subject: Delay messages with Stomp: connection reset
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable


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=E2=84=A2 and for the Java=E2=84=A2 platform
http://www.mikejustin.com - http://www.betabeans.de
--=20
View this message in context: http://old.nabble.com/Delay-messages-with-Sto=
mp%3A-connection-reset-tp27837862p27837862.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.