STOMP quits sending to all subscribers when one client disconnects

[ekaltenbach]

Hello,

I am using Wildfly 9.0 with the built-in HornetQ.  I configured HornetQ to support STOMP.  My clients are implemented in C#.  I am using the C# asynchronous socket classes/methods to connect to JMS/STOMP.  When I subscribe to a JMS topic, I use the following logic:

            System.Text.StringBuilder strBuilder = new System.Text.StringBuilder();

            strBuilder.Append("SUBSCRIBE\n");

            strBuilder.Append("destination:" + destination + "\n");

            strBuilder.Append("id:" + id + "\n");

            strBuilder.Append("ack:auto\n");

            strBuilder.Append("\n");

            strBuilder.Append('\0');

            SendMessageToStompSocket(strBuilder.ToString());

All of my code seems to be working great.  I have multiple clients connecting via STOMP and all are able to send and receive messages.  The one issue I have occurs when one of my clients application closes.  When one client application shuts down, all of the other client applications quit receiving  messages.  If I start a new client application, as soon as it sends a SUBSCRIBE message then all of the client applications, that had previously send SUBSCRIBE messages, will begin receiving messages again from the subscribed JMS topic.

I tried sending another SUBSCRIBE message when the messages stop, but I received a response from the server saying that I was already subscribed with that id.

Has anybody else seen this behavior? 

Does anybody have any suggestions how to fix or work around the problem?

Having all of my clients stop receiving messages when I exit a single client is unacceptable.

Thanks,

Ed

[jbertram]

It might be worth trying Wildfly 10 which uses ActiveMQ Artemis.  To be clear, the HornetQ code-base was donated to Apache ActiveMQ almost 2 years ago now.  All development has been (and will be) focused on Artemis.  If this same thing happens in Artemis then I recommend coming up with an easy way to reproduce the issue and then one of the developers can take a closer look.

[ekaltenbach]

Hello,

Here are a few more details. 

The problem happens regardless if I send an UNSUBSCRIBE or not before exiting.  I do not send a DISCONNECT message.  I am pretty sure that the problem occurs when the socket is shutdown and disconnected. 

Ed