You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2013/02/14 21:49:12 UTC
[jira] [Closed] (AMQNET-407) if subscriber is stopped publisher
also stopped in my app with activemq
[ https://issues.apache.org/jira/browse/AMQNET-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish closed AMQNET-407.
-------------------------------
Resolution: Incomplete
No test case with broker config provided. Looks to be a misconfiguration of producer flow control on the broker side
> if subscriber is stopped publisher also stopped in my app with activemq
> -----------------------------------------------------------------------
>
> Key: AMQNET-407
> URL: https://issues.apache.org/jira/browse/AMQNET-407
> Project: ActiveMQ .Net
> Issue Type: Bug
> Environment: c# code with Apache.NMS and Apache.NMS.ActiveMQ dll
> ActiveMQ version is 5.6
> Reporter: Tamilmaran
>
> I studied that in ActiveMQ publisher publishes messages even if there is no subscriber to consume it. But in my application it is not. My server app has a durable subscriber, client app publishes msg to server. If i stopped the server, the client is not publishing any message. When i checked the log it's showing that connection is already closed. What could be the reason for it or any activemq configuration change?
> I have used c# code with Apache.NMS and Apache.NMS.ActiveMQ dll
> ActiveMQ version is 5.6
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira