[
http://jira.jboss.com/jira/browse/JBTM-355?page=comments#action_12409554 ]
Pavel Kadlec commented on JBTM-355:
-----------------------------------
I am referring to the amount of work done by each participant. I use modified version of
transaction bridging done by jhalliday
(
http://anonsvn.labs.jboss.com/labs/jbosstm/workspace/jhalliday/txbridge/s...).
The participant is JTA transaction.
I am persisting through entity manager 500 000 entities in one transaction, so prepare
phase can take quite long. In my case it's 1 minute when I have table with no indexes.
If I have table with a lot of indexes, prepare phase takes 6 hours.
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