JDBC 8.1.6.0.1 THIN w/ Java 1.3 Memory Question

Question

JProbe indicates that the number of TTC7 and DBItem objects created by Oracle is huge and grows with each use of a new Query statement. The objects are NOT freed when the resultset is closed OR when the preparedstatement is closed. The only way to get the objects release is to close the connection. I would like to know if anybody else is experiencing this problem and if there is a resolution.
For example calling batchLoad for different databases and different queries can create a TON of these objects - in one app over 100K of them.
public static Collection batchLoad(String sqlWhere) throws Exception
PreparedStatement ps = batchPrepare(sqlWhere);
Collection c = batchExecute(ps, null);
ps.close();
return c;
public static Collection batchExecute(PreparedStatement stmt, Object [] params) throws Exception
Collection c = null;
c = new Collection();
ResultSet r = null;
try
SQLUtil.setParams(stmt, params);
r = stmt.executeQuery();
while (r.next())
Object obj = null;
obj = doLookup(getPK(r), r, 0);
c.add(obj);
catch (SQLException sqle)
System.out.println(sqle);
finally
try{if (r!=null) r.close();} catch(Exception e) {System.out.println("Bad ResultSet release!");}
return c;
public static PreparedStatement batchPrepare(String sqlWhere) throws Exception
String whereClause = null;
if ((sqlWhere == null) | | (sqlWhere.length()==0))
whereClause = " ";
else
whereClause = " where " + sqlWhere;
PreparedStatement stmt = DBConnManager.DBConnIDR.prepareStatement("select " + DBObj.buildColList(DBTableRefName, ColNames) + " from " + DBTableRefName + whereClause);
return stmt;
Thanks

Answer 1

no production version of the oracle products (oas, ias, rdbms, jdbc, sqlj, etc.) are certified to be used with jdk 1.3.
null