Jayashree Menon

Many Thanks Shailesh.
However none of the above apply to the scenario. We did a lot of Research and testing at our end. Following are the scenarios and the conclusions.

We tested the application by connecting to DataSource of Oracle 9i. It worked perfectly fine. No resultsets were closed.

The same piece of code connecting to Oracle 10g datasource fails.

Next we tried connecting to Oracle 10g through DriverManager instead of Datasource. It worked perfectly fine.

Our conclusion is that Oracle 10g datasource has some issues which we are not clear about. Is it because we are updating the same table as that of the resultset in the same connection that the resultset is getting closed? We are not too sure of this. Would be glad if anyone can shed some light on this.

Thanks a lot
Jayashree Nair

Thank You Dilip.
We did put in a lot of SOPs and checked, but the connection object is not null or closed. Even the ResultSet is not null. Which is what is strange.
I hope we get a resolution for this quickly.

Our application which was on Websphere5.1 and Oracle 9i was recently upgraded to Websphere6.1.0.13 and Oracle 10g. With the same set of Code and other setting such as Datasopurces, connection pooling etc, we are getting an error as :

DSRA9110E: ResultSet is closed
Instead of the complete code I will post the logic and some pseudo code on this.

Session Bean //Global variables Connection connection = null query_str_1 = "get all rows to process from table 1" query_str_2 = "update the status of each record of table 1" business method(){ connection = getConn(); resultset = connection.executeQuery(query_str_1); loop thru the resultset{ try{ do validation for each record 1 post entries into another table }catch(Exception ){ //in case of any exceptions or errors executeUpdate(query_str_2); continue; } } } unfortunately after the first run of the loop I am getting an error as mentioned DSRA9110E: ResultSet is closed However there are multiple rows in the result set. I want it to continue with the next record which it does not do. What could be the problem with the new environment? Any ideas or inputs are welcome.

We are trying to upgrade our application from Websphere 5.3 to Websphere 6.1.0.13. In doing thus I have set variable in the name Space bindings of Websphere 6.1.0.13

Did it as
Environment->naming->New->.....

My code for lookup is as follows
try{ javax.naming.Context ic = new javax.naming.InitialContext(); variablename = (String)ic.lookup("thisNode/cell/legacyRoot/PROPERTY_FILE_PATH_JNDI"); }catch(NamingException ex){ System.out.println("variablename =====>Exception==>"+variablename); ex.printStackTrace(); throw new RuntimeException(ex.getMessage()); }
This was the way it was coded for Websphere 5.3

I have an ejb client which is remote and trying to do a lookup on Websphere6.1 for this variable.

It is failing with a stack trace as follows ..
javax.naming.NameNotFoundException: Context: PSLAIX01Node21Cell/nodes/BTDITNode04/servers/server1, name: thisNode/cell/legacyRoot/PROPERTY_FILE_PATH_JNDI: First component in name PROPERTY_FILE_PATH_JNDI not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL :-o mg.org/CosNaming/NamingContext/NotFound:1.0] at com.ibm.ws.naming.jndicos.CNContextImpl.processNotFoundException(CNContextImpl.java:4730) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1907) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552) at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1354) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:172) at javax.naming.InitialContext.lookup(InitialContext.java:363) at com.orbitech.common.CommonPropertyLoader.CommonPropertyLoader(CommonPropertyLoader.java:24) at com.orbitech.common.CommonPropertyLoader.getAttribute(CommonPropertyLoader.java:106) at orbi.custcom.LGDBUtils.getDriverMangConnection(LGDBUtils.java:144) at orbi.custcom.LGNewInterface.doOnlineBatchProcessing(LGNewInterface.java:370) at orbi.custcom.LGMain.callCustComm(LGMain.java:1700) at BatchUpload.processYearEndTaxSumRpt(BatchUpload.java:565) at BatchUpload.main(BatchUpload.java:816) Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL :-o mg.org/CosNaming/NamingContext/NotFound:1.0 at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85) at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(_NamingContextStub.java:504) at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4351) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1901) ... 12 more javax.naming.NameNotFoundException: Context: PSLAIX01Node21Cell/nodes/BTDITNode04/servers/server1, name: thisNode/cell/legacyRoot/PROPERTY_FILE_PATH_JNDI: First component in name PROPERTY_FILE_PATH_JNDI not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL :-o mg.org/CosNaming/NamingContext/NotFound:1.0] at com.ibm.ws.naming.jndicos.CNContextImpl.processNotFoundException(CNContextImpl.java:4730) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1907) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552) at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1354) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:172) at javax.naming.InitialContext.lookup(InitialContext.java:363) at com.orbitech.common.CommonPropertyLoader.CommonPropertyLoader(CommonPropertyLoader.java:24) at com.orbitech.common.CommonPropertyLoader.getAttribute(CommonPropertyLoader.java:106) at orbi.custcom.LGDBUtils.getDriverMangConnection(LGDBUtils.java:145) at orbi.custcom.LGNewInterface.doOnlineBatchProcessing(LGNewInterface.java:370) at orbi.custcom.LGMain.callCustComm(LGMain.java:1700) at BatchUpload.processYearEndTaxSumRpt(BatchUpload.java:565) at BatchUpload.main(BatchUpload.java:816) Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL :-o mg.org/CosNaming/NamingContext/NotFound:1.0 at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85) at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(_NamingContextStub.java:504) at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4351) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1901) ... 12 more javax.naming.NameNotFoundException: Context: PSLAIX01Node21Cell/nodes/BTDITNode04/servers/server1, name: thisNode/cell/legacyRoot/PROPERTY_FILE_PATH_JNDI: First component in name PROPERTY_FILE_PATH_JNDI not found. [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL :-o mg.org/CosNaming/NamingContext/NotFound:1.0] at com.ibm.ws.naming.jndicos.CNContextImpl.processNotFoundException(CNContextImpl.java:4730) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1907) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1862) at com.ibm.ws.naming.jndicos.CNContextImpl.lookupExt(CNContextImpl.java:1552) at com.ibm.ws.naming.jndicos.CNContextImpl.lookup(CNContextImpl.java:1354) at com.ibm.ws.naming.util.WsnInitCtx.lookup(WsnInitCtx.java:172) at javax.naming.InitialContext.lookup(InitialContext.java:363) at com.orbitech.common.CommonPropertyLoader.CommonPropertyLoader(CommonPropertyLoader.java:24) at com.orbitech.common.CommonPropertyLoader.getAttribute(CommonPropertyLoader.java:106) at orbi.custcom.LGDBUtils.getDriverMangConnection(LGDBUtils.java:146) at orbi.custcom.LGNewInterface.doOnlineBatchProcessing(LGNewInterface.java:370) at orbi.custcom.LGMain.callCustComm(LGMain.java:1700) at BatchUpload.processYearEndTaxSumRpt(BatchUpload.java:565) at BatchUpload.main(BatchUpload.java:816) Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL :-o mg.org/CosNaming/NamingContext/NotFound:1.0 at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:85) at com.ibm.WsnOptimizedNaming._NamingContextStub.resolve_complete_info(_NamingContextStub.java:504) at com.ibm.ws.naming.jndicos.CNContextImpl.cosResolve(CNContextImpl.java:4351) at com.ibm.ws.naming.jndicos.CNContextImpl.doLookup(CNContextImpl.java:1901) ... 12 more

Please help resolve this