[
https://issues.apache.org/activemq/browse/AMQNET-89?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=45076#action_45076
]
Jim Gomes commented on AMQNET-89:
---------------------------------
Changing the implementation to allow setting RequestTimeout properties
individually on the IConnection, ISession, and IMessageProducer objects. The
default initialization will come from the transport setting. For instance, the
IConnection object will be initialized with the ITransport RequestTimeout
setting. The ISession object will be initialized with the IConnection's
setting. the IMessageProducer object will be initialized with the ISession's
setting. After the objects are created, they will have their own independent
RequestTimeout settings. For instance, if I create an IMessageProducer, and
then change the ISession's RequestTimeout setting, the previously created
IMessageProducer will not use the newly set RequestTimeout for the ISession.
> Allow the transport's request timeout to be set on a single-call basis
> without changing default timeout.
> --------------------------------------------------------------------------------------------------------
>
> Key: AMQNET-89
> URL: https://issues.apache.org/activemq/browse/AMQNET-89
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ Client
> Affects Versions: 1.0
> Environment: .NET 2.0, Windows XP, ActiveMQ 5.1.0
> Reporter: Jim Gomes
> Assignee: Jim Gomes
> Priority: Minor
> Fix For: 1.0
>
> Original Estimate: 1 hour
> Time Spent: 1 hour, 45 minutes
> Remaining Estimate: 0 minutes
>
> The timeout value for the transport layer can be set on the connection URI.
> However, sometimes it is valuable to programmatically override this default
> on a single call to Request().
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
