activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bug Vito (JIRA)" <jira+amq...@apache.org>
Subject [jira] [Updated] (AMQNET-383) NMS.Stomp being disconnected from Apache Apollo after sending messages, after a period with no communication on the topic
Date Sat, 21 Apr 2012 14:14:34 GMT

     [ 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

        

Mime
View raw message