[jbossts-issues] [JBoss JIRA] Commented: (JBTM-355) Be able to configure transport timeout in com.arjuna.webservices.util.TransportTimer from some configuration file

Andrew Dinn (JIRA) jira-events at lists.jboss.org
Wed Apr 16 05:26:54 EDT 2008

    [ http://jira.jboss.com/jira/browse/JBTM-355?page=comments#action_12409069 ] 
Andrew Dinn commented on JBTM-355:

Can you please explain why the value of this timeout needs to be configured with a larger value and how this value relates to your transaction's 'size'? Also, by 'size' are you referring to the number of participants or the amount of work done by each participant?

The transport timeout is only ever employed when dispatch of a WS-C/T protocol message must wait on receipt of a corresponding protocol message. For example, the WS-AT Coordinator engine responds to a prepare request by sending a PREPARE message to the participant and then waiting for a PREPARING message to be returned in response.

Processing of the incoming message and dispatching the corresponding response will normally happen very quickly as it only involves a small amount of work on the part of the transaction system. The other variables in the equation are the communication transport delays and, in some cases, a certain amount of processing time added by the participant implementations (in the example above the participant's prepare method will be invoked). The participant may conceivably be delaying the response for more than 30 seconds. If so then this is likely to be due to an error in the participant.

> Be able to configure transport timeout in com.arjuna.webservices.util.TransportTimer from some configuration file
> -----------------------------------------------------------------------------------------------------------------
>                 Key: JBTM-355
>                 URL: http://jira.jboss.com/jira/browse/JBTM-355
>             Project: JBoss Transaction Manager
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: WS-T Implementation
>            Reporter: Pavel Kadlec
>         Assigned To: Andrew Dinn
>             Fix For: 4.4
> The timeout in com.arjuna.webservices.util.TransportTimer is fixed and as far as I know there is not possible to configure it from configuration file. 30 seconds (default value) is too short for my purposes, I have large transaction.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbossts-issues mailing list