If sanity checking is enabled, the cache manager runs a stock query to verify that connections are ready for use before placing them back in the cache. Sanity checking prevents errors that occur when components release a connection that is not ready for use by another component. For example, there may be pending results on the connection, causing an error when the next component to use the connection tries to send a command.
If you have debugged the results handling in your application, you can improve performance by disabling sanity checking on the Caching tab in the EAServer Manager Cache Properties dialog box or by using jagtool to set the com.sybase.jaguar.conncache.checkallowed property to false.
