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

Timothy Bish closed AMQ-2994.
-----------------------------

    Resolution: Cannot Reproduce

Not reported elsewhere and no logs are other code needed to investigate.
                
> Topic (non-durable)  gets unsubscribed even though the TCP connections to 
> Active MQ are alive (observed on Windows 2008 server)
> -------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2994
>                 URL: https://issues.apache.org/jira/browse/AMQ-2994
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.2.0
>         Environment: Windows 2008 server (Enterprise edition)
>            Reporter: Dip Narayan Sarkar
>   Original Estimate: 150h
>  Remaining Estimate: 150h
>
> In the concerned product, one Web Application deployed on Tomcat server  does 
> non-durable subscription to topics to Active MQ.
> Both Active MQ and Tomcat are running on WIndows 2008 server (Enterprise 
> edition)
> On one of the 2008 servers, it is seen that one topic subscribed by Tomcat 
> got "UNSUBSCRIBED" even though the tcp connections from Tomcat to Active MQ 
> are alive. The messages published by the corresponding topic is about 15 - 20 
> per minute.  Tomcat logs DO NOT have any relevant exception trace.
> Neither there are any exception traces in ActiveMQ logs
> The system has been running for 15 days. On 16th day we found that the JMS 
> messages are not reaching the Web App, upon debugging process thru JConsole, 
> we found that the Tomcat's subscription are not present.
> This happened for the 2nd time on a Win 2008 server.
> Same code base is running fine for > 25 days (with larger flux of messages) 
> on more than one Win 2003 servers.
> Need some pointers on possible root causes and if any known issues are 
> present.

--
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

        

Reply via email to