The DB procedure is executing fine and i am able to view the audit trail in DB. We have identified that the problem is directly with DB hit. It dint proceed to wait activity stage. We even changed(increased the value of) some of the adapter properties in console like
JTA:- Timeout Seconds,Checkpoint Interval Seconds
Data Source :-Test Frequency Seconds,Statement Cache Size,Shrink Frequency ,Connection Reserve Timeout and bounced the server
But still we get Transaction rolled out error.
Is it a synchronous BPEL process? It is not recommended to have asynchronous activities inside a synchronous process...
I think you will have increase every timeout configuration in order to support a wait of 10 minutes... I could say that this wait activity is probably not the best design, but I don't know your use case...
Adding to the above conversation, Our SOA version is 184.108.40.206 ; Actually 10 mins Wait is placed after the DB call , but didn't come to the Wait step itself. DB response may come approximately in 9mins time and our Transaction failed after 300 seconds(5mins). DB adapter configured as Non-XA and Not supporting for Global transactions. Below is the diagnostic log for your reference.
ORABPEL-02183 JTA transaction is not in active state.
[2014-06-03T10:54:27.095-07:00] [xxxxxx_server1] [ERROR]  [oracle.soa.bpel.engine.dispatch] [tid: orabpel.engine.pool-6.thread-7] [userId: <anonymous>] [ecid: 0bc183a572cd738c:-1f57e9ca:146613b0b68:-8000-0000000898900cb94,0] [APP: soa-infra] failed to handle message[[
weblogic.transaction.internal.TimedOutException: Transaction timed out after 300 seconds
Is it related to any BPEL engine property changes?
As per SOA governance, SOA is meant to handle the real-time scenarios, not the 10 min wait scenarios. If any case, SOA services needs to wait, it can wait for seconds(=JTA seconds) not this much(10 mins) number of minutes. this is not a good design. If you would be able to achieve this in coming days by setting its BPEL transaction properties, it will hang up you server, if number of concurrent transactions waiting for it.
Best practice says: We should tune our server to its minimum delays and maximum memory, not with maximum delay and minimum memory.
As you are interacting with the database you need to maintain the time frame which has given by Oracle SOA JTA transaction.
If at all you need this type of wait scenarios you can manually increase the JTA transaction timeout to 3600 sec.
Below are the steps to increase JTA transaction timeout in Weblogic
1.Log on to Weblogic console
2. Go to JTA tab (This can be found under services-->JTA)
3. Change the Timeout seconds to 3600 (Default it would be 300 sec)
Hope this should resolve your issue.