By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,693 Members | 1,936 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,693 IT Pros & Developers. It's quick & easy.

Handling invalid database connections from connection pools

P: n/a
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...ion&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.
Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Maybe you can try WAS newsgroup.

"Edward Singleton" <si*******@mchsi.com> wrote in message
news:7e**************************@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...ion&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.

Nov 12 '05 #2

P: n/a
Test message
Nov 12 '05 #3

P: n/a
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.

Nov 12 '05 #4

P: n/a
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.

Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.