Hi All,

Please help me.

We have created Data source for application. Test connection is successfull.

When i am login into application its giving below error.

WAS level is 7.0.0.0 no fix pack has been applied. DB2 9.7.

Error : [1/27/12 15:41:15:612 GMT+05:30] 0000001b SystemErr    
R com.ibm.websphere.ce.cm.ObjectClosedException: DSRA9110E:
Statement is closed.
[1/27/12 15:41:15:612 GMT+05:30] 0000001b SystemErr     R  at com.ibm.ws.rsadapter.jdbc.WSJdbcWrapper.createClosedException
(WSJdbcWrapper.java:109)
[1/27/12 15:41:15:612 GMT+05:30] 0000001b SystemErr     R  at com.ibm.ws.rsadapter.jdbc.WSJdbcStatement.runtimeXIfNotClosed
(WSJdbcStatement.java:1676)
[1/27/12 15:41:15:612 GMT+05:30] 0000001b SystemErr     R  at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute
(WSJdbcPreparedStatement.java:589)
[1/27/12 15:41:15:612 GMT+05:30] 0000001b SystemErr     R  at com.ibatis.sqlmap.engine.execution.SqlExecutor.executeUpdate
(SqlExecutor.java:84)
[1/27/12 15:41:15:612 GMT+05:30] 0000001b SystemErr     R  at com.i


00000018 SystemErr     R com.ibatis.common.jdbc.exception.NestedSQLException:  
--- The error occurred in com/inventys/intermixentry/db/
fusion_user_groups.xml. 
--- The error occurred while applying a parameter map. 
--- Check the getGroupId-InlineParameterMap. 
--- Check the statement (query failed). 
--- Cause: com.ibm.websphere.ce.cm.ObjectClosedException: DSRA9110E: Statement is closed.
Caused by: com.ibm.websphere.ce.cm.ObjectClosedException: DSRA9110E: Statement is closed.
[1/27/12 15:52:09:604 GMT+05:30] 00000018 SystemErr     R  at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.execute
QueryWithCallback(GeneralStatement.java:185)
[1/27/12 15:52:09:604 GMT+05:30] 00000018 SystemErr     R  at com.ibatis.sqlmap.engine.mapping.statement.GeneralStatement.execute
QueryFor


We have apply any fix for this. Please help me this errors needs to be
handled by code level or in WAS level.


Thanks,
Chinna.

Chinna, without knowing your application it's very difficult to give you some advice. This kind of Exception (Statement closed) is usually an application error (the logic is bad implemented), not a WebSphere one! But, as I said, usually!
Sometimes the coders cache the statement to avoid preparing it again, and close it when an SQLException is caught. After that, they try to use it again.
Another situation that I've already seen in the past is that an object calls a method from another object and sends the connection object as a parameter (to use the same thread, to avoid getting a new connection, etc.). If the called object closes the connection and the caller doesn't care about it, you can also get this kind of error.
My hint: if it is a own programm (from your development staff) give them a call with the stack trace.
I hope this helps.
Regards,
Rodney

Hi,

I do agree that it is a programming issue either connection is wrongly closed or application using connection pool and its timeout is not set properly!

//Ahmed