Atomikos Forum

There are 8 components running on Tomcat 6.0.  Each of these components is running with its own local transactional context.  If a component is shut down I can not delete the lock file for that single component without bringing Tomcat down.  This is because Tomcat has a hold on the lock file (not the component itself).  It would be nice to have the ability to deal with one component problem without having to bring full system down.  This is not a show stopper but are there any ways around this problem?

Hi,

What version of TransactionsEssentials are you referring to?

Thanks

Version 3.3.1.

Hello,
    I upgraded to 3.3.3.  When I shut the tomcat down the lck files disappear.
  Life is Good.
  Thanks,
Garth