2 Replies Latest reply on Sep 4, 2007 4:03 AM by ashishanand

    JBoss 4.0.4 java.sql.SQLException: No more data to read from

    ashishanand

      We have 2 machines each with identical JBoss 4.0.4 Server and Oracle 10g installation.
      We have an application (war file) installed on both the system.

      When trying to insert data into oracle database from within the application, it works fine on one machine, however, on the 2nd machine we encountered the following error.

      Oracle-ds.xml (for connection pooling) configuration on both the installation have identical configuration.


      2007-08-07 11:15:43,078 DEBUG [org.jboss.web.tomcat.tc5.Tomcat5] Saw org.jboss.system.server.started notification, starting connectors
      2007-08-07 11:15:43,093 INFO [org.apache.coyote.http11.Http11BaseProtocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
      2007-08-07 11:15:43,218 INFO [org.apache.jk.common.ChannelSocket] JK: ajp13 listening on /0.0.0.0:8009
      2007-08-07 11:15:43,234 INFO [org.apache.jk.server.JkMain] Jk running ID=0 time=0/94 config=null
      2007-08-07 11:15:43,234 INFO [org.jboss.system.server.Server] JBoss (MX MicroKernel) [4.0.4.GA (build: CVSTag=JBoss_4_0_4_GA date=200605151000)] Started in 22s:297ms
      2007-08-07 11:17:19,000 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: registering pool with interval 900000 old interval: 9223372036854775807
      2007-08-07 11:17:19,000 DEBUG [org.jboss.resource.connectionmanager.IdleRemover] internalRegisterPool: about to notify thread: old next: 1186457089000, new next: 1186457089000
      2007-08-07 11:17:40,015 WARN [org.jboss.resource.connectionmanager.TxConnectionManager] Connection error occured: org.jboss.resource.connectionmanager.TxConnectionManager$TxConnectionEventListener@3b9a5f[state=NORMAL mc=org.jboss.resource.adapter.jdbc.local.LocalManagedConnection@1a7d9e7 handles=1 lastUse=1186456656140 permit=true trackByTx=false mcp=org.jboss.resource.connectionmanager.JBossManagedConnectionPool$OnePool@d2ee5d context=org.jboss.resource.connectionmanager.InternalManagedConnectionPool@1f568f xaResource=org.jboss.resource.connectionmanager.TxConnectionManager$LocalXAResource@16c02df txSync=null]
      java.sql.SQLException: No more data to read from socket
      at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
      at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:146)
      at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:208)
      at oracle.jdbc.driver.T4CMAREngine.unmarshalUB1(T4CMAREngine.java:1118)
      at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMAREngine.java:1070)
      at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:478)
      at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
      at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:955)
      at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1168)
      at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3316)
      at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3400)
      at org.jboss.resource.adapter.jdbc.WrappedPreparedStatement.executeUpdate(WrappedPreparedStatement.java:251)


      Any help is appreciated.

      Thanks in advance.
      Regards,

        • 1. Re: JBoss 4.0.4 java.sql.SQLException: No more data to read
          vickyk

           

          Oracle-ds.xml (for connection pooling) configuration on both the installation have identical configuration.

          Is your application failing always on a particular instance of JBoss or it gives error on the last accessed Application ?



          • 2. Re: JBoss 4.0.4 java.sql.SQLException: No more data to read
            ashishanand

            I've found the cause of the problem. It happens because of we are using Oracle world lexer (setting) for indexing. If the index is deleted or the option is changed from world lexer to basic lexer it works fine. In Oracle 10g (10.2.0.1.0) using world lexer option for creating index will cause this problem. The indexer fails when there is a lot of text to be indexed, the amount of text... I cannot say for sure. (about 10 pages of text).

            Regards,