[jira] [Resolved] (ARTEMIS-2278) Lost Message - Never Delivered - STOMP? Maybe

["Justin Bertram (JIRA)" <ji...@apache.org>]

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

Justin Bertram resolved ARTEMIS-2278.
-------------------------------------
    Resolution: Information Provided

> Lost Message - Never Delivered - STOMP? Maybe
> ---------------------------------------------
>
>                 Key: ARTEMIS-2278
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2278
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: STOMP
>    Affects Versions: 2.5.0
>            Reporter: Guy Allard
>            Assignee: Justin Bertram
>            Priority: Major
>         Attachments: artnomsg.zip, broker.xml.2.4.0, broker.xml.2.6.4
>
>
> Problem Description:
> STOMP is used to SEND a message to the broker, and then SUBSCRIBE and
> receive messages. In this problem no MESSAGE frame is ever received
> from the broker (and client hangs during receive).
> What Artemis level?:
> I see this using *Artemis 2.5.0 or any of the 2.6.x series.* I have
> a 2.4.0 system that runs flawlessly.
> The attachment has:
> - a short Ruby script that recreates the problem here
> - data from a working 2.4.0 system: a) artemis.log and b) a tcpdump
> of packet traffic
> - data from a failing 2.6.4 system: a) artemis.log and b) a tcpdump
> of packet traffic
> My Thoughts:
> This seems to be STOMP related because I also have a JMS test bed that
> does not fail like this.
> However, I develop/maintain two different STOMP client libraries (one Ruby, one go).
> I see this problem in both of them.
> Guide me please. Is this a bug or am I doing something totally
> stupid.
> The attachment should be named: artnomsg.zip.
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)