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/01 16:00:20 UTC

[jira] [Commented] (AMQ-4290) if subscriber is stopped publisher also stopped in my app with activemq

    [ https://issues.apache.org/jira/browse/AMQ-4290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13568773#comment-13568773 ] 

Timothy Bish commented on AMQ-4290:
-----------------------------------

This sounds like an issue of producer flow control kicking in.  See: http://activemq.apache.org/producer-flow-control.html
                
> if subscriber is stopped publisher also stopped in my app with activemq
> -----------------------------------------------------------------------
>
>                 Key: AMQ-4290
>                 URL: https://issues.apache.org/jira/browse/AMQ-4290
>             Project: ActiveMQ
>          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