Inuseconnectiontimeoutmilliseconds event does not stop a running JDBC query or a running HTTP request
 Technote (FAQ)
 
Problem
If you are using the Local Redirector plug-in configuration, you might discover that setting the inuseconnectiontimeoutmilliseconds property in the was.conf file to a low value does not stop the running request, or the running JDBC® query if an inuseconnectiontimeoutmilliseconds event occurs.
 
Cause
This is normal behavior.
 
Solution
The designed behavior of an inuseconnectiontimeoutmilliseconds event is to replace only the running connection in the JDBC pool and destroy the Application Server's reference to this connection. The Application Server is incapable of stopping a running query on the database side, and is not designed to kill a request (that is, immediately return a response to the browser) if such an event occurs.

This behavior is documented in WebSphere Application Server Standard Edition Planning, Installing, and Using Version 3.5.

 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server for z/OS > Plug-in
Operating system(s): z/OS
Software version: 4.0.1
Software edition:
Reference #: 1157133
IBM Group: Software Group
Modified date: May 10, 2004