[#HHH-3359] Loader leaks memory when ResultSet wrapping is enabled - Hibernate JIRA. This issue was already reported on the forums ( but I can find no actual JIRA entry.
![[#HHH-3359] Loader leaks memory when ResultSet wrapping is enabled - Hibernate JIRA](http://cdn.pearltrees.com/s/pic/th/resultset-wrapping-hibernate-54607720)
The issue is that when the hibernate.jdbc.wrap_result_sets property is set to true, ResultSets are never removed from the AbstractBatcher's resultSetsToClose set, eventually causing memory to fill up with ResultSet objects and their associated resources (like PreparedStatements). This issue was witnessed in 3.2.6, but a look at the 3.3 CR1 source code reveals that it's still in there. What happens: 1) org.hibernate.loader.Loader.doQuery calls org.hibernate.loader.Loader.getResultSet 2) org.hibernate.loader.Loader.getResultSet calls Batcher.getResultSet. 3) Loader then calls its wrapResultSetIfEnabled method to wraps the ResultSet in a ResultSetWrapper if the wrap_result_sets option is enabled. 4) In Loader.doQuery's finally block, Batcher.closeQueryStatement is called with the PreparedStatement and the wrapped ResultSet as parameters 5) closeQueryStatement does: if ( resultSetsToClose.remove( rs ) )
Issue Navigator - Hibernate JIRA. Hibernate - configuration.xml - hibernate, hibernate, jdbc, jdbc, jndi, jndi. SQLException: Io exception: Got minus. Java.sql.SQLException: Protocol. HI all, This has worked fine for very long, but starting a few days ago I started getting this error everytime the code tries to write (insert or update) into the db: java.sql.SQLException: Protocol violation The oracle code error is 17401 Trying to use another client like SqlDeveloper I can write with no problems.
Googleing for this error seems it is related to bad jdbc driver version, but it doesn't look the case...since my application uses JDK1.5., I'm using ojdbc14.jar, and it worked fine for a long time. My DBA saied that the only thing that is changed in last days is that he setted this parameter: cursor_sharing=SIMILAR instead of EXACT But I have no idea if this could be related to my problem. Does any of you have any idea of how to solve this?
Mattia. [#HHH-3159] Oracle 11g - desupport of oracle.jdbc.driver - Hibernate JIRA. With Oracle 11g, the deprecated package oracle.jdbc.driver no longer exists and this causes issues with all OracleDialect classes making it impossible to use Hibernate.
![[#HHH-3159] Oracle 11g - desupport of oracle.jdbc.driver - Hibernate JIRA](http://cdn.pearltrees.com/s/pic/th/oracle-desupport-hibernate-54577324)
This issue affects all of the following classes: Oracle9iDialect.java Oracle9Dialect.java Oracle10gDialect.java The line error in question is: Class types = ReflectHelper.classForName("oracle.jdbc.driver.OracleTypes"); This simply needs to be changed to: Class types = ReflectHelper.classForName("oracle.jdbc.OracleTypes"); From the Oracle 11g readme.txt "In Oracle JDBC release 9.0.1 customer use of the classes in that package was deprecated.
A new package, oracle.jdbc, was introduced and customers were advised to begin using the interfaces and classes defined in oracle.jdbc. Problems of hibernate calling oracle. JDBC Drivers release 11.1.0.7.0 - Production README. FishEye: Annotated - Hibernate/core/patches/hibernate-3.3.2.GA_CP04_JBPAPP-9172/core/src/main/java/org/hibernate/dialect/Oracle10gDialect.java. Hibernate dialect for Oracle Database 11g. Java - How to call Oracle Function or Procedure using Hibernate 4 (EntityManager) or JPA 2.