You have created a SCA composite. The composite consists of a mediator which in turn calls a BPEL process. During execution when mediator calls the BPEL, the mediator is timing out before the BPEL responds
go the the following location
ORACLE_HOME/domains/user_domain_name/config/soa-infra/configuration/bpel-config.xml
and chagne the syncMaxWaitTime to some higher value.
<syncMaxWaitTime>600</syncMaxWaitTime>
If you are running a SOA composite with a large payload and getting connection time out exception.Log on to weblogic console
Go to JTA
Increase the value of Timeout,default value is 30.
Save the changes and restart the server.
This is the change you need to do in 11.1.1.1 however in 11.1.1.2 it is different
to make a change in 11.1.1.2
Log in to the EM console
http://localhost:port/em
Expand SOA and right click on soa-infra
Select SOA Administration -> BPEL Properties
Click on More BPEL Configuration Properties link
and find the syncMaxWaitTime
Change it to some higher value and save.
As in 10.1.3.x we have three time out similarly in 11g we have three time out
one syncmaxwaitTime out that we have checked right now
Another is done at mbean level and the third one is JTA transaction time out.
Again it holds a realation ship that
synMaxWaitTime < mbean timeout < JTA transaction time out
synMaxWait time out is at process level
mbean is at application level and
JTA is for container level.
For mbean time out
log in to console
http://host:port/console
select deployment
find soa-infra and expand it
again find there /soa-infra
click on configuration tab and change the session timeout.
For JTA time out
Expand the services in the domain structure
and find JTA
click on jta and find time out there change it and resrart the server to make all these changes
No comments:
Post a Comment