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.
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
Discover new time-saving features in one game-changing release, ScreenConnect 6.0, based on partner feedback. New features include a redesigned UI, app configurations and chat acknowledgement to improve customer engagement!
Configure Web Service (server application)
I. Configure security for Web Services methods First, we need to protect Session bean which implements the service:
1. Open EJB deployment descriptor (ejb-jar.xml) in the EJB project that contains you…
This article is about some of the basic and important steps to be used to improve the performance in web-sphere commerce application development.
1) Always leverage the Dyna-caching facility provided by the product
2) Remove the unwanted code …