Multiple RequestTimeout Options in NMS.ActiveMQ causes option to not work when
used with Failover.
--------------------------------------------------------------------------------------------------
Key: AMQNET-259
URL: https://issues.apache.org/activemq/browse/AMQNET-259
Project: ActiveMQ .Net
Issue Type: Bug
Components: ActiveMQ
Affects Versions: 1.3.0, 1.2.0
Reporter: Timothy Bish
Assignee: Jim Gomes
Priority: Minor
Fix For: 1.4.0
NMS.ActiveMQ has several different places where a RequestTimeout option is able
to be configured. The one in the Transport layer severs no real purpose any
more and can lead to confusion as its not able to be set correctly when the
FailoverTransport is used as the layering of Transports hides the value. The
Connection object has its own RequestTimeout and should be the only one we need
as it is used to set the value for the Session and Producer classes.
I'd like to remove the RequestTimeout option from the Transports layer
altogether since the timeout is actually specified in the request call that
takes a timeout option.
Also the current ConnectionFactory doesn't properly configure the
Connection.RequestTimeout if set on the URI, this should be fixed here as well.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
