ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mario Ds Briggs <mario.bri...@in.ibm.com>
Subject Re: Prepared Statement cache
Date Wed, 22 Jul 2009 07:05:33 GMT
The statement cache is configured on the Data Source properties in WAS. You
probably want to check with your WAS admin what's the minimal way of
flushing it without bouncing WAS itself ( bouncing the app alone wont help)


             Michael Schall                                                
             l.com>                                                     To 
             22/07/2009 03:38                                           cc 
             Please respond to         Re: Prepared Statement cache        

Anyway to just tell the webservers (I assume JNDI) to drop all prepared

On Tue, Jul 21, 2009 at 4:09 PM, Glenn Barnard <barnardglenn@gmail.com>
  restart your webservers!

  On Tue, Jul 21, 2009 at 5:00 PM, Michael Schall <mike.schall@gmail.com>
   We run are running iBATIS within WebSphere 6.1 on Windows using JNDI
   against a DB2 database.  During a performance tuning session we found a
   query using an index that did not have a vital column.  We added the
   missing column to the end of the index on a test database and using a
   db2 query analyzer we saw a big performance gain.  We moved the index to
   our production servers and see similar gains using db2 tools, however we
   do not see the benefit in the WebSphere application.  How/Where are are
   prepared statements cached and how can I clear them to get a plan that
   takes advantage of the new index.



To unsubscribe, e-mail: user-java-unsubscribe@ibatis.apache.org
For additional commands, e-mail: user-java-help@ibatis.apache.org

View raw message