We do this directly in the config files; make sure your admin server and managed servers are down.
At Weblogic level:
Set the global transaction JTA to 3600 seconds, be default it is 40 sec:
$DOMAIN_HOME/soa_domain/config/config.xml ... <timeout-seconds>3600</timeout-seconds> ...At SOA 11g - BPEL level: Set the sync wait time of synchrounouse processed to 120 seconds (45 by default). In the first 11g release this can be done via the file, since patch set #1 this can be done via EM going to the BPEL Manager properties.
$DOMAIN_HOME/soa_domain/config/soa-infra/configuration/bpel-config.xml ... <syncMaxWaitTime>120</syncMaxWaitTime> ...The following EJB needs to be extended on their time out. This can be done in via Enterprise Manager.
Note, that the first time it will ask you to create a Plan.xml file.
Make sure that this Plan.xml is stored in his own directory, for example: $WLS_DOMAIN/soa_domain/plan/ejb
- Log into Oracle WebLogic Administration Console.
- Click Deployments.
- Expand soa-infra -> EJBs.
- You can check in the config tab for the timeout setting in the BPEL* EJBs:
BPELEngineBean
BPELDeliveryBean
BPELActivityManagerBean
BPELServerManagerBean
BPELProcessManagerBean
BPELInstanceManagerBean
BPELFinderBean - Click Save.
- Update the soa-infra application
- Restart Oracle WebLogic Server.
4 comments:
Hi Marc,
What do you mean by "You can check in the config tab for the timeout setting in the BPEL* EJBs"
You have mentioned some Bean names but i see 3 more beans i.e-
-BPELDispatcherBean-300
-BPELTestInstanceManager-300
-BPELSensorValuesBean-120
All the BPELbeans have Transaction Timeout as 300 except for BPELSensorValuesBean which have 120
If I have syncMaxWaitTime as 45 and JTA as 300. Where all do i need to change for BPEL EJB's transaction timeout?
Regards,
HP
Great article, it solved a 300s transaction timeout I was having!!!
Same here, there is no specific documentation elsewhere for this. Thanks a lot!
Same here, there is no specific documentation elsewhere for this. Thanks a lot!
Post a Comment