Stale IIS sessions cause by occasional webservice connection failures

[John_Webber1]

We have a Java-based API webservice which works most of the time, however sometimes it throws a generic connection error and leaves a stale session on the Onbase IIS webserver. This webservice points to a load balancer which handles traffic to the Onbase app server. Onbase doesn't log the error because the connection is lost. The lost connection only happens occasionally without any pattern. The session stays after an app pool recycle. Not until an IISReset does the session go away.

Would a timeout on the connection object help get rid of the stale sessions? Any other ideas?

[Patrick_Sweeney · Accepted solution]

Hello John,

This may be due to a bug in the way that Java handles sessions that existed in OnBase 15 and was fixed for OnBase 16.  However that was due to the Application Server hanging on to a successfully connected session - which seem to be contrary to what you're experiencing.

A timeout may help, in that it should assist in making sure applications are disconnected and disposed of properly.  In a similar vein it is important to make sure that created applications/webservices are properly disposed of, either via the 'using' statement pattern or by explicitly calling Dispose().

Connection issues involving a load balancer can be complicated and may require substantial background information about the way your system is set up as well as how, when, and under what additional conditions the connection is being attempted.  It's recommended that you work with your first line of support to correctly identify why the connection is failing and how to handle it going forward.

[Adam_Ryman]

This is being looked into by API Support.