Effective October 27, 2012, online and email support for FuseSource products will move to Red Hat support channels. For more information, please see the JIRA Migration to Red Hat FAQ.
As of October 27th, please open all new issues in the Red Hat Customer Portal .
Issue Details (XML | Word | Printable)

Key: MBNET-1
Type: Support Request Support Request
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Unassigned
Reporter: Adrian Trenaman
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Forge: FUSE MB: .NET Client

NMS-ERROR Unknown Response ID messages on failover

Created: 26/May/10 09:18 AM   Updated: 26/May/10 03:19 PM
Component/s: None
Affects Version/s: None
Fix Version/s: None

Environment: C# .Net client using NMS 1.3.0


 Description  « Hide
We've observed a number of 'Unknown Response ID' errors in NMS clientside logs on reconnection after failover (see below). It loos like this might be related to issue AMQNET-246 on Apache. We're currently using Apache NMS 1.3.0.

If these messages can be ignored, can we change the error level to DEBUG or INFO?

2010-05-20 12:46:40.474 	57	  	-2	Warn 	NMS-ERROR	[NMS] Transport failed to 
tcp://<MACHINE-IP>:8520/?keepAlive=true&nbsp;wireFormat.maxInactivityDuration=0&nbsp;jms.prefetchPolicy.all=1, attempting to automatically reconnect due to: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period 
of time, or established connection failed because connected host has failed to respond.
2010-05-20 12:46:40.489 	9	  	-2	Info 	NMS-ERROR	[NMS] Restoring previous transport connection.
2010-05-20 12:46:40.521 	9	  	-2	Info 	NMS-ERROR	[NMS] Sending queued commands...
2010-05-20 12:46:40.521 	9	  	-2	Info 	NMS-ERROR	[NMS] Successfully reconnected to: 
tcp://<MACHINE-IP>:8520/?keepAlive=true&nbsp;wireFormat.maxInactivityDuration=0&nbsp;jms.prefetchPolicy.all=1
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 1 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 2 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 7 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 3 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 6 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 4 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 5 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 8 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 14 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 535 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 6044 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 6046 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 6048 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 6051 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 6074 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 6082 ]
2010-05-20 12:46:40.521 	104	  	-2	Error 	NMS-ERROR	[NMS] Unknown response ID: 0 for response: Response[ commandId = 0, responseRequired = False, CorrelationId = 12748 ]

 All   Comments   Change History      Sort Order: Ascending order - Click to sort in descending order
[ Permlink | « Hide ]
Timothy Bish added a comment - 26/May/10 12:33 PM
Since AMQNET 246 was resolved this shouldn't be an issue in v1.3.0. Recommend that an issue at Apache Jira be opened with a sample application and instructions on how to reproduce the error.

[ Permlink | « Hide ]
Adrian Trenaman added a comment - 26/May/10 03:14 PM
Thanks Timothy,

On requesting further information from the customer, it emerged that they were in fact using 1.2.0 at the time the test was run.

I'm closing this issue for now; we can reopen if the customer reproduces on 1.3.0.

Best,
Ade.


[ Permlink | « Hide ]
Timothy Bish added a comment - 26/May/10 03:19 PM
Ah, that would explain it, was wondering if there might be a version mix up. This should not occur when using 1.3.0, if it does let me know.


Powered by Atlassian JIRA the Professional Issue Tracker. (Enterprise Edition, Version: 3.13.2-#335) - Bug/feature request - Atlassian news - Contact Administrators