Re: System or internal errorDSRA0010E: SQL State = IX000, Error Code = -79716
pedro wrote: > Hi, > > We have a web application deployed on a websphere 6 application server > that's used to make some queries over an informix database. When > executing a specific operation the apps executes a query on the > database and gets the following exception: > > com.ibm.websphere.ce.cm.StaleConnectionException: System or internal > errorDSRA0010E: SQL State = IX000, Error Code = -79,716 > at > sun.reflect.GeneratedConstructorAccessor63.newInstance(Unknown Source) > at > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java: > 45) > at java.lang.reflect.Constructor.newInstance(Constructor.java: > 521) > at > com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java: > 523) > at > com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java: > 578) > at > com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.mapException(InternalGenericDataStoreHelper.java: > 533) > at > com.ibm.ws.rsadapter.AdapterUtil.translateSQLException(AdapterUtil.java: > 1121) > at > com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.synchronizePropertiesWithCRI(WSRdbManagedConnectionImpl.java: > 2411) > at > com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.getConnection(WSRdbManagedConnectionImpl.java: > 2680) > at com.ibm.ejs.j2c.MCWrapper.getConnection(MCWrapper.java: > 1959) > at > com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java: > 599) > at > com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java: > 431) > at > com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java: > 400) > at > pt.tmn.provisioning.web.utils.DatabaseUtils.getConnection(DatabaseUtils.java: > 102) > at > pt.tmn.provisioning.web.utils.DatabaseUtils.executeQuery(DatabaseUtils.java: > 51) > at > pt.tmn.provisioning.web.mvpn.dao.MvpnCrmDao.listAccounts(MvpnCrmDao.java: > 117) > at > pt.tmn.provisioning.web.mvpn.actions.MvpnCrmAction.listAccounts(MvpnCrmAction.java: > 109) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > 64) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: > 43) > at java.lang.reflect.Method.invoke(Method.java:615) > at > org.apache.struts.actions.ActionDispatcher.dispatchMethod(ActionDispatcher.java: > 335) > at > org.apache.struts.actions.ActionDispatcher.dispatchMethod(ActionDispatcher.java: > 318) > at > org.apache.struts.actions.ActionDispatcher.execute(ActionDispatcher.java: > 220) > at > pt.tmn.provisioning.web.mvpn.actions.MvpnCrmAction.execute(MvpnCrmAction.java: > 67) > at > org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java: > 431) > at > org.apache.struts.action.RequestProcessor.process(RequestProcessor.java: > 236) > at > org.apache.struts.action.ActionServlet.process(ActionServlet.java: > 1196) > at > org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) > at javax.servlet.http.HttpServlet.service(HttpServlet.java: > 763) > > After some research I thought that it had something to do with this > problem http://www-1.ibm.com/support/docview.wss?uid=swg21240540 and > so we updated the JDBC driver on the application server to the version > 3.00.JC3. However the problem persists. > > Does anybody know how can I fix this? Is this an Informix/Websphere > problem, or is my application doing anything wrong? > > Thanks in advance, > Pedro > The error 79716 is common when there is a firewall between the application server and the db server. I've seen this several times, namely in the same customer site. Nevertheless, you should check or ask someone to check, the resource adapter pool parameters, specifically the stale connection settings. This is strange, if the operation you mention is always the same... unless the operation takes a considerable ammount of time. You could also check the WAS error logs (maybe with a higher debug level) for specific Informix JDBC error messages like "broken pipe". This is the usual error when there is a firewall in the middle killing the TCP connections. Regards. -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...
On 6 Ago, 00:08, Fernando Nunes <s...@domus.online.pt> wrote: > pedro wrote: > > Hi, > > > We have a web application deployed on a websphere 6 application server > > that's used to make some queries over an informix database. When > > executing a specific operation the apps executes a query on the > > database and gets the following exception: > > > com.ibm.websphere.ce.cm.StaleConnectionException: System or internal > > errorDSRA0010E: SQL State = IX000, Error Code = -79,716 > > at > > sun.reflect.GeneratedConstructorAccessor63.newInstance(Unknown Source) > > at > > sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java: > > 45) > > at java.lang.reflect.Constructor.newInstance(Constructor.java: > > 521) > > at > > com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java: > > 523) > > at > > com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java: > > 578) > > at > > com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.mapException(InternalGenericDataStoreHelper.java: > > 533) > > at > > com.ibm.ws.rsadapter.AdapterUtil.translateSQLException(AdapterUtil.java: > > 1121) > > at > > com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.synchronizePropertiesWithCRI(WSRdbManagedConnectionImpl.java: > > 2411) > > at > > com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.getConnection(WSRdbManagedConnectionImpl.java: > > 2680) > > at com.ibm.ejs.j2c.MCWrapper.getConnection(MCWrapper.java: > > 1959) > > at > > com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java: > > 599) > > at > > com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java: > > 431) > > at > > com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java: > > 400) > > at > > pt.tmn.provisioning.web.utils.DatabaseUtils.getConnection(DatabaseUtils.java: > > 102) > > at > > pt.tmn.provisioning.web.utils.DatabaseUtils.executeQuery(DatabaseUtils.java: > > 51) > > at > > pt.tmn.provisioning.web.mvpn.dao.MvpnCrmDao.listAccounts(MvpnCrmDao.java: > > 117) > > at > > pt.tmn.provisioning.web.mvpn.actions.MvpnCrmAction.listAccounts(MvpnCrmAction.java: > > 109) > > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > > at > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > > 64) > > at > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: > > 43) > > at java.lang.reflect.Method.invoke(Method.java:615) > > at > > org.apache.struts.actions.ActionDispatcher.dispatchMethod(ActionDispatcher.java: > > 335) > > at > > org.apache.struts.actions.ActionDispatcher.dispatchMethod(ActionDispatcher.java: > > 318) > > at > > org.apache.struts.actions.ActionDispatcher.execute(ActionDispatcher.java: > > 220) > > at > > pt.tmn.provisioning.web.mvpn.actions.MvpnCrmAction.execute(MvpnCrmAction.java: > > 67) > > at > > org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java: > > 431) > > at > > org.apache.struts.action.RequestProcessor.process(RequestProcessor.java: > > 236) > > at > > org.apache.struts.action.ActionServlet.process(ActionServlet.java: > > 1196) > > at > > org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) > > at javax.servlet.http.HttpServlet.service(HttpServlet.java: > > 763) > > > After some research I thought that it had something to do with this > > problemhttp://www-1.ibm.com/support/docview.wss?uid=swg21240540and > > so we updated the JDBC driver on the application server to the version > > 3.00.JC3. However the problem persists. > > > Does anybody know how can I fix this? Is this an Informix/Websphere > > problem, or is my application doing anything wrong? > > > Thanks in advance, > > Pedro > > The error 79716 is common when there is a firewall between the application > server and the db server. I've seen this several times, namely in the same > customer site. > > Nevertheless, you should check or ask someone to check, the resource adapter > pool parameters, specifically the stale connection settings. > This is strange, if the operation you mention is always the same... unless the > operation takes a considerable ammount of time. > > You could also check the WAS error logs (maybe with a higher debug level) for > specific Informix JDBC error messages like "broken pipe". This is the usual > error when there is a firewall in the middle killing the TCP connections. > > Regards. > > -- > Fernando Nunes > Portugal > > http://informix-technology.blogspot.com > My email works... but I don't check it frequently... Hi Fernando, Thanks for your reply. The query is actually very slow, so your diagnostic probably hit the nail in the head. However, I didn't understand the solution that you suggest and I would ask you if you can elaborate a bit. Is this a firewall timeout problem? Where can I check the stale connection settings? In webpshere's administration console? When you say resource adapter pool parameters, are you talking about the JDBC datasource? I'm sorry for my ignorance, but I could really use the help. :) Thanks in advance, Pedro
pedro wrote: > On 6 Ago, 00:08, Fernando Nunes <s...@domus.online.pt> wrote: >> pedro wrote: >>> Hi, >>> We have a web application deployed on a websphere 6 application server >>> that's used to make some queries over an informix database. When >>> executing a specific operation the apps executes a query on the >>> database and gets the following exception: >>> com.ibm.websphere.ce.cm.StaleConnectionException: System or internal >>> errorDSRA0010E: SQL State = IX000, Error Code = -79,716 >>> at >>> sun.reflect.GeneratedConstructorAccessor63.newInstance(Unknown Source) >>> at >>> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java: >>> 45) >>> at java.lang.reflect.Constructor.newInstance(Constructor.java: >>> 521) >>> at >>> com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapExceptionHelper(GenericDataStoreHelper.java: >>> 523) >>> at >>> com.ibm.websphere.rsadapter.GenericDataStoreHelper.mapException(GenericDataStoreHelper.java: >>> 578) >>> at >>> com.ibm.ws.rsadapter.spi.InternalGenericDataStoreHelper.mapException(InternalGenericDataStoreHelper.java: >>> 533) >>> at >>> com.ibm.ws.rsadapter.AdapterUtil.translateSQLException(AdapterUtil.java: >>> 1121) >>> at >>> com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.synchronizePropertiesWithCRI(WSRdbManagedConnectionImpl.java: >>> 2411) >>> at >>> com.ibm.ws.rsadapter.spi.WSRdbManagedConnectionImpl.getConnection(WSRdbManagedConnectionImpl.java: >>> 2680) >>> at com.ibm.ejs.j2c.MCWrapper.getConnection(MCWrapper.java: >>> 1959) >>> at >>> com.ibm.ejs.j2c.ConnectionManager.allocateConnection(ConnectionManager.java: >>> 599) >>> at >>> com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java: >>> 431) >>> at >>> com.ibm.ws.rsadapter.jdbc.WSJdbcDataSource.getConnection(WSJdbcDataSource.java: >>> 400) >>> at >>> pt.tmn.provisioning.web.utils.DatabaseUtils.getConnection(DatabaseUtils.java: >>> 102) >>> at >>> pt.tmn.provisioning.web.utils.DatabaseUtils.executeQuery(DatabaseUtils.java: >>> 51) >>> at >>> pt.tmn.provisioning.web.mvpn.dao.MvpnCrmDao.listAccounts(MvpnCrmDao.java: >>> 117) >>> at >>> pt.tmn.provisioning.web.mvpn.actions.MvpnCrmAction.listAccounts(MvpnCrmAction.java: >>> 109) >>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) >>> at >>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: >>> 64) >>> at >>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java: >>> 43) >>> at java.lang.reflect.Method.invoke(Method.java:615) >>> at >>> org.apache.struts.actions.ActionDispatcher.dispatchMethod(ActionDispatcher.java: >>> 335) >>> at >>> org.apache.struts.actions.ActionDispatcher.dispatchMethod(ActionDispatcher.java: >>> 318) >>> at >>> org.apache.struts.actions.ActionDispatcher.execute(ActionDispatcher.java: >>> 220) >>> at >>> pt.tmn.provisioning.web.mvpn.actions.MvpnCrmAction.execute(MvpnCrmAction.java: >>> 67) >>> at >>> org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java: >>> 431) >>> at >>> org.apache.struts.action.RequestProcessor.process(RequestProcessor.java: >>> 236) >>> at >>> org.apache.struts.action.ActionServlet.process(ActionServlet.java: >>> 1196) >>> at >>> org.apache.struts.action.ActionServlet.doPost(ActionServlet.java:432) >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java: >>> 763) >>> After some research I thought that it had something to do with this >>> problemhttp://www-1.ibm.com/support/docview.wss?uid=swg21240540and >>> so we updated the JDBC driver on the application server to the version >>> 3.00.JC3. However the problem persists. >>> Does anybody know how can I fix this? Is this an Informix/Websphere >>> problem, or is my application doing anything wrong? >>> Thanks in advance, >>> Pedro >> The error 79716 is common when there is a firewall between the application >> server and the db server. I've seen this several times, namely in the same >> customer site. >> >> Nevertheless, you should check or ask someone to check, the resource adapter >> pool parameters, specifically the stale connection settings. >> This is strange, if the operation you mention is always the same... unless the >> operation takes a considerable ammount of time. >> >> You could also check the WAS error logs (maybe with a higher debug level) for >> specific Informix JDBC error messages like "broken pipe". This is the usual >> error when there is a firewall in the middle killing the TCP connections. >> >> Regards. >> >> -- >> Fernando Nunes >> Portugal >> >> http://informix-technology.blogspot.com >> My email works... but I don't check it frequently... > > Hi Fernando, > > Thanks for your reply. > > The query is actually very slow, so your diagnostic probably hit the > nail in the head. > > However, I didn't understand the solution that you suggest and I would > ask you if you can elaborate a bit. > > Is this a firewall timeout problem? Where can I check the stale > connection settings? In webpshere's administration console? When you > say resource adapter pool parameters, are you talking about the JDBC > datasource? > > I'm sorry for my ignorance, but I could really use the help. :) > > Thanks in advance, > Pedro > It can be a firewall timeout issue... I may be confusing two different issues. There are settings in the RSAdapter, but you have an Informix JDBC error code, so it should be the JDBC connection pool. We can try to look at the query... because even if we solve the timeout we may have to deal with the "user timeout", specially if it's a web application... The best thing would be to contact me directly on the customer site... Check the internal mail address book for my name, or access the internal IBM support page (muleta...). Regards. -- Fernando Nunes Portugal http://informix-technology.blogspot.com My email works... but I don't check it frequently...