Murad Iqbaal wrote:
Was this working before? Once, I also encountered this connection closed error, it was a pain to resolve. Make sure you are not using select * in your query. Pick up table fields by their names and try.
Certainly select * should be avoided, but how could it cause the closed connection error?
It was thrown by WebSphere App Server 7.01. It did not make sense that is why it was hard to track. When we changed the select *, it started working.
Sometimes when the time out property is set on the connection pool of the application server, it forcibly releases the connection back to the pool after the specified period(ie.whatever is specified in the property,like 300 seconds etc). In which case you get the Connection has been Closed error.
No matter how many women are assigned to the project, a pregnancy takes nine months. Much longer than this tiny ad:
Thread Boost - a very different sort of advertisinghttps://coderanch.com/t/674455/Thread-Boost-feature