Fix for bug 1378926 - error 8448 with java.lang.OutOfMemoryError Trafodion SQL processes dump java heap at $MY_SQROOT/logs in the format java_pid<pid>.hprof when java.lang.OutOfMemoryError exception is raised.
There were local references/global references that were not being deleted in the trafodion code and that was causing leak in Java objects.
HTableClient_JNI objects are now cleaned up from the Java side if the corresponding java objects are left in in-use pool at the time of ODBC/JDBC disconnect. This takes care of memory leak on the C++ heap and java object heap for such cases.
Fix for bug 1373179 Native Hbase Table access via Trafodion dumps core. The error messages passed from Java layer to JNI was not handled correctly leading to core dump. Fixed the error handling code correctly.
Also flagged three Java Objects in HTableClient for gc earlier to reduce the java object memory usage.
Separated out the relase and flush HTableClient as two different operations to ensure that HTableClient can be continued to be used even after flush.
Changed NAString in error routines to use the relevant heap instead of system heap.