[
http://jira.jboss.com/jira/browse/JBTM-355?page=comments#action_12409631 ]
Pavel Kadlec commented on JBTM-355:
-----------------------------------
i.) I am using Oracle Database 10g.
i.) In stateless session bean I create entity manager (per session bean call) by entity
manager factory. Then I persist entities (250 entities per one stateless session bean
call). In finally block I ONLY close entity manager.
There will no problem for me to flush, clear and finally close entity manager instead of
only closing.
You are correct, prepare phase is MUCH more faster (in milliseconds) with flushing done
during the business process and not only at the end of the process (at the commit of the
transaction)
Thank you very much for your help, time and great description of the possible solutions.
I think that this feature request can be rejected.
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