SQLj Applications must close Connection Context after usage

Resolving The Problem

There are two ways to resolve the issue:

• The application must close the SQLj Connection Context when done using it. Close the context with the CLOSE_CONNECTION option (or without any parameter, which means the same thing) if you will no longer be using the connection handle. Close the context with the KEEP_CONNECTION option if you intend to continue using the connection handle, in which case you are responsible for closing the connection handle once you are done with it. Failure to do so might result in a connection leak.
  
  For example:
  If your context is myContext and your connection is con, then the code would be:
  
  

myContext.close(ConnectionContext.CLOSE_CONNECTION);

or myContext.close(ConnectionContext.KEEP_CONNECTION); //...continue using the connection con.close();

• The SQLj must be translated using the -db2optimize option and sqlj customization must be run on the SQLj profiles. Doing that will result in DB2 creating a default Context under the covers that is cached inside of WebSphere Application Server. Note that this option will also provide better performance due to the caching of Connection Context.