• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 668
  • Last Modified:

We are getting a 'Connection is already closed' exception from WebSphere 5 and jConnect 5.5

We have an web application that uses a Sybase/JDBC Datasource.  We are utilziing the standard connection pooling provided by WebSphere 5 and the jConnect JDBC provider.  We are experiencing intermittent SqlExceptions "JZ0C0: Connection is already closed." when attempting to use connections returned from the Datasource.  We're fairly confident we are dutifully closing all of our statements, result sets and connections when we are done using them.  It is our understanding that when we close a connection, it is returned to the connection pool and is available for further use.

This appears to work properly most of the time.  We have not been able to reproduce it reliably.

-jon
0
jonprettyman
Asked:
jonprettyman
1 Solution
 
mmuruganandamCommented:
Make sure that all your connections are closed in the finally block of all your code.  There are chances that your connection might be closed based on one data condition and try to use the same connection in the same block for some other reason.

It is purely a code bug.


Regards,
Muruga
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now