This content has been marked as final. Show 25 replies
Same stack trace. Obviously you still have the old JAR somewhere, probably in your Tomcat or application lib directory.
"My classpath is:
Is that what the program prints out from the line I asked you to put in? I need to see that. Put the ojdbc6.jar
ahead of the QTJava.zip file in the classpath. What's in that thing? Could it have a copy of the driver classes in it?
Is it a standalone program?
I guess it is a JSP/web application. You should place the jars in WEB-INF/lib (or Tomact/lib).
Which code is generating this error?
And this seems to be relatively fresh drivers (220.127.116.11 driver against 18.104.22.168 DB):
Caused by: java.sql.SQLException: Protocol violation at oracle.jdbc.driver.T4CTTIfun.readRXH(T4CTTIfun.java:532) at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:319) at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186) at oracle.jdbc.driver.T4C7Ocommoncall.doOROLLBACK(T4C7Ocommoncall.java:68) at oracle.jdbc.driver.T4CConnection.doRollback(T4CConnection.java:642) at oracle.jdbc.driver.PhysicalConnection.rollback(PhysicalConnection.java:3716) at oracle.jdbc.OracleConnectionWrapper.rollback(OracleConnectionWrapper.java:145) at org.hibernate.transaction.JDBCTransaction.rollbackAndResetAutoCommit(JDBCTransaction.java:213) at org.hibernate.transaction.JDBCTransaction.rollback(JDBCTransaction.java:192) ... 57 more
Add the good but you have to also remove the old.
If you see 'ttc7' in any line of your stacktrace, the
old driver is somewhere ahead of the new driver
in the classpath being used by tomcat.
As you may see there is no TTC7 in my trace - T4C only. And there are no old drivers anywhere on the classpath.
Problem exists anyway.
Yes. You need to open an official JDBC driver SR.
If the problem would be reproducible - sure, but it is intermittent, we have meet issue a couple of hundred times per several hundred thousands requests.
Oracle driver support should be able to proceed with helping you, based on the stack trace
you show, and the new info you provide, that this connection failure is intermittent.
Sorry, for not being clear right from the start - but they are not connection failures, they occur at different points, but the most often on rollback.
Anyhow, I would try to open an SR.
By 'connection failure' I meant 'failure of the connection', not 'failure to connect'.
When/if there is a protocol failure, the connection is usually unuseable afterwards.
If it happens sometimes during other calls besides the one you show in your stack
trace, include as many different ones as possible.