Errors, Errors, and More Errors

Question

I am having massive problems with our Sql Server (v8 sp4)/Websphere (5) application.
We rolled out a new version of our (previous stable) J2EE application at the beginning of December 2005. Our app uses container-managed transactions, no entity beans.
We immediately began experiencing blocking processes. KILLing the blocking process almost always resulted in a few widowed and orphaned records.
I tried tuning the connection/transaction/context. Previously, the app created new connections for almost every function call to every bean. I changed the configuration to share the same connection for all the calls. The problem reduced slightly.
I have tried reducing the number of queries in each transaction. No help, either.
Today, I checked the logs and we are getting a crazy collection of database errors:
- "Statement is closed"
- "ResultSet is closed"
- "Invalid parameter binding(s)" (lots of these!)
- "No valid transaction context present"
- "Transaction is ended due to timeout"
- "Transaction has already failed, aborting operation."
As well as Java exceptions like:
- "NullPointerException"
- "SQLException: DSRA9002E ResourceException with error code null"
This makes no sense whatsoever. We didn't make massive changes to the code. Our changes focused on some new beans, new JSPs, etc.
Any ideas?
Russell T
Atlanta, GA (USA)

Answer 1

I apologize for explaining badly the connection setup. We are using connection pooling (through Websphere).
What I intended to say was that we were acquiring connections from the Context willy-nilly throughout the code. I created an abstract bean that every session bean extends in order to eliminate redundant code.
The abstract session bean gets its connection like this:
Context envCtx = (Context) new InitialContext();
String dataSourceName = (String) envCtx.lookup("java:comp/env/dataSourceName");
DataSource dataSource = (DataSource) envCtx.lookup("jdbc/" + dataSourceName);
connection = dataSource.getConnection();The Websphere admin has even tried additional tuning of the connection pool settings, such as size, timeout, reap time, etc.