OTN Discussion Forums : Connection Timeout in Call of external ...

edmundo

Posts: 47
Registered: 07/04/06

Connection Timeout in Call of external Sync WS
Posted: Aug 15, 2007 3:13 AM

Hi!

I have a asynchronous web service call (<invoke>) to an external web service.

So, I have trouble with connection timeout.
I add timeout property to partnerlink and set value of this property to 30 seconds.
But this property doesn't work, because the status of the instance after 30 seconds is active. I try to change timeout to 60 seconds, but it also doesn't work.

Anybody can help me??

edmundo

Posts: 47
Registered: 07/04/06

Re: Connection Timeout in Call of external Sync WS
Posted: Aug 15, 2007 3:27 AM

in response to: edmundo

Reply

I also tried other way.... to create connection timeout.

I added Scope activity. then I put Invoke activity into scope activity.

then to scope activity I added onAlarm branch.

So, this construction works. But it's not automatically. I need to "Refresh Alarm Table" in BPEL Console to stop active intstancies.

Is there anyway to "Refresh Alarm Table" automatically???

Thank You.

P.S. Sorry for my English

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Sep 10, 2008 8:34 AM

in response to: edmundo

Reply

Hi,
Does anyone have another solution for this problem?
I'm running 10.1.3.3.0 and this I think is unacceptable on a product such as this.
Is there any working automatic workaround?

Thanks,
Alex

Buddy@Kolkata

Posts: 33
Registered: 02/01/07

Re: Connection Timeout in Call of external Sync WS
Posted: Sep 10, 2008 9:21 AM

in response to: edmundo

Reply

Hi

Hope the following links would be helpfull

http://dietrichschroff.blogspot.com/2008/03/bpel-timeout-behaviour-of-synchronous.html
http://soastuff.wordpress.com/2007/05/24/synchronous-bpel-processes-and-timeout-errors

Thanks

Buddhadev

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Sep 11, 2008 12:25 AM

in response to: Buddy@Kolkata

Reply

Hi,
The only problem on those 2 solutions is that they are intended to the Oracle Application Server.
I'm running BPEL on weblogic 9.2, so the configuration files reference on those articles are not valid for my env.

Thanks
Alex

Riko

Posts: 118
Registered: 03/04/07

Re: Connection Timeout in Call of external Sync WS
Posted: Sep 11, 2008 12:32 AM

in response to: AlexCosta

Reply

Alex,

Must you wait for the WS to finish or you can continue with the process?

Riko

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Sep 11, 2008 2:50 AM

in response to: Riko

Reply

Hi,
it's a blocking sync call.

thanks

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Dec 3, 2008 12:47 AM

in response to: AlexCosta

timeout , bpel , weblogic

Reply

Hi,
I can't believe that nobody knows how to increase this parameter in a WL 9.2 / BPEL 10.1.3.3 installation.
After all it's a official supported platform and yet, a standard configuration feature like this one is, apparently, forgotten by Oracle.

On my project i have to invoke a external Sync Webservice with the timeout defined of 5min. I do not see any possible workaround for this problem.

thanks,
Alex

mmebag

Posts: 6
Registered: 09/30/08

Re: Connection Timeout in Call of external Sync WS
Posted: Dec 3, 2008 8:31 AM

in response to: AlexCosta

Reply

Alex, on BPEL console there on admin
there is a parameter that's is call maxSyncWaitTime, there express the the time in second if you need to wait 5 minutes you must to define to 300, also check the parameter of time-out of transaction-manager.xml of the instance where BPEl is deploy

Hope it helps

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Dec 3, 2008 8:38 AM

in response to: mmebag

Reply

Hi,
I already try to change the maxSyncWaitTime with no effect.
The transaction-manager.xml from what i've been told is not used in the weblogic instalation.

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Dec 3, 2008 8:40 AM

in response to: AlexCosta

Reply

Plus, the value on the file is set to:
transaction-timeout="30"

I'm getting timeouts around 120 secs.

thanks,

mmebag

Posts: 6
Registered: 09/30/08

Re: Connection Timeout in Call of external Sync WS
Posted: Dec 3, 2008 10:31 AM

in response to: AlexCosta

Reply

so where did you find out that xml, transaction time out manage the JTA transacction, so can you try setting up above 120 maybe 150 an restart services

Also my personal opinion is that 120 secons is too much for a syn service, i think even 40 sec is too much, sync must be faster if not, then make an async call
the problem is that external ws must be async

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Dec 4, 2008 12:39 AM

in response to: mmebag

Reply

Hi,
The file is located in the standalone bpel installation that is required on the WL installations.
Specifically: /ora102/product/10.1.3.1/OraBPELWL/bpel/system/appserver/oc4j/j2ee/home/config

AlexCosta

Posts: 68
Registered: 01/27/06

Re: Connection Timeout in Call of external Sync WS
Posted: Dec 15, 2008 4:00 AM

in response to: edmundo

Reply

Hi,
I got it working.
Here is the list of changes:
WL 9.2:
Services > JTA from the left pane.
Set JTA attributes in the right pane "Timeout Seconds" = 340
Maximum Duration of XA Calls: 340000
Services -> JDBC -> DataSources -> BPELServerDataSource -> Configuration -> transaction
"XA Transaction Timeout" - 340
"Set XA Transaction Timeout" - Active

BPEL Domain:
Change the value of the syncMaxWaitTime - 300

Transaction Change
1. Go to bea\user_projects\apps\soaApps\BPELPM and make a backup of ejb_ob_engine.jar (if anything goes wrong just put back the original ejb_ob_engine.jar)
2. Open the JAR in WinZip and edit weblogic-ejb-jar.xml
3. Change the <trans-timeout-seconds> from 120 to 300 seconds for example for the following Beans : CubeEngine, CubeDelivery and MessageBean
4. Save XML and repack the JAR
5. Go to Weblogic Console -> Deployments and Lock&Edit
6. Select BPELPM and Update it -> this will force a redeployment of the JARs
7. Click Activate Changes (at this steps there might be some errors in Weblogic Console but after step 8 there will be no problems )
8. Stop the SOA server and start it again .

Hope this help you guys.
Alex