View Single Post
  #3 (permalink)  
Old September 15th, 2007, 05:24
jeff.depaul jeff.depaul is offline
Member
 
Join Date: Jun 2007
Posts: 37
Groans: 0
Groaned at 0 Times in 0 Posts
Thanks: 1
Thanked 8 Times in 8 Posts
Rep Power: 0
jeff.depaul is on a distinguished road
Send a message via Yahoo to jeff.depaul
Re: BPEL Server - Timeout Values for OTM

We already have the memory heap size set to 2GB so I think we are good there, but increasing the timeout definetly made a difference. In Fusion 10.1.3.3 the file name is transaction-manager.xml and the parameter is transaction-timeout="xxxx".

We had increased before from the default setting but only to around 14400 (I think we doubled it from the original default setting -twice). We were only able to process smaller volumes or ranges of deliveries with batch sizes of 10 or less. The conc req in EBS was failing with null pointer exception and we could not consistently reproduce (mixing and matching different volumes with batch sizes).

After changing the parameter above and the transaction-timeout in orion-ejb-jar.xml - we are able to process large volumes with batchsizes up to 50 deliveries (possibly more, just have not tried yet).

Also to note is that these settings got replaced (as expected) when we upgraded from 10.1.3.1 to 10.1.3.3 of Fusion. We had to go in and rest them all again after the upgrade. Changing the value of "syncMaxWaitTime" in domain.xml file had no effect as it was reset back to default upon container startup. This setting is controllable in the BPEL console manager and I guess they expect you to change it from the application side rather than at the OS level.

-jeff

Thanks again for your help.
Reply With Quote
The Following User Says Thank You to jeff.depaul For This Useful Post:
chrisplough (September 15th, 2007)