U2 session timeout (OpenInsight 32-Bit)
At 31 JUL 2007 10:21:13AM Enrique Murphy wrote:
Following with the U2 testing, I found that when a OI session that connects to a U2 server is left open 15 or 30 minutes, it seems to "timeout" in the U2 server, and then it is impossible to close the OI session, because no U2 table is then available to OI.Is this fixed in OI 8.01?.Is the OEngine U2 connection problem fixed in OI 8.01?Thanks.Enrique
At 31 JUL 2007 05:44PM Bob Carten wrote:
Hi Enrique,
I made some minor changes in 8.01, including code so that if the connection times out it will try to reconnect. However, I do not think I truly solved the problem. I intend to spend a block of time on the Bond in the next month or so, to resolve some of the issues you and others have raised.
- Bob
At 01 AUG 2007 08:44AM Enrique Murphy wrote:
OK. I will be waiting. I have a chance to put into production an OI for U2 application. If everything gets right, it could be by September, so I would like to count with the bond working well by then. I will let you know of any other issue I see.
At 14 AUG 2007 06:18PM Bob Carten wrote:
Enrique,
I had a chance to work with Bill Winters of IBM U2 Technical Services last week.
He told me that the Intercall connection has a default timeout setting.
It is possible to set the timeout to zero, so that the connection will never time out.
However, he recommends against setting the timeout to zero because it can lead to orphaned sessions.
Orphaned sessions can only be repaired by restarting the service. He suggested sending a keep alive message to the server on a regular basis.
I wrote two programs which will be included in the next release.
U2_KeepALive uses idleproc to send a message to the U2 server every 10 minutes
U2_TimeDate is a supporting routine which returns the server time and date in OI DT format, for example 1433.33456
The timedate function is useful on its own, to ensure that all clients are using the same clock.
Click on the links to see the source.
I intend to make attach table call U2_Keepalive.
Until then, call it yourself from the startup of the application.
HTH
Bob
At 15 AUG 2007 09:01AM [email protected] wrote:
Sweet ,,
At 22 JUN 2011 02:07AM Asraph Ali wrote:
Hi,
It has been a while since you posted that, I believe U2_Keepalive is now called internally to keep the connection alive. I have users complaining they get the error 'ID not found in table'(validation msg) for any valid ID in the table. However on restarting they are able to access those records. The problem seems to be with idle connections.
I can call U2_KeepAlive at startup, But is it necessary?