changes in login pages - kills IDP?

[Chad La Joie]

The behavior your describing is uncommon for JSP changes.  Those are
compiled at runtime when a request comes in and if the compilation
fails Tomcat spits out some gross stacktrace.

So I'd do what Paul just suggested and then log in to the Tomcat
manager and see what it says the status of the IdP app and what
context path it claims to be mounted under.  I'm wondering if the
web.xml file is corrupted in some way.  Did you add anything to it
(e.g., servlet filters or taglibs) when doing the JSP updates?  If
taglibs, perhaps a TLDs is corrupted to.  Whatever it is, it's
something Tomcat is checking *before* it starts up anything to do with
the IdP itself.

On Mon, Mar 19, 2012 at 17:35, Oleg Chaikovsky
<oleg.chaikovsky at aegisusa.net> wrote:
>
>
> Yeah - I pretty much felt this was the issue but the catalina.out log
> file did not offer succinct clues to me (well, at least that pointed me
> in the right direction). the threads errors were well known in this list
> that its something that can be ignored. it also showed the deployment
> descriptor for idp.xml which made me wonder why that showed up.
>
> I realize this is the shib list, and not the tomcat list. If you can
> point me to a possible avenue
> of solution I will go there otherwise I will check Tomcat lists

-- 
Chad La Joie
www.itumi.biz
trusted identities, delivered