Link to home
Avatar of mruff
mruff

asked on

Websphere JDBC Connection: J2CA0045E, Connection not available

Dear experts,
Since two days our application cannot acquire jndi/JDBC connections anymore.
The same set up: WebSphere 6.1., our application was working until two days.
I do NOT know if someone changed some configuration since then.
When our application start up and requests a jndi/JDBC connection we get J2CA0045E, Connection not available

What we already tried:
1.
followed all instructions: http://www-01.ibm.com/support/docview.wss?uid=swg21385033
Investigated the pool. Druing application startup with:
$AdminControl invoke $ds showPoolContents (we configured $ds correctly before)
we get ...Instance not found
After the application has started (which takes a long time due to the fact that no connections are available)
The pool seems fine and with the above command we can see:
MCWrapper ... Managed connection .... State: STATE_ACTIVE_FREE, whereas during our application startup I can see in the SystemOut.log of the WAS: MCWrapper ... Managed connection .... State: STATE_TRAN_WRAPPER_INUSE
2. Created a new JDBC connection from scratch
The JDBC connections itself is working fine, we get a connection when testing in the wasadmin web console by pressing the button "Test Connection"
->A single connection is fine
It seems that the Connection pool has a problem.
We have no further ideas how to analyse this problem more in depth or how to fix it
Any help is VERY appreciated
Many thanks
Avatar of Gary Patterson, CISSP
Gary Patterson, CISSP
Flag of United States of America image

What is the back-end database?
How many connections in the pool?
Have there been any changes to the application recently?
How many threads are configured in the web container?.  Is isGrowable configured for the web container thread pool?

The "Instance not found" message during startup probably just means that the connection pool hasn't been started yet.

When you say "After the application is started ... the pool looks fine ...".  What do you mean?  Please provide the full output of showPoolContents.
Avatar of mruff
mruff

ASKER

DB2, Backend DB2 is fine, I can connect with db2 client or WINSQL without problem to the exact same db with the same credentials as the WAS jndi/JDBC data source is configured
Connections in the pool : 40
App changes: No
Web Container Threads: min 10: Max 50, it is a development environment with VERY little load
The "Instance not found" message during startup probably just means that the connection pool hasn't been started yet.
Ok, but then the application hangs during startup and in the SystemOut I get a message: Startup process may be hung running since 600K milisec. ->Yet another very useful websphere message, does not tell which component hangs where
When you say "After the application is started ... the pool looks fine ...".  What do you mean?  Please provide the full output of showPoolContents.
Unfortunately I cannot provide the full output (cannot copy paste, since the system runs in a highly secured zone) I had to type everything ...
The basics:
Poolmanager name jdbc/mypool
Pool manager objext 123456
total numbers of connections 4 (max/min 40/1, reap/unused/aged 180/1800/0, connectointimeout/purge 180/Entire pool)  (testconnection/interfal/false/0, stuck timer/time/threshold 0/0/0, surge time/connectoins 0/-1)
Shared Connections information (shared partitions 200)
No Shared connections
Free Connection information (free distribution table/partitions 20/1)
(0)(0)MCWrapper id xyz Managed connection WSRdbManagedConnectoinImpl@1234 STATE_ACTIVE_FREE
...3 more entries
ASKER CERTIFIED SOLUTION
Avatar of Gary Patterson, CISSP
Gary Patterson, CISSP
Flag of United States of America image

Blurred text
THIS SOLUTION IS ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
Avatar of mruff

ASKER

Dear Gary,
The infrastructure team reverted to the last known working configuration. The system is up and running again. Although I do not know which wrong configuration caused the problem.
Martin