[jira] Updated: (AMQ-832) Messages sent and retrieved via STOMP sticking around

["Gary Tully (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/AMQ-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully updated AMQ-832:
---------------------------

    Fix Version/s: 5.3.0
                       (was: 5.2.0)

> Messages sent and retrieved via STOMP sticking around
> -----------------------------------------------------
>
>                 Key: AMQ-832
>                 URL: https://issues.apache.org/activemq/browse/AMQ-832
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.0.1
>         Environment: Java 1.5, Linux, AMD64
>            Reporter: Bruce Mitchener
>             Fix For: 5.3.0
>
>
> I'm sending and receiving messages entirely through STOMP and messages are getting stuck in the queue (using 4.0.1).
> This is pretty inconvenient as when I restart my processes and they re-subscribe, the messages get re-delivered to them.
> incubator-activemq-4.0.1/bin$ ./browse --amqurl tcp://localhost:61616 something/game/0
> JMS_CUSTOM_FIELD:_timestamp = 2006-07-19 10:23:43.847049
> JMS_HEADER_FIELD:JMSDestination = something/game/0
> JMS_HEADER_FIELD:JMSDeliveryMode = non-persistent
> JMS_HEADER_FIELD:JMSMessageID = ID:hotei-60326-1153156802410-3:589:-1:1:8
> JMS_BODY_FIELD:JMSBytes:1 =
> JMS_HEADER_FIELD:JMSExpiration = 0
> JMS_HEADER_FIELD:JMSPriority = 0
> JMS_HEADER_FIELD:JMSRedelivered = false
> JMS_HEADER_FIELD:JMSTimestamp = 0
> JMS_CUSTOM_FIELD:_timestamp = 2006-07-19 10:23:45.535995
> JMS_HEADER_FIELD:JMSDestination = something/game/0
> JMS_HEADER_FIELD:JMSDeliveryMode = non-persistent
> JMS_HEADER_FIELD:JMSMessageID = ID:hotei-60326-1153156802410-3:589:-1:1:9
> JMS_BODY_FIELD:JMSBytes:1 =
> JMS_HEADER_FIELD:JMSExpiration = 0
> JMS_HEADER_FIELD:JMSPriority = 0
> JMS_HEADER_FIELD:JMSRedelivered = false
> JMS_HEADER_FIELD:JMSTimestamp = 0
> I'm not using durable subscriptions, persistence messaging, etc.
> Is there something that I'm doing wrong that might cause this?
> The messages randomly get stuck .. it isn't always repeatable and is much less frequent with 4.0.1 than it was with 4.0 prereleases.
> This software is going into production soon, so would it be safe to try out a 4.0.2 or 4.1 snapshot?  Would they be likely to fix this given the current sets of changes in them?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.