Internal Drive Error (SQL Expception) in WebSphere Application Server - Websphere

This is a discussion on Internal Drive Error (SQL Expception) in WebSphere Application Server - Websphere ; Hello We have deployed web application on and configured data source using DB2 UDB for iSeries (Toolbox) on WebSphere Application Server and restart web sphere service. Now Whenever I was accessing my application it's gave me error "Internal driver error" ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Internal Drive Error (SQL Expception) in WebSphere Application Server

  1. Internal Drive Error (SQL Expception) in WebSphere Application Server

    Hello

    We have deployed web application on and configured data source using DB2 UDB for iSeries (Toolbox) on WebSphere Application Server and restart web sphere service.

    Now Whenever I was accessing my application it's gave me error "Internal driver error" and throwing following exception in systemerr.log:-

    I guess this error occurs during any JDBC Transaction.

    Also, please find the attached file JDBCTrace_WASDataSource.zip for JDBC trace.

    hread[WebContainer : 0,5,main] Fri Aug 26 07:41:59 EDT 2005 as400: Connection B10B379F (-1297684670) : Throwing exception. Actual exception: Internal driver error. (class java.lang.InterruptedException) sqlState: HY000 vendor code -99999.java.sql.SQLException: Internal driver error. (class java.lang.InterruptedException) at java.lang.Throwable.(Throwable.java:195)
    at java.lang.Exception.(Exception.java:41)
    at java.sql.SQLException.(SQLException.java:40)
    at com.ibm.as400.access.JDError.throwSQLException(JDE rror.java:521)
    at com.ibm.as400.access.AS400JDBCConnection.sendAndRe ceive(AS400JDBCConnection.java:2597)
    at com.ibm.as400.access.AS400JDBCStatement.close(AS40 0JDBCStatement.java:434)
    at com.ibm.as400.access.AS400JDBCPreparedStatement.cl ose(AS400JDBCPreparedStatement.java:433)
    at com.saterisystems.sasinv1r0.dispatcher.SS_Statemen tControl.closeConn(SS_StatementControl.java:245)
    at com.saterisystems.sasinv1r0.requester.SS_DAOReques ter.closeConn(SS_DAORequester.java:212)
    at com.saterisystems.sasinv1r1.webarch.iarchie.beans. SS_RegisterBean.doesAccountNoExist(SS_RegisterBean .java:1908)
    at com.saterisystems.sasinv1r1.webarch.iarchie.beans. SS_RegisterBean.doProcess(SS_RegisterBean.java:255 )
    at com.saterisystems.sasinv1r1.webarch.iarchie.main.J HMnBean.processRequest(JHMnBean.java:400)
    at com.saterisystems.sasinv1r1.webarch.iarchie.main.J HMnBean.processRequest(JHMnBean.java:214)
    at com.saterisystems.sasinv1r1.webarch.iarchie.servle ts.RequestDispatcher.executeTxn1(RequestDispatcher .java:1089)
    at com.saterisystems.sasinv1r1.webarch.iarchie.servle ts.RequestDispatcher.handleRequest1(RequestDispatc her.java:848)
    at com.saterisystems.sasinv1r1.webarch.iarchie.servle ts.JHMainServlet.doPost(JHMainServlet.java:154)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:763)
    at javax.servlet.http.HttpServlet.service(HttpServlet .java:856)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.ser vice(ServletWrapper.java:1282)
    at com.ibm.ws.webcontainer.servlet.ServletWrapper.han dleRequest(ServletWrapper.java:673)
    at com.ibm.ws.webcontainer.servlet.CacheServletWrappe r.handleRequest(CacheServletWrapper.java:80)
    at com.ibm.ws.webcontainer.WebContainer.handleRequest (WebContainer.java:1802)
    at com.ibm.ws.webcontainer.channel.WCChannelLink.read y(WCChannelLink.java:84)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleDiscrimination(HttpInboundLink.java:469)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.handleNewInformation(HttpInboundLink.java:408)
    at com.ibm.ws.http.channel.inbound.impl.HttpInboundLi nk.ready(HttpInboundLink.java:286)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.sendToDiscriminaters(NewConnectionIniti alReadCallback.java:201)
    at com.ibm.ws.tcp.channel.impl.NewConnectionInitialRe adCallback.complete(NewConnectionInitialReadCallba ck.java:103)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.reque stComplete(WorkQueueManager.java:566)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.attem ptIO(WorkQueueManager.java:619)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager.worke rRun(WorkQueueManager.java:952)
    at com.ibm.ws.tcp.channel.impl.WorkQueueManager$Worke r.run(WorkQueueManager.java:1039)
    at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.j ava:1455)

    Your help is greatly appreciated.



  2. Re: Internal Drive Error (SQL Expception) in WebSphere Application Server

    I'm having exaclty the same problem.
    I'm doing repetitive queries to an AS400 database using this same driver. Sometimes, after a while when I prepare a statement, I got the same kind of stacktrace:

    java.sql.SQLException: Internal driver error. (class java.lang.InterruptedException)
    at com.ibm.as400.access.JDError.throwSQLException(JDE rror.java:521)
    at com.ibm.as400.access.AS400JDBCConnection.sendAndRe ceive(AS400JDBCConnection.java:2546)
    at com.ibm.as400.access.AS400JDBCStatement.commonPrep are(AS400JDBCStatement.java:1321)
    at com.ibm.as400.access.AS400JDBCPreparedStatement.(AS400JDBCPreparedStatement.java:182)
    at com.ibm.as400.access.AS400JDBCConnection.prepareSt atement(AS400JDBCConnection.java:1812)
    at com.ibm.as400.access.AS400JDBCConnection.prepareSt atement(AS400JDBCConnection.java:1635)
    at org.jboss.resource.adapter.jdbc.BaseWrapperManaged Connection.prepareStatement(BaseWrapperManagedConn ection.java:381)
    at org.jboss.resource.adapter.jdbc.WrappedConnection. prepareStatement(WrappedConnection.java:208)
    (but the same code has runned 30 times in a loop before without failing)

    This code runs in JBoss3.2.5 and I'm sure no one else is using the pooled connexion at the same time.

    After this error has occured once, all access to the connexion fail, and I'm forced to flush the pool to get rid of the malfunctioning connextion.

    Any help would be greatly appreciated....



+ Reply to Thread