Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- Technology and Support
- DevNet
- DevNet Collaboration
- Collaboration Knowledge Base
- Fetchtimeout in custom action element
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
1905
Views
0
Helpful
0
Comments
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 01-25-2014 10:38 AM
This document was generated from CDN thread
Created by: Asher Schweigart on 26-03-2013 01:38:37 PM
I have a custom element that pulls some information using XML http requests, and it is causing CVP to throw a "error.badfetch".
Running the same element in the debugger throws no such error, but it does take a long time to continue, so I am wondering if it is a voicexml timeout issue.
From what I have read in other posts, I should be able to set the fetchtimeout vxml property on my custom action element. I don't see the normal pane to do that in CS, so I am thinking I should do it in the java code? How would I do this in java?
Subject: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 26-03-2013 02:26:50 PM
Asher, the fetchtimeout timer is only for the gateway when it's waiting for another vxml page. Your error.badfetch is being generated by VxmlServer. I don't know if you can customize VxmlServer (Tomcat) to tell it how long to wait for response. Someone at Cisco would have to help you with this. Or maybe you could do it inside your java by setting an http fetch timeout property for tomcat. -- Janine Graves
Subject: RE: Fetchtimeout in custom action element
Replied by: Sidney Orret on 26-03-2013 02:45:24 PM
First thing I would ask about your custom VXML element is from where the XML http request is being issued. From the VXML Server or from the Voice GW?
Is the VXML Server acting as middleware (as it does with the database element) or is letting the voice browser to talk directly to the XML provider (like it does for example with TTS audio)?
Subject: RE: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) -
Replied by: Sidney Orret on 26-03-2013 02:50:54 PM
Janine, you got me confused here as I would expect the error.badfetch thrown by the GW. I see error.badfetch on the VXML GW on instances when for examples audio files are missing or the url is incorrect. Am I missing something?
Subject: RE: Fetchtimeout in custom action element
Replied by: Shikha Sharma on 26-03-2013 03:29:33 PM
You can put an audio element just before your custom action element and set following vxml properties:
fetchtimeout
fetchaudio(if you want to play music while waiting for xml response)
This approach works for our webservice calls.
Subject: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - General
Replied by: Janine Graves on 26-03-2013 03:31:50 PM
Sidney,
It turns out that the VXML gateway and Vxml Server can both throw
error.badfetch events. It depends on who is making the http request. I
was surprised when the Vxml Server did this, but live and learn!
And, unfortunately, the VXML Property 'fetchtimeout' - only changes the
timer on the gateway side. I don't know how to tell VxmlServer to wait
longer than x seconds for a response. I also don't know what the default
time period is, or whether you can configure it.
When I used to teach for Audium, they told me that Vxml Server can make
http requests (for example, in the element named 'Action' - you can
select URI - and enter a URI to connect to a separate server and execute
some web app on that server. This is called the XML API - it's discussed
in the CVP Programming Guide).
Anyway, to make a long story short, for that http request VxmlServer has
a HARD CODED 5-second timeout to receive back the response. It's not
configurable. And I tend to think this is the case for Asher's scenario.
BUT - it sure would be nice if someone from Cisco could chime in. Paul
Tindall - can you help???
Subject: RE: New Message from Janine Graves in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 26-03-2013 03:38:50 PM
That is correct. I still see random and infrequent error.badfetch which even Cisco has been unable to nail down exactly. I suspect something on the gateway. One should monitor the gateway CPU utilization when this happens. I know for a fact that when it spikes and gets close to 100% you will get a bunch of these errors.
If it happens frequently you can def nail it down, however if it is rare and infrequent then your job it will require some debugging and setting debugs in prod to trace it down.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, March 26, 2013 3:32 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Janine Graves in Customer Voice Portal (CVP) - General Discussion - All Versions: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - General
Janine Graves has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Sidney,
It turns out that the VXML gateway and Vxml Server can both throw
error.badfetch events. It depends on who is making the http request. I
was surprised when the Vxml Server did this, but live and learn!
And, unfortunately, the VXML Property 'fetchtimeout' - only changes the
timer on the gateway side. I don't know how to tell VxmlServer to wait
longer than x seconds for a response. I also don't know what the default
time period is, or whether you can configure it.
When I used to teach for Audium, they told me that Vxml Server can make
http requests (for example, in the element named 'Action' - you can
select URI - and enter a URI to connect to a separate server and execute
some web app on that server. This is called the XML API - it's discussed
in the CVP Programming Guide).
Anyway, to make a long story short, for that http request VxmlServer has
a HARD CODED 5-second timeout to receive back the response. It's not
configurable. And I tend to think this is the case for Asher's scenario.
BUT - it sure would be nice if someone from Cisco could chime in. Paul
Tindall - can you help???
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535547 or simply reply to this email.
Subject: Re: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Janine Graves on 26-03-2013 03:42:51 PM
Nope, that won't work in Asher's case. The fetchtimeout timer tells the
Gateway not to time out while waiting for the next VXML page.
BUT - if it is the VXML Server is making an http request of a back-end
system, and if that's timing out, the Vxml Server doesn't obey the
fetchtimeout timer. It would have to be done (somehow) in the java code.
Subject: RE: Fetchtimeout in custom action element
Replied by: Asher Schweigart on 26-03-2013 03:53:12 PM
The element is a middleware element; I am fetching the information for a ticket in our helpdesk system and then routing the call based on that ticket.
So am I understanding you correctly Janine, I cannot set the fetchtimeout timer for this element in CS at all? I believe that means I can't set it in java either, right?
So to make this element not fail, I'll have to figure out how to make the element stop processing and exit before the 5 seconds is up. Not quite sure how to do that yet, but I think I can make that work.
Subject: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 26-03-2013 03:56:51 PM
Oops, Asher I just re-read your post. Since your debugger works but in production it doesn't - then it DOES sound like the vxml gateway is throwing the error.badfetch. And, in that case, as Shikha suggested, use the audio element just before this slow step, you can set the voicexml property in the Settings tab - set fetchtimeout to 60s (or whatever). And set the fetchaudio to a URI of filler music to play to the caller. Sorry for the confusion - but I thought your Vxml Server was throwing error.badfetch (which can occur). On 3/26/2013 1:38 PM, Cisco Developer Community Forums wrote: Asher Schweigart has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- I have a custom element that pulls some information using XML http requests, and it is causing CVP to throw a "error.badfetch". Running the same element in the debugger throws no such error, but it does take a long time to continue, so I am wondering if it is a voicexml timeout issue. From what I have read in other posts, I should be able to set the fetchtimeout vxml property on my custom action element. I don't see the normal pane to do that in CS, so I am thinking I should do it in the java code? How would I do this in java? -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13530941 or simply reply to this email. -- Janine Graves
Subject: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 26-03-2013 04:03:50 PM
Wow, the forum is doing weird things. Posting replies 3x.
Subject: RE: Fetchtimeout in custom action element
Replied by: Shikha Sharma on 26-03-2013 04:14:21 PM
To me, this particular issue sounds like a simple case of Gateway timing out while VXML server is waiting for XML response as indicated by the delay on particular element step and this type of issue can easily be resolved by either setting fetchtimeout on global application level or on individual element level( audio element configured with fetchaudio in this case). Its interesting to know about vxml server timeout as I personally have never experienced one so far even while calling external APIs or backend system with response time of more than 30 seconds.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: GEOFFREY THOMPSON on 26-03-2013 04:35:50 PM
I have not had any problem with fetchaudio working correctly while the back end takes a while to process. It seemed to work perfectly for me. I put sleeps into the back end to simulate a delay and I can’t recall it playing up. It seemed to follow what the standard said.
Regards,
Geoff
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Paul Tindall on 27-03-2013 04:39:09 AM
Not sure I can help much but I can confirm the built-in back-end HTTP request doesn't give you any flexibility in terms of request timeout, security etc. You will have to code your own HTTP request in a custom action/decision element to get a longer timeout.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 27-03-2013 06:54:50 AM
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, March 26, 2013 3:30 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties:
fetchtimeout
fetchaudio(if you want to play music while waiting for xml response)
This approach works for our webservice calls.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Asher Schweigart on 27-03-2013 04:45:34 PM
That is what I've done, I have a custom action element that does the http request:
URL url = new URL("URL_that_returns_XML);
URLConnection conn = url.openConnection();
conn.setRequestProperty("Authorization", "Basic "+cred);
conn.connect();
InputStream sn = conn.getInputStream();
So maybe the timeout is not what is causing the error.
This is what the logs said:
10.255.60.88.1364318999643.19285.HD_start,03/26/2013 13:32:03.299,A VoiceXML error occurred of type "error.badfetch"
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:14.533,A VoiceXML error occurred of type "error.badfetch"
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:41.265, The error was: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
com.audium.server.MultipleThreadException: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
Subject: RE: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: GEOFFREY THOMPSON on 27-03-2013 04:56:11 PM
When working with custom elements that do something serious, you should not rely on the activity log. You will sometimes get a “badfetch” as a result of an exception in your own code.
I always put in low level tracing to a file (named with date/time appended so each execution is in its own file) in C:\temp that I can turn off or on in the custom element with a Boolean flag – in Settings[]
During the development I have this set to true, and details I need to figure out what’s going on are in that file. When it’s ready, I can turn it off at the application level.
If you put in System.println they will appear in Tomcat\logs\stdoutXXX.log, but then you have to recompile to take them out.
Regards,
Geoff
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Shikha Sharma on 01-04-2013 12:15:44 PM
This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 01-04-2013 12:23:30 PM
That is obvious for fetchimeout. However you will also need to tune your web service timeout if your webservice is taking long time . If not you will see socket read timeout on Tomcat.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Monday, April 01, 2013 12:16 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Hemal Mehta:
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, March 26, 2013 3:30 PM To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com> Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties: fetchtimeout fetchaudio(if you want to play music while waiting for xml response) This approach works for our webservice calls. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13734378 or simply reply to this email.
Subject: RE: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General D
Replied by: Shikha Sharma on 02-04-2013 11:24:01 AM
Nope you won't receive any socket exception if you set proper timeout in your WS client code or you can always configure timeouts in tomcat. Webservices are usually maintained by cross functional teams and hence one does not always have control on their response time especially if the servers hosting them are old or running slow. Also, the issue here is related to badfetch and not Read timeout exception is a separate discussion altogether.
--------- Original Message ---------Subject: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
From: Cisco Developer Community Forums <cdicuser@developer.cisco.com>
Date: 4/1/13 12:23 pm
To: "cdicuser@developer.cisco.com" <cdicuser@developer.cisco.com>
Hemal Mehta has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- That is obvious for fetchimeout. However you will also need to tune your web service timeout if your webservice is taking long time . If not you will see socket read timeout on Tomcat.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Monday, April 01, 2013 12:16 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Hemal Mehta:
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, March 26, 2013 3:30 PM To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com> Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties: fetchtimeout fetchaudio(if you want to play music while waiting for xml response) This approach works for our webservice calls. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13734378 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13736246 or simply reply to this email.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 02-04-2013 11:34:01 AM
That is what I am saying. Read
“However you will also need to tune your web service timeout if your webservice is taking long time”
Tuning and setting proper timeout are the same…
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, April 02, 2013 11:24 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General D
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Nope you won't receive any socket exception if you set proper timeout in your WS client code or you can always configure timeouts in tomcat. Webservices are usually maintained by cross functional teams and hence one does not always have control on their response time especially if the servers hosting them are old or running slow. Also, the issue here is related to badfetch and not Read timeout exception is a separate discussion altogether.
--------- Original Message ---------Subject: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
From: Cisco Developer Community Forums <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Date: 4/1/13 12:23 pm
To: "cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>" <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Hemal Mehta has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- That is obvious for fetchimeout. However you will also need to tune your web service timeout if your webservice is taking long time . If not you will see socket read timeout on Tomcat.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Monday, April 01, 2013 12:16 PM
To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Hemal Mehta:
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, March 26, 2013 3:30 PM To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com%3cmailto:cdicuser@developer.cisco.com>> Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties: fetchtimeout fetchaudio(if you want to play music while waiting for xml response) This approach works for our webservice calls. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13734378 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13736246 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13773458 or simply reply to this email.
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Shikha Sharma on 02-04-2013 11:51:18 AM
Put this code code under try catch block and print out errors in tomcat for the time being. You may also want to check if you are realeasing resources properly with sn.close(); statement in the end.
Subject: RE: Fetchtimeout in custom action element
Replied by: Janine Graves on 09-04-2013 05:25:02 PM
Hi Asher,
Did you ever find the cause of this problem?
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 09-04-2013 05:27:02 PM
Actually, did you find the cause/solution to this problem?
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:41.265, The error was: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
com.audium.server.MultipleThreadException: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
Created by: Asher Schweigart on 26-03-2013 01:38:37 PM
I have a custom element that pulls some information using XML http requests, and it is causing CVP to throw a "error.badfetch".
Running the same element in the debugger throws no such error, but it does take a long time to continue, so I am wondering if it is a voicexml timeout issue.
From what I have read in other posts, I should be able to set the fetchtimeout vxml property on my custom action element. I don't see the normal pane to do that in CS, so I am thinking I should do it in the java code? How would I do this in java?
Subject: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 26-03-2013 02:26:50 PM
Asher, the fetchtimeout timer is only for the gateway when it's waiting for another vxml page. Your error.badfetch is being generated by VxmlServer. I don't know if you can customize VxmlServer (Tomcat) to tell it how long to wait for response. Someone at Cisco would have to help you with this. Or maybe you could do it inside your java by setting an http fetch timeout property for tomcat. -- Janine Graves
Subject: RE: Fetchtimeout in custom action element
Replied by: Sidney Orret on 26-03-2013 02:45:24 PM
First thing I would ask about your custom VXML element is from where the XML http request is being issued. From the VXML Server or from the Voice GW?
Is the VXML Server acting as middleware (as it does with the database element) or is letting the voice browser to talk directly to the XML provider (like it does for example with TTS audio)?
Asher Schweigart:I have a custom element that pulls some information using XML http requests, and it is causing CVP to throw a "error.badfetch".
Running the same element in the debugger throws no such error, but it does take a long time to continue, so I am wondering if it is a voicexml timeout issue.
From what I have read in other posts, I should be able to set the fetchtimeout vxml property on my custom action element. I don't see the normal pane to do that in CS, so I am thinking I should do it in the java code? How would I do this in java?
Subject: RE: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) -
Replied by: Sidney Orret on 26-03-2013 02:50:54 PM
Janine, you got me confused here as I would expect the error.badfetch thrown by the GW. I see error.badfetch on the VXML GW on instances when for examples audio files are missing or the url is incorrect. Am I missing something?
Janine Graves:Asher, the fetchtimeout timer is only for the gateway when it's waiting for another vxml page. Your error.badfetch is being generated by VxmlServer. I don't know if you can customize VxmlServer (Tomcat) to tell it how long to wait for response. Someone at Cisco would have to help you with this. Or maybe you could do it inside your java by setting an http fetch timeout property for tomcat. -- Janine Graves
Subject: RE: Fetchtimeout in custom action element
Replied by: Shikha Sharma on 26-03-2013 03:29:33 PM
You can put an audio element just before your custom action element and set following vxml properties:
fetchtimeout
fetchaudio(if you want to play music while waiting for xml response)
This approach works for our webservice calls.
Subject: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - General
Replied by: Janine Graves on 26-03-2013 03:31:50 PM
Sidney,
It turns out that the VXML gateway and Vxml Server can both throw
error.badfetch events. It depends on who is making the http request. I
was surprised when the Vxml Server did this, but live and learn!
And, unfortunately, the VXML Property 'fetchtimeout' - only changes the
timer on the gateway side. I don't know how to tell VxmlServer to wait
longer than x seconds for a response. I also don't know what the default
time period is, or whether you can configure it.
When I used to teach for Audium, they told me that Vxml Server can make
http requests (for example, in the element named 'Action' - you can
select URI - and enter a URI to connect to a separate server and execute
some web app on that server. This is called the XML API - it's discussed
in the CVP Programming Guide).
Anyway, to make a long story short, for that http request VxmlServer has
a HARD CODED 5-second timeout to receive back the response. It's not
configurable. And I tend to think this is the case for Asher's scenario.
BUT - it sure would be nice if someone from Cisco could chime in. Paul
Tindall - can you help???
Subject: RE: New Message from Janine Graves in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 26-03-2013 03:38:50 PM
That is correct. I still see random and infrequent error.badfetch which even Cisco has been unable to nail down exactly. I suspect something on the gateway. One should monitor the gateway CPU utilization when this happens. I know for a fact that when it spikes and gets close to 100% you will get a bunch of these errors.
If it happens frequently you can def nail it down, however if it is rare and infrequent then your job it will require some debugging and setting debugs in prod to trace it down.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, March 26, 2013 3:32 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Janine Graves in Customer Voice Portal (CVP) - General Discussion - All Versions: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - General
Janine Graves has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Sidney,
It turns out that the VXML gateway and Vxml Server can both throw
error.badfetch events. It depends on who is making the http request. I
was surprised when the Vxml Server did this, but live and learn!
And, unfortunately, the VXML Property 'fetchtimeout' - only changes the
timer on the gateway side. I don't know how to tell VxmlServer to wait
longer than x seconds for a response. I also don't know what the default
time period is, or whether you can configure it.
When I used to teach for Audium, they told me that Vxml Server can make
http requests (for example, in the element named 'Action' - you can
select URI - and enter a URI to connect to a separate server and execute
some web app on that server. This is called the XML API - it's discussed
in the CVP Programming Guide).
Anyway, to make a long story short, for that http request VxmlServer has
a HARD CODED 5-second timeout to receive back the response. It's not
configurable. And I tend to think this is the case for Asher's scenario.
BUT - it sure would be nice if someone from Cisco could chime in. Paul
Tindall - can you help???
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535547 or simply reply to this email.
Subject: Re: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Janine Graves on 26-03-2013 03:42:51 PM
Nope, that won't work in Asher's case. The fetchtimeout timer tells the
Gateway not to time out while waiting for the next VXML page.
BUT - if it is the VXML Server is making an http request of a back-end
system, and if that's timing out, the Vxml Server doesn't obey the
fetchtimeout timer. It would have to be done (somehow) in the java code.
Subject: RE: Fetchtimeout in custom action element
Replied by: Asher Schweigart on 26-03-2013 03:53:12 PM
The element is a middleware element; I am fetching the information for a ticket in our helpdesk system and then routing the call based on that ticket.
So am I understanding you correctly Janine, I cannot set the fetchtimeout timer for this element in CS at all? I believe that means I can't set it in java either, right?
So to make this element not fail, I'll have to figure out how to make the element stop processing and exit before the 5 seconds is up. Not quite sure how to do that yet, but I think I can make that work.
Subject: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 26-03-2013 03:56:51 PM
Oops, Asher I just re-read your post. Since your debugger works but in production it doesn't - then it DOES sound like the vxml gateway is throwing the error.badfetch. And, in that case, as Shikha suggested, use the audio element just before this slow step, you can set the voicexml property in the Settings tab - set fetchtimeout to 60s (or whatever). And set the fetchaudio to a URI of filler music to play to the caller. Sorry for the confusion - but I thought your Vxml Server was throwing error.badfetch (which can occur). On 3/26/2013 1:38 PM, Cisco Developer Community Forums wrote: Asher Schweigart has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- I have a custom element that pulls some information using XML http requests, and it is causing CVP to throw a "error.badfetch". Running the same element in the debugger throws no such error, but it does take a long time to continue, so I am wondering if it is a voicexml timeout issue. From what I have read in other posts, I should be able to set the fetchtimeout vxml property on my custom action element. I don't see the normal pane to do that in CS, so I am thinking I should do it in the java code? How would I do this in java? -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13530941 or simply reply to this email. -- Janine Graves
Subject: Re: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 26-03-2013 04:03:50 PM
Wow, the forum is doing weird things. Posting replies 3x.
Subject: RE: Fetchtimeout in custom action element
Replied by: Shikha Sharma on 26-03-2013 04:14:21 PM
To me, this particular issue sounds like a simple case of Gateway timing out while VXML server is waiting for XML response as indicated by the delay on particular element step and this type of issue can easily be resolved by either setting fetchtimeout on global application level or on individual element level( audio element configured with fetchaudio in this case). Its interesting to know about vxml server timeout as I personally have never experienced one so far even while calling external APIs or backend system with response time of more than 30 seconds.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: GEOFFREY THOMPSON on 26-03-2013 04:35:50 PM
I have not had any problem with fetchaudio working correctly while the back end takes a while to process. It seemed to work perfectly for me. I put sleeps into the back end to simulate a delay and I can’t recall it playing up. It seemed to follow what the standard said.
Regards,
Geoff
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Paul Tindall on 27-03-2013 04:39:09 AM
Janine Graves:Sidney,
Anyway, to make a long story short, for that http request VxmlServer has
a HARD CODED 5-second timeout to receive back the response. It's not
configurable. And I tend to think this is the case for Asher's scenario.
BUT - it sure would be nice if someone from Cisco could chime in. Paul
Tindall - can you help???
Not sure I can help much but I can confirm the built-in back-end HTTP request doesn't give you any flexibility in terms of request timeout, security etc. You will have to code your own HTTP request in a custom action/decision element to get a longer timeout.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 27-03-2013 06:54:50 AM
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice.
Hemal
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, March 26, 2013 3:30 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties:
fetchtimeout
fetchaudio(if you want to play music while waiting for xml response)
This approach works for our webservice calls.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Asher Schweigart on 27-03-2013 04:45:34 PM
Paul Tindall:Not sure I can help much but I can confirm the built-in back-end HTTP request doesn't give you any flexibility in terms of request timeout, security etc. You will have to code your own HTTP request in a custom action/decision element to get a longer timeout.
That is what I've done, I have a custom action element that does the http request:
URL url = new URL("URL_that_returns_XML);
URLConnection conn = url.openConnection();
conn.setRequestProperty("Authorization", "Basic "+cred);
conn.connect();
InputStream sn = conn.getInputStream();
So maybe the timeout is not what is causing the error.
This is what the logs said:
10.255.60.88.1364318999643.19285.HD_start,03/26/2013 13:32:03.299,A VoiceXML error occurred of type "error.badfetch"
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:14.533,A VoiceXML error occurred of type "error.badfetch"
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:41.265, The error was: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
com.audium.server.MultipleThreadException: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
Subject: RE: New Message from Asher Schweigart in Customer Voice Portal (CVP) - Gene
Replied by: GEOFFREY THOMPSON on 27-03-2013 04:56:11 PM
When working with custom elements that do something serious, you should not rely on the activity log. You will sometimes get a “badfetch” as a result of an exception in your own code.
I always put in low level tracing to a file (named with date/time appended so each execution is in its own file) in C:\temp that I can turn off or on in the custom element with a Boolean flag – in Settings[]
During the development I have this set to true, and details I need to figure out what’s going on are in that file. When it’s ready, I can turn it off at the application level.
If you put in System.println they will appear in Tomcat\logs\stdoutXXX.log, but then you have to recompile to take them out.
Regards,
Geoff
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Shikha Sharma on 01-04-2013 12:15:44 PM
This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Hemal Mehta:The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, March 26, 2013 3:30 PM To: cdicuser@developer.cisco.com Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties: fetchtimeout fetchaudio(if you want to play music while waiting for xml response) This approach works for our webservice calls. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 01-04-2013 12:23:30 PM
That is obvious for fetchimeout. However you will also need to tune your web service timeout if your webservice is taking long time . If not you will see socket read timeout on Tomcat.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Monday, April 01, 2013 12:16 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Hemal Mehta:
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, March 26, 2013 3:30 PM To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com> Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties: fetchtimeout fetchaudio(if you want to play music while waiting for xml response) This approach works for our webservice calls. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13734378 or simply reply to this email.
Subject: RE: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General D
Replied by: Shikha Sharma on 02-04-2013 11:24:01 AM
Nope you won't receive any socket exception if you set proper timeout in your WS client code or you can always configure timeouts in tomcat. Webservices are usually maintained by cross functional teams and hence one does not always have control on their response time especially if the servers hosting them are old or running slow. Also, the issue here is related to badfetch and not Read timeout exception is a separate discussion altogether.
--------- Original Message ---------Subject: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
From: Cisco Developer Community Forums <cdicuser@developer.cisco.com>
Date: 4/1/13 12:23 pm
To: "cdicuser@developer.cisco.com" <cdicuser@developer.cisco.com>
Hemal Mehta has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- That is obvious for fetchimeout. However you will also need to tune your web service timeout if your webservice is taking long time . If not you will see socket read timeout on Tomcat.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Monday, April 01, 2013 12:16 PM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Hemal Mehta:
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, March 26, 2013 3:30 PM To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com> Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties: fetchtimeout fetchaudio(if you want to play music while waiting for xml response) This approach works for our webservice calls. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13734378 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13736246 or simply reply to this email.
Subject: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Replied by: Hemal Mehta on 02-04-2013 11:34:01 AM
That is what I am saying. Read
“However you will also need to tune your web service timeout if your webservice is taking long time”
Tuning and setting proper timeout are the same…
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Tuesday, April 02, 2013 11:24 AM
To: cdicuser@developer.cisco.com
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General D
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- Nope you won't receive any socket exception if you set proper timeout in your WS client code or you can always configure timeouts in tomcat. Webservices are usually maintained by cross functional teams and hence one does not always have control on their response time especially if the servers hosting them are old or running slow. Also, the issue here is related to badfetch and not Read timeout exception is a separate discussion altogether.
--------- Original Message ---------Subject: New Message from Hemal Mehta in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
From: Cisco Developer Community Forums <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Date: 4/1/13 12:23 pm
To: "cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>" <cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>>
Hemal Mehta has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- That is obvious for fetchimeout. However you will also need to tune your web service timeout if your webservice is taking long time . If not you will see socket read timeout on Tomcat.
From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com]
Sent: Monday, April 01, 2013 12:16 PM
To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com>
Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General
Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- This workaround is not to change webservice timeout, it is to restrict VXML gateway from timing out while waiting for response from webservice that have long response time.
Hemal Mehta:
The webservice timeouts do not get controlled by fetchtimeout. You need to explicity code that in the webservice. Hemal From: Cisco Developer Community Forums [mailto:cdicuser@developer.cisco.com] Sent: Tuesday, March 26, 2013 3:30 PM To: cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com<mailto:cdicuser@developer.cisco.com%3cmailto:cdicuser@developer.cisco.com>> Subject: New Message from Shikha Sharma in Customer Voice Portal (CVP) - General Discussion - All Versions: RE: Fetchtimeout in custom action element Shikha Sharma has created a new message in the forum "General Discussion - All Versions": -------------------------------------------------------------- You can put an audio element just before your custom action element and set following vxml properties: fetchtimeout fetchaudio(if you want to play music while waiting for xml response) This approach works for our webservice calls. -- To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13535491 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13734378 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13736246 or simply reply to this email.
--
To respond to this post, please click the following link: http://developer.cisco.com/web/cvp/forums/-/message_boards/view_message/13773458 or simply reply to this email.
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Shikha Sharma on 02-04-2013 11:51:18 AM
Put this code code under try catch block and print out errors in tomcat for the time being. You may also want to check if you are realeasing resources properly with sn.close(); statement in the end.
Asher Schweigart:
That is what I've done, I have a custom action element that does the http request:
URL url = new URL("URL_that_returns_XML);
URLConnection conn = url.openConnection();
conn.setRequestProperty("Authorization", "Basic "+cred);
conn.connect();
InputStream sn = conn.getInputStream();
So maybe the timeout is not what is causing the error.
This is what the logs said:
10.255.60.88.1364318999643.19285.HD_start,03/26/2013 13:32:03.299,A VoiceXML error occurred of type "error.badfetch"
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:14.533,A VoiceXML error occurred of type "error.badfetch"
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:41.265, The error was: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
com.audium.server.MultipleThreadException: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
Subject: RE: Fetchtimeout in custom action element
Replied by: Janine Graves on 09-04-2013 05:25:02 PM
Hi Asher,
Did you ever find the cause of this problem?
Asher Schweigart:I have a custom element that pulls some information using XML http requests, and it is causing CVP to throw a "error.badfetch".
Running the same element in the debugger throws no such error, but it does take a long time to continue, so I am wondering if it is a voicexml timeout issue.
From what I have read in other posts, I should be able to set the fetchtimeout vxml property on my custom action element. I don't see the normal pane to do that in CS, so I am thinking I should do it in the java code? How would I do this in java?
Subject: RE: Re: New Message from Sidney Orret in Customer Voice Portal (CVP) - Gene
Replied by: Janine Graves on 09-04-2013 05:27:02 PM
Actually, did you find the cause/solution to this problem?
10.255.60.88.1364319084959.19289.HD_start,03/26/2013 13:32:41.265, The error was: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
com.audium.server.MultipleThreadException: Another thread is currently working on this session. This means the original thread took too long to complete what it was doing. To prevent abnormal behaviour the original thread will exit immediately. The call should not be affected.
Labels:
Getting Started
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:
Customers Also Viewed These Support Documents