We modified the tomcat script so it killed the process group, that resolved some of the issues as I recall.
The other thing is that you may want to have unpackWAR set to false on the context, otherwise when you update the war file tomcat will continue to use the previously unpacked war vs. the new one by default. On Feb 10, 2014, at 13:48 , Brian Coca <[email protected]> wrote: > I just remembered that I had so many problems with tomcat 7 start/stop that > I ended up writing my own init script (will need to look for it). This was > sans ansible, I was using puppet at the time. > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
