Results 1 to 4 of 4
  1. #1
    Join Date
    Mar 2006
    Posts
    2

    Unanswered: Oracle SQLException: No more data to read from socket

    I'm getting this error while trying to call a stored procedure. This happens only 8 times in 1000 attempts.
    Basically I call a procedure which returns some values.
    The error stack shows -
    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(T4CMA REngine.java:1118)
    at oracle.jdbc.driver.T4CMAREngine.unmarshalSB1(T4CMA REngine.java:1070)
    at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java: 478)
    at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4 CCallableStatement.java:215)

    I am working on the following -
    RDBMS version : 10.2.0.1.0
    JDBC driver version: 10.2.0.1.0
    The logs seem to indicate that the call fails to go through just before setting an out paramter using "ocs.registerOutParameter" with a user defined object type.
    Could this be an issue with connection pooling or setting the connection map properly for user defined object types or something else?
    Thanks in advance for any help!

  2. #2
    Join Date
    May 2004
    Location
    Dominican Republic
    Posts
    721
    You said: happens only 8 times in 1000 attempts. So, when you run these 8 again, does it happens again for those 8 ??

  3. #3
    Join Date
    Mar 2006
    Posts
    2
    Quote Originally Posted by JMartinez
    You said: happens only 8 times in 1000 attempts. So, when you run these 8 again, does it happens again for those 8 ??

    Hey JMartinez, the issue is very intermittent. I called the same prodecure 1000 times to see how many times - i get this error. Hence the stat.

  4. #4
    Join Date
    May 2004
    Location
    Dominican Republic
    Posts
    721
    I see. Dont know what else to tell, other than socket problems are a pain in the arse sometimes and since they come from java's built methods. I would try using different intervals (like if you execute the procedure every 1 second, I would try raising this interval to something like 5 seconds) and see what happens.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •