ICC timeout value is not getting updated
from ICC logs, timeout value seems to be 8sec
30/07/2010 18:09:24 DEBUG - ICConnectorManager.doGet: Request string is reqid=61-396&icconnectorMessage=[VOX.newcall("10480",)][61-396]&timeout=8000&channel=1048

While in ddconfig.xml, we have changes it to 4 sec (via ddadmin)
<icconfig>
<enablevoxconnector value="true"/>
<defaulttimeout value="4000"/>

The 2 values are separate. The value found in icconfig is the primary value. The 8000 passed in via the command is a backup value.

we noticed that timeout dosent happen after 4sec. Please check the log snippet below
App trace:
22/07/2010 15:25:24 INFO - 2CE28D24EEF0C73E11CEA74FFF335497:/Visanet_v3_20100720 : VOX response: VOX.newcall.response("Out of sync","10268","")

ICconnector log:
22/07/2010 15:25:15 DEBUG - ICConnectorManager.doGet: Request string is reqid=14837-337&icconnectorMessage=[VOX.newcall("10268",)][14837-337]&timeout=8000&channel=10268
22/07/2010 15:25:15 DEBUG - ICConnectorManager.doGet: Waiting for notification from VOX for request:14837-337
22/07/2010 15:25:15 DEBUG - [BLZ1_VOX_VP] ICConnectorCommon.Write: Writing to socket:[VOX.newcall("10268",)][14837-337]
22/07/2010 15:25:24 DEBUG - ICConnectorManager.jobCompleted: Response back from Vox: VOX.newcall.response("Out of sync","10268","") for req: 14837-337
22/07/2010 15:25:24 DEBUG - ICConnectorManager.doGet: Wait time for Vox to return response:8602ms for request ID:14837-337
22/07/2010 15:25:24 DEBUG - ICConnectorManager.doGet: Looking up 14837-337 and returning response back to caller:VOX.newcall.response("Out of sync","10268","")
22/07/2010 15:25:24 DEBUG - ICConnectorManager.doGet: Time to complete doGet request:8602ms for request ID:14837-337

What you are getting back is the response from the VOX. The VOX is set to 8 sec timeout, however the ICC is stopping after 4 secs and reporting it to the app. 4 secs after that, the VOX is returning a sync issue. In order to understand the whole scenario, I would need to see the VOX log for that time period. What might be happening is the VOX is not getting a call in even though it is getting a new call request and it is waiting the 8 secs to see if the call arrives. Can't tell exactly without seeing the VOX side.

Hi Neil

you are saying that "the 2 values are separate. The value found in icconfig is the primary value. The 8000 passed in via the command is a backup value."

what is the meaning of primary value? we need to change the 8000 value sent by the command, how we do that?

thanks
Magdalena

If you need to change the timeout, you would do it in the DD admin servlet. At one time, we were going to allow you to configure the timeout so long running processes like workflows could be adjusted, but it was never a necessary requirement, so the timeout is passed in via the command but not used. However, there is one place we do use the passed in timeout and that is when the invoke workflow call is to be returned immediately. In that case, we pass in a 0, however this is all internal code and the app developer cannot change this cmd line timeout manually.

So for the short answer, modify the ICC Config in the Admin servlet to change your timeout.

our customer wants that all transactions that take more than 4 secs to be closed, is there any way to do that?

we want to wait no more than 4 secs for a VOX response...

Just set the timeout to 4 secs on the ICC config screen in DD admin servlet.