Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Date: Thu, 25 Aug 2011 20:24:28 +0000 (UTC)
From: "Timothy Bish (JIRA)" <jira@apache.org>
To: dev@activemq.apache.org
Message-ID: 
 <95961038.14987.1314303869000.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1563944592.2800.1307979831464.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (AMQ-3366) Non localhost clients unable to
 receive subscription updates
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Timothy Bish commented on AMQ-3366:
-----------------------------------

We need more information to even start to investigate this.  Broker logs with debug enabled, configuration, and client logs would be a necessary start.

> Non localhost clients unable to receive subscription updates
> ------------------------------------------------------------
>
>                 Key: AMQ-3366
>                 URL: https://issues.apache.org/jira/browse/AMQ-3366
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Transport
>    Affects Versions: 5.4.2
>         Environment: WinXP x64, Java 1.6.23
>            Reporter: RWOB
>
> We have a nonpersistent subscriber app.  Most of the time we run the broker and the client on the same machine.  Occasionally however, we will have other clients connect from other PCs on the network, running identical code.
> After some arbitrary time however, new nonlocal clients that connect are unable to receive updates to the topic.  New local clients, however, have no problem.
> For the nonlocal clients, there are no error messages and the broker registers the connection and disconnection of the client.  Just no data streaming through.
> The only thing that seems to resolve the issue is restarting both the broker machine and the client machine which is somewhat problematic.
> I wish I had better details to pinpoint this bug (or idiosyncratic network issue) but the absence of dataflow is tricky to lock down.  Any thoughts on the issue or ways I could help to provide more detailed debug information?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira