Mailing-List: contact dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@activemq.apache.org
Message-ID: <13518424.25111277480812608.JavaMail.jira@thor>
Date: Fri, 25 Jun 2010 11:46:52 -0400 (EDT)
From: "Timothy Bish (JIRA)" <jira+amqnet@apache.org>
To: dev@activemq.apache.org
Subject: [jira] Commented: (AMQNET-258) Getting Unknown Response ID errors
 in client log on failover
In-Reply-To: <26568623.23431277397291810.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/activemq/browse/AMQNET-258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60285#action_60285 ] 

Timothy Bish commented on AMQNET-258:
-------------------------------------

I'd actually like to drop them down to Debug level unless there's some objection since under normal circumstances these generally don't hurt anything and can cause some confusion especially around failover which is a commonly used feature.

> Getting Unknown Response ID errors in client log on failover
> ------------------------------------------------------------
>
>                 Key: AMQNET-258
>                 URL: https://issues.apache.org/activemq/browse/AMQNET-258
>             Project: ActiveMQ .Net
>          Issue Type: Bug
>          Components: NMS
>    Affects Versions: 1.3.0
>         Environment: Client side Windows 2003, NMS 1.3.0.1959, ActiveMQ Client 1.3.0.1965
> Broker ActiveMQ 5.3.1-fuse-01-00, Redhat Linux 64 bit
>            Reporter: Jonathan Anstey
>            Assignee: Timothy Bish
>         Attachments: activemq1.xml, activemq2.xml, nms-client.log, nms-client.zip
>
>
> So the issue is that I'm getting "Unknown response ID" errors in my NMS client log. I've attached the client as nms-client.zip and the log as nms-client.log. I was running this client on a Windows server 2003 system though any Windows box should do.
> The client is connecting with a failover URI like
> failover:(tcp://mendoza:61616?keepAlive=true&wireFormat.maxInactivityDuration=0,tcp://mendoza:61617?keepAlive=true&wireFormat.maxInactivityDuration=0)?initialReconnectDelay=100&randomize=false&timeout=15000
> The mendoza Linux machine has two AMQ brokers in M/S mode running on different ports. Broker configs are attached. The M/S is set up using KahaDB pointing to a NFS share on another Linux box. FYI to mount the share on mendoza I ran the following (pedro is another Linux box):
> sudo mount -o soft,intr,rsize=8192,wsize=8192 pedro:/local1 /mnt/pedro/local1
> To get this whole set up running, you'll need to change over the brokerUri in the client Program.cs to whatever host you are using and change the brokers to point to whatever NFS share you have mounted. To reproduce the failure, I had this running overnight but could see failures much earlier when I started taking down one broker at a time to start the failover process. 
> Let me know if you need any more info.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.