[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)]

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

I'm still not convinced that configuring this timeout is the correct thing to do. Can you explain i) which database you are using and ii) what your code is doing in the prepare call?

I am assuming that this problem arises because entities created in your subordinate TX only get flushed at prepare time due to the delegation involved in bridging. The persistence manager install a Syncrhonization to flush cached SQL updates to the database. This normally runs before the 2PC is entered but with bridging the flush cannot be performed (i.e. the Synchronization cannot be executed) until the delegated prepare arrives which stalls the parent TX.

One possibility might be for you to manually flush changes inside your EJB code as you make them. This should leave little or no work to do at prepare time because the DB updates will already be out on disk. Can you try this?

Another option might be to do break the create operations into lots of little transactions. Do you have to do this update all in one go?

Anyway leaving these questions aside for the moment, if you want to reset the timeout you can easily do so by invoking TransportTimer.setTransportTimeout(long) from your application code.


> 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