I have a service is set for a 45 second timeout.

It's been timing out today after 15 seconds and I don't get to catch the timeout, application just hangs up on me.

In data node it's inside a try catch * block.

What is your "fetchtimeout"? If that is shorter than the WS timeout the Voice Browser will get a timeout. Was there any trace?

fetchtimeout is default, that's it I believe. However that doesn't explain why I don't get to catch or process the timeout.

referral_fe answers phone execs cbc_referral_facets which does the wsop which times out, see between Web Service Request and Finished

10/06/2014 08:57:59:718 INFO - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : Calling method
10/06/2014 08:57:59:718 DEBUG - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : Collecting [connectivity.ws.beans.referral.IVRReferralStub$ReferralSubmission@1997f158] from:referralSubmission
10/06/2014 08:57:59:718 DEBUG - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : Web Service Request ->
10/06/2014 08:58:14:647 INFO - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : Using SCESession 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe servlet : Finished
10/06/2014 08:58:14:662 DEBUG - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : *** Reply for [/cbc_referral_facets/Finished] ***
10/06/2014 08:58:14:662 DEBUG - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : 0:<?xml version="1.0" encoding="UTF-8"?>
1:<vxml version="2.1" xmlns="http://www.w3.org/2001/vxml" xml:lang="en-us">
2:<meta name="author" content="Avaya Aura Orchestration Designer"/>
3:<meta name="runtime-version" content="06.00.11.06.p4"/>
4:<meta name="runtimecommon-version" content="06.00.11.06"/>
5:<meta name="runtime-hotfixes" content="wi1087784, wi01048783"/>
6:<meta name="copyright" content="Copyright (c) 2002-2011, Avaya"/>
7:<form id="Finished">
8:<block>
9:<return/>
10:</block>
11:</form>
12:</vxml>
13:

10/06/2014 08:58:14:709 INFO - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : Using SCESession 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe servlet : Finished
10/06/2014 08:58:14:709 INFO - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : ** Popped Stack Frame [/cbc_referral_facets]
10/06/2014 08:58:14:709 DEBUG - 4F0398CCC63E21A935CE27FD87BE15F4:/referral_fe : Not able to save posted variable information [ReferralFacets]

Was the trace edited? It looks odd.

Yeah, took out the web request information, had some personal information in it.

can you email or "private" mesage the unedited trace? There is nothing I can tell from what is posted.

Thanks I got the trace. Does your application catch error.badfetch? I am not seeing any error in the actual web service or a reply. So it looks like you get a fetchtimeout from the Voice Browser and proceed to the finish node.

I would expect a bit later in the trace to see something like:

*** Abandoning thread sessionid [...]

about 45 seconds later in the trace.log or catalina.out.

Abandoning thread sessionid is present in the catalina.out file.

Application appears to act funny because it's badfetch app root handler just returns with no announcement...

Okay the thing to do is to add a property to the application and increase the fetchtimeout. I there was not enough trace to comment about the handling of badfetch (i.e. the vxml that is generated). If you increase the fetchtimeout you might want to have a transitional prompt (usually music) that starts playing if the fetch takes more than N seconds.