This is a discussion on Handling invalid database connections from connection pools within the DB2 forums, part of the Database Server Software category; --> I am currently developing a web app using WSAD 5.1 and DB2 V7.2.8. I understand there is a myriad ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I am currently developing a web app using WSAD 5.1 and DB2 V7.2.8. I understand there is a myriad of database errors related to obtaining valid connections that are mapped directly to com.ibm.websphere.ce.cm.StaleConnectionException. There are apparently two solutions to ensure a valid connection is obtained from a WebSphere dataSource. The first is to catch StaleConnectionExceptions and attempt to execute the transaction again a finite number of times. The second is to configure WebSphere to test each connection as they are obtained. See link http://publib.boulder.ibm.com/infoce...n &maxHits=50 for details. I would like to catch com.ibm.websphere.ce.cm.StaleConnectionException since it is not likely that our shop will ever move our applications off WebSphere. Does anyone know what library should be included in the Java build path? Is this the preferred method of handling invalid connections? I cannot seem to find any useful documentation on this subject for WSAD 5.1. Thanks in advance. |
| |||
| Maybe you can try WAS newsgroup. "Edward Singleton" <singleton@mchsi.com> wrote in message news:7e007c06.0407061151.245ca4c9@posting.google.c om... > I am currently developing a web app using WSAD 5.1 and DB2 V7.2.8. I > understand there is a myriad of database errors related to obtaining > valid connections that are mapped directly to > com.ibm.websphere.ce.cm.StaleConnectionException. There are > apparently two solutions to ensure a valid connection is obtained from > a WebSphere dataSource. The first is to catch > StaleConnectionExceptions and attempt to execute the transaction again > a finite number of times. The second is to configure WebSphere to > test each connection as they are obtained. See link > http://publib.boulder.ibm.com/infoce...n &maxHits=50 > for details. > > I would like to catch com.ibm.websphere.ce.cm.StaleConnectionException > since it is not likely that our shop will ever move our applications > off WebSphere. Does anyone know what library should be included in > the Java build path? Is this the preferred method of handling invalid > connections? I cannot seem to find any useful documentation on this > subject for WSAD 5.1. Thanks in advance. |
| |||
| We're stuck in the same place. The WAS 3.5 to 4.0 documentation says to use com.ibm.websphere.ce.cm.StaleConnectionException, but the 5.0 documentation is silent on the matter, and of course the WSAD documentation is useless. This class isn't in the WAS 5.0 api documentation. |
| ||||
| We're stuck in the same place. The WAS 3.5 to 4.0 documentation says to use com.ibm.websphere.ce.cm.StaleConnectionException, but the 5.0 documentation is silent on the matter, and of course the WSAD documentation is useless. This class isn't in the WAS 5.0 api documentation. |
| Thread Tools | |
| Display Modes | |
|
|