After this error occurs, the application couldn't get connection to
DB2 any more and all the SQL statements cannot be executed.
Could anyone kindly help by telling what is going wrong? This
may happen any time: after recycling the server, or after the
application has been called for a while. So it is the problem with
WAS/DB2 setting, or with the application?
The basic reason for such a error is connection failure from the database server. There are two possible reasons:
1.The network failure.
For this try to have a good connectivity or have both the DB server and the web application on the same machine.
2.If this is occuring at a particular point in the application,
please check that you are not forcing the connection from the application , if so please ensure that you restart the database manager and try the successive statements.
Please let me know if you get a different solution.
> I have a web application running on DB2 and OS390. The problem is
> that we will suddenly run into a problem unpredictably. The error
> message is...
Talking about "unpredictably", I mean I couldn't trace to a particular
point in the application where such connection failure will definitely o
occur. It could simply happen any time. Thus, could I say it is the
connection problem between WAS and DB servers?
Someone suggested that it may be caused by non-properly closure of
DB connection, which holds up all the JDBC cursors. Is it possible?
> 1.The network failure.
> For this try to have a good connectivity or have both the DB server
> and the web application on the same machine.
The WAS and DB servers are actually in the same OS390 machine,
but segregated into two "segments". Will there still have such
Well my headache is how to diagnose the exact cause of the problem.
Any good suggestion?
Well to diagnose the problem from the DB side, you can create a a event monitor on the db for statements ,deadlocks and transactions. Through this you can see the last statement executed or transaction taken place and then go to the application and check at that particular point.
Hope this will work.
Prashant G Dahalkar