Exception thrown in TcpTransport while using failover protocol
--------------------------------------------------------------
Key: AMQNET-171
URL: https://issues.apache.org/activemq/browse/AMQNET-171
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ Client
Affects Versions: 1.2
Environment: Windows XP SP2 Framework 2.0
Reporter: Michel Van Hoof
Assignee: Jim Gomes
While doing some tests i noticed an error being thrown even though i use the
failover protocol. The exception was:
Apache.NMS.ActiveMQ.BrokerException: System.InvalidOperationException: Error
writing to broker. Transport connection is closed.
at Apache.NMS.ActiveMQ.Transport.Tcp.TcpTransport.Oneway(Command command) in
d:\Hudson\jobs\Apache.NMS.ActiveMQ
Trunk\workspace\src\main\csharp\Transport\Tcp\TcpTransport.cs:line 118 :
Transport connection error: Error writing to broker. Transport connection is
closed.
at Apache.NMS.ActiveMQ.Transport.ResponseCorrelator.Request(Command command,
TimeSpan timeout) in d:\Hudson\jobs\Apache.NMS.ActiveMQ
Trunk\workspace\src\main\csharp\Transport\ResponseCorrelator.cs:line 105
at Apache.NMS.ActiveMQ.Connection.SyncRequest(Command command, TimeSpan
requestTimeout) in d:\Hudson\jobs\Apache.NMS.ActiveMQ
Trunk\workspace\src\main\csharp\Connection.cs:line 338
at Apache.NMS.ActiveMQ.Session.DoSend(Command message, TimeSpan
requestTimeout) in d:\Hudson\jobs\Apache.NMS.ActiveMQ
Trunk\workspace\src\main\csharp\Session.cs:line 484
at Apache.NMS.ActiveMQ.MessageProducer.Send(IDestination destination,
IMessage message, MsgDeliveryMode deliveryMode, MsgPriority priority, TimeSpan
timeToLive, Boolean specifiedTimeToLive) in d:\Hudson\jobs\Apache.NMS.ActiveMQ
Trunk\workspace\src\main\csharp\MessageProducer.cs:line 181
at Apache.NMS.ActiveMQ.MessageProducer.Send(IDestination destination,
IMessage message) in d:\Hudson\jobs\Apache.NMS.ActiveMQ
Trunk\workspace\src\main\csharp\MessageProducer.cs:line 115
Connectionstring: "failover:(tcp://myhostname:xxxx)"
I have no clue WHY it was thrown (since other messages did get sent as they
should)
I have been looking at where the response is thrown but since the code is
virtually commentless, it's not really easy to follow the rabbit down the hole
:s
Looking at it, the issues happend when a connection error occured when the
producer was waiting/excepting a response that his message has been received by
the broker...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
