The Server is AIR 4 SP1

And connection.disconnect.hangup do stamp DB and exit.

Hi Neil,

For your suggestion to upgraded to DD 5.1, it will fixed the redone on disconnect,isn't it?

Besides, is it will fix the issue that DD app drop every 5 minutes?

Please advise.

Chukiat d.

There have been alot of changes since 4.1 on application exit and how it handles reentrant code. From the looks of it, you are encoutering that problem where the app is setting the exit timer and you are reentering and doing a DB operation, so the app is getting lost. The new changes to DD in 5.0 and 5.1 should help in this regard and it should fix the 5 minute session timeout.

Hi Neil,

Thank you for your suggestion.

Today, I have test with extends the session timeout from 5 minutes to 30 minutes (Tomcat Default).

The result of DD App is not be dropped the connection after 5 minutes.

So How are the DD App relate with session timeout in web.xml?

Please give me any suggestion.

Besides, If customer would used the existed DD4.1.10.p2,
Can I extend the exit timer from 5 seconds to 10 seconds in order to waiting the browser will try to fetch the hangup handler on the app server before the session was closed ?

Thank you .

Chukiat D.

I don't recommend a 10 second exit timer especially with a CTI application. I think your best bet is to upgrade.