Hi,
When connecting concurrently to DB2 via JDBC from a Websphere hosted
servlet-based application, we keep getting the SQL1224N DB2 error:
"SQL1224N A database agent could not be started to service a request, or was
terminated as a result of a database system shutdown or a force command."
(absolutely no 'force application' or 'shutdown' commands were issued, and
the db manager is runing fine)
A custom connection pooling is being used, not the Websphere connection
pooling. To eliminate the possiblity of connection limits, we open/close
a connection for each request (!) but the problem still persists (and at
very light loads too, < 10 clients). The database manager configuration
shows that ample number of DB2 agents (around 200 max and 20 in the agent
pool) have been allocated, but the db2 'list applications' command never
shows more than 1 agent running on behalf of the Websphere 'java' process
(the application from which I am trying to get the connections).
Has anyone encountered this problem? Cycling Websphere usually gets around
this problem before eventually it happens again. Is it something within the
JDBC driver which keeps open resources even though the Java application has
issued the conn.close()? One would expect that altleast open/close of a
connection on each request (for <10 request) should not result in this
problem. Is this an application|DB2 configuration|JDBC driver bug|AIX
environment|DB2 license issue?
Any input appreciated.
Thanks,
Arvind
PS: If possible, please also cc any replies to my email address
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
