dtomer at allegheny.edu
Thu May 12 17:07:14 EDT 2016
Christopher - thanks for the reply. We are using the RHEL-provided Java.
Not the openjdk, but the oracle package, if that matters. Backing out the
tomcat update seems to resolve the error. but if you're thinking it's
really a Java issue, do you have some troubleshooting ideas I can try?
Thanks again for your help.
On Thu, May 12, 2016 at 2:12 PM, Christopher Bongaarts <cab at umn.edu> wrote:
> On 5/12/2016 1:07 PM, Cantor, Scott wrote:
> 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.
> We've seen similar issues with Tomcat when we run it with the
> RHEL-provided Java (which we do on our Grouper servers but not our Shib
> servers) and Java is updated out from under us. RHEL-provided Apache seems
> to handle upgrades fine, though.
> %% Christopher A. Bongaarts %% cab at umn.edu %%
> %% OIT - Identity Management %% http://umn.edu/~cab %%
> %% University of Minnesota %% +1 (612) 625-1809 %%
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the users