activemq-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From AlexP <apara-activ...@standardset.com>
Subject Re: Apollo 1.6 multiple connected/disconnected messages while using Stomp
Date Fri, 15 Nov 2013 03:44:16 GMT
After some debugging, we discovered that Apollo 1.6 Stomp implementation
seems to be closing a Stomp connection on an un-subscribe of an invalid
subscription.  

Here is the sample log:

2013-11-14 18:45:36,072 STOMP connection '/127.0.0.1:38038' error: The
subscription '2' not found.
2013-11-14 18:45:41,083 disconnected: local:/127.0.0.1:61613,
remote:/127.0.0.1:38038

2013-11-14 18:46:03,034 STOMP connection '/127.0.0.1:38039' error: The
subscription '0' not found.
2013-11-14 18:46:08,040 disconnected: local:/127.0.0.1:61613,
remote:/127.0.0.1:38039

We corrected our code which was indeed trying to un-subscribe invalid
subscriptions so this issue is not occurring, however, I am wondering if an
ERROR frame should have been sent instead of a disconnect?

Thanks.
-AP_



--
View this message in context: http://activemq.2283324.n4.nabble.com/Apollo-1-6-multiple-connected-disconnected-messages-while-using-Stomp-tp4674484p4674512.html
Sent from the ActiveMQ - User mailing list archive at Nabble.com.

Mime
View raw message