You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Bug Vito (JIRA)" <ji...@apache.org> on 2012/04/21 16:08:35 UTC
[jira] [Created] (AMQNET-383) NMS.Stomp being disconnected from
Apache Apollo after sending messages, after a period with no communication
on the topic
Bug Vito created AMQNET-383:
-------------------------------
Summary: NMS.Stomp being disconnected from Apache Apollo after sending messages, after a period with no communication on the topic
Key: AMQNET-383
URL: https://issues.apache.org/jira/browse/AMQNET-383
Project: ActiveMQ .Net
Issue Type: Bug
Components: Stomp
Affects Versions: 1.5.2
Environment: Apollo 1.0 or 1.1 (windows or linux) with vanilla configuration, with the addition of a valid user in the group "users"
Apache NMS.Stomp 1.5.2 dlls
NUnit 2.6
MonoDevelop 2.8.x or Visual studio 2010
Reporter: Bug Vito
Assignee: Jim Gomes
Fix For: 1.5.3
Having only a consumer and a producer on two different connections, and being on the same topic, The following causes a disconnect:
1 producer sends a message/messages
2 reasonable delay (lets say typical 30 seconds)
3 producer sends messages again
At this point the consumer received the messages send at "1", and some of the messages of "3" before being disconnected:
Client side exception:
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
Server side:
2012-04-18 14:13:16,293 Shutting connection '/10.10.21.200:54398' down due to: java.io.IOException: Unable to parser header line [ascii: ACK]
2012-04-18 14:13:16,294 disconnected: local:/10.10.23.70:61613, remote:/10.10.21.200:54398
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (AMQNET-383) NMS.Stomp being disconnected from
Apache Apollo after sending messages, after a period with no communication
on the topic
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish resolved AMQNET-383.
---------------------------------
Resolution: Fixed
Fix applied to trunk and the 1.5.x fixes branch.
> NMS.Stomp being disconnected from Apache Apollo after sending messages, after a period with no communication on the topic
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-383
> URL: https://issues.apache.org/jira/browse/AMQNET-383
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.5.2
> Environment: Apollo 1.0 or 1.1 (windows or linux) with vanilla configuration, with the addition of a valid user in the group "users"
> Apache NMS.Stomp 1.5.2 dlls
> NUnit 2.6
> MonoDevelop 2.8.x or Visual studio 2010
> Reporter: Bug Vito
> Assignee: Timothy Bish
> Fix For: 1.5.3
>
> Attachments: NUnitTests.cs
>
>
> Having only a consumer and a producer on two different connections, and being on the same topic, The following causes a disconnect:
> 1 producer sends a message/messages
> 2 reasonable delay (lets say typical 30 seconds)
> 3 producer sends messages again
> At this point the consumer received the messages send at "1", and some of the messages of "3" before being disconnected:
> Client side exception:
> Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
> Server side:
> 2012-04-18 14:13:16,293 Shutting connection '/10.10.21.200:54398' down due to: java.io.IOException: Unable to parser header line [ascii: ACK]
> 2012-04-18 14:13:16,294 disconnected: local:/10.10.23.70:61613, remote:/10.10.21.200:54398
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (AMQNET-383) NMS.Stomp being disconnected from
Apache Apollo after sending messages, after a period with no communication
on the topic
Posted by "Bug Vito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Bug Vito updated AMQNET-383:
----------------------------
Attachment: NUnitTests.cs
NUnit test cases
> NMS.Stomp being disconnected from Apache Apollo after sending messages, after a period with no communication on the topic
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-383
> URL: https://issues.apache.org/jira/browse/AMQNET-383
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.5.2
> Environment: Apollo 1.0 or 1.1 (windows or linux) with vanilla configuration, with the addition of a valid user in the group "users"
> Apache NMS.Stomp 1.5.2 dlls
> NUnit 2.6
> MonoDevelop 2.8.x or Visual studio 2010
> Reporter: Bug Vito
> Assignee: Jim Gomes
> Fix For: 1.5.3
>
> Attachments: NUnitTests.cs
>
>
> Having only a consumer and a producer on two different connections, and being on the same topic, The following causes a disconnect:
> 1 producer sends a message/messages
> 2 reasonable delay (lets say typical 30 seconds)
> 3 producer sends messages again
> At this point the consumer received the messages send at "1", and some of the messages of "3" before being disconnected:
> Client side exception:
> Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
> Server side:
> 2012-04-18 14:13:16,293 Shutting connection '/10.10.21.200:54398' down due to: java.io.IOException: Unable to parser header line [ascii: ACK]
> 2012-04-18 14:13:16,294 disconnected: local:/10.10.23.70:61613, remote:/10.10.21.200:54398
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-383) NMS.Stomp being disconnected from
Apache Apollo after sending messages, after a period with no communication
on the topic
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13294627#comment-13294627 ]
Timothy Bish commented on AMQNET-383:
-------------------------------------
Not quite sure what's going on here. Tested with Apollo v1.3 and the connection fails 30 seconds after the last ack indicating something with the keep alive stuff but not sure what.
> NMS.Stomp being disconnected from Apache Apollo after sending messages, after a period with no communication on the topic
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-383
> URL: https://issues.apache.org/jira/browse/AMQNET-383
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.5.2
> Environment: Apollo 1.0 or 1.1 (windows or linux) with vanilla configuration, with the addition of a valid user in the group "users"
> Apache NMS.Stomp 1.5.2 dlls
> NUnit 2.6
> MonoDevelop 2.8.x or Visual studio 2010
> Reporter: Bug Vito
> Assignee: Timothy Bish
> Fix For: 1.5.3
>
> Attachments: NUnitTests.cs
>
>
> Having only a consumer and a producer on two different connections, and being on the same topic, The following causes a disconnect:
> 1 producer sends a message/messages
> 2 reasonable delay (lets say typical 30 seconds)
> 3 producer sends messages again
> At this point the consumer received the messages send at "1", and some of the messages of "3" before being disconnected:
> Client side exception:
> Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
> Server side:
> 2012-04-18 14:13:16,293 Shutting connection '/10.10.21.200:54398' down due to: java.io.IOException: Unable to parser header line [ascii: ACK]
> 2012-04-18 14:13:16,294 disconnected: local:/10.10.23.70:61613, remote:/10.10.21.200:54398
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (AMQNET-383) NMS.Stomp being disconnected from
Apache Apollo after sending messages, after a period with no communication
on the topic
Posted by "Bug Vito (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13395892#comment-13395892 ]
Bug Vito commented on AMQNET-383:
---------------------------------
As a temporary workaround, a node in our project has been dedicated as a master (this could also be a dedicated slave), which sends a heartbeat (simple message)on the topic at every 2.5s to keep everything alive. The solution has now been up and running for weeks.
> NMS.Stomp being disconnected from Apache Apollo after sending messages, after a period with no communication on the topic
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-383
> URL: https://issues.apache.org/jira/browse/AMQNET-383
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.5.2
> Environment: Apollo 1.0 or 1.1 (windows or linux) with vanilla configuration, with the addition of a valid user in the group "users"
> Apache NMS.Stomp 1.5.2 dlls
> NUnit 2.6
> MonoDevelop 2.8.x or Visual studio 2010
> Reporter: Bug Vito
> Assignee: Timothy Bish
> Fix For: 1.5.3
>
> Attachments: NUnitTests.cs
>
>
> Having only a consumer and a producer on two different connections, and being on the same topic, The following causes a disconnect:
> 1 producer sends a message/messages
> 2 reasonable delay (lets say typical 30 seconds)
> 3 producer sends messages again
> At this point the consumer received the messages send at "1", and some of the messages of "3" before being disconnected:
> Client side exception:
> Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
> Server side:
> 2012-04-18 14:13:16,293 Shutting connection '/10.10.21.200:54398' down due to: java.io.IOException: Unable to parser header line [ascii: ACK]
> 2012-04-18 14:13:16,294 disconnected: local:/10.10.23.70:61613, remote:/10.10.21.200:54398
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (AMQNET-383) NMS.Stomp being disconnected from
Apache Apollo after sending messages, after a period with no communication
on the topic
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AMQNET-383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQNET-383:
-----------------------------------
Assignee: Timothy Bish (was: Jim Gomes)
> NMS.Stomp being disconnected from Apache Apollo after sending messages, after a period with no communication on the topic
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-383
> URL: https://issues.apache.org/jira/browse/AMQNET-383
> Project: ActiveMQ .Net
> Issue Type: Bug
> Components: Stomp
> Affects Versions: 1.5.2
> Environment: Apollo 1.0 or 1.1 (windows or linux) with vanilla configuration, with the addition of a valid user in the group "users"
> Apache NMS.Stomp 1.5.2 dlls
> NUnit 2.6
> MonoDevelop 2.8.x or Visual studio 2010
> Reporter: Bug Vito
> Assignee: Timothy Bish
> Fix For: 1.5.3
>
> Attachments: NUnitTests.cs
>
>
> Having only a consumer and a producer on two different connections, and being on the same topic, The following causes a disconnect:
> 1 producer sends a message/messages
> 2 reasonable delay (lets say typical 30 seconds)
> 3 producer sends messages again
> At this point the consumer received the messages send at "1", and some of the messages of "3" before being disconnected:
> Client side exception:
> Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.
> Server side:
> 2012-04-18 14:13:16,293 Shutting connection '/10.10.21.200:54398' down due to: java.io.IOException: Unable to parser header line [ascii: ACK]
> 2012-04-18 14:13:16,294 disconnected: local:/10.10.23.70:61613, remote:/10.10.21.200:54398
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira