When you debug you specify a different timeout, could that be the cause?

Sent from my HTC

----- Reply message -----
From: "Cisco Developer Community Forums" <cdicuser@developer.cisco.com>
Date: Tue, Aug 14, 2012 05:48
Subject: New Message from Greg Lowe in Contact Center Express Scripting (CCXS) - Contact Center Express Scripting Questions: Exception time-out while calling subflow - UCCX 8.5(1)
To: "cdicuser@developer.cisco.com" <cdicuser@developer.cisco.com>

Greg Lowe has created a new message in the forum "Contact Center Express Scripting Questions":

--------------------------------------------------------------
Hi All,

I'm hoping for some help with trying to debug an error I'm having in one of my scripts.

I have a Call Subflow step within my script which calls a XML file based on the Input Mappings provided. My problem is I receive a timeout error (error below) as soon as the script hits the Call Subflow step. I have tried to debug the script the Call Subflow calls (systemStatus-CSQhttp.aef) but it passes the debug fine and no errors are reported. I only get the error when using the Call Subflow step.

Has anyone seen such a timeout error before or know what would be causing the timeout?

Error:
"Exception creating connection to: 169.254.95.120; nested exception is:
java.net.SocketTimeoutException: connect timed out; nested exception is:
java.rmi.ConnectIOException: Exception creating connection to: 169.254.95.120; nested exception is:
java.net.SocketTimeoutException: connect timed out"


Greg
--
To respond to this post, please click the following link:

<http://developer.cisco.com/web/ccxs/forums/-/message_boards/view_message/6277828>

or simply reply to this email.