IDP troubleshooting

Doug Tomer dtomer at
Thu May 12 17:04:13 EDT 2016

Yes, I restarted Tomcat.  I don't know how to restart Tomcat while clearing
all of it's working state.  Can you tell me how to do that, or point me in
the right direction?  I'm also not sure if I am running with an unpacked
warfile.  I see the idp.war unpacked in /var/lib/tomcat6/webapps/idp,
and /var/cache/tomcat6/work/Catalina/localhost/idp/org/apache/jsp, but
you're probably talking about something else, right?

I restored a snapshot of our shibboleth-idp prior to the yum updates and
confirmed it was working correctly, than applied all the yum updates
excluding tomcat6*, and the systems still works correctly, so I agree with
you that it's the updated Tomcat.  Any suggestions you can give me to help
troubleshoot the issue with this Tomcat upgrade would be greatly
appreciated.  I will also open a case with Red Hat.

Thanks again for your help.

On Thu, May 12, 2016 at 2:07 PM, Cantor, Scott <cantor.2 at> wrote:

> > Thanks for the reply.  Here's the version info and the error from the
> idp-
> > process.log.  Please let me know if there's anything else I can provide
> or
> > steps to take to help troubleshoot.
> Did you restart Tomcat? Did you do so while clearing all of its working
> state? Are you running with an unpacked warfile? Etc.
> Seems clear your webapp instance is corrupted and needs to be restarted
> fresh.
> Again, this is because you updated Tomcat. You cannot do that unattended,
> and as such, there is little value in using a packaged version since it
> can't be updated like other packages safely. Those who have a different
> experience with that approach can, I guess, suggest how to avoid the result
> you got, because I don't know of one.
> -- Scott
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list