> From: Zaq Rizer [mailto:[email protected]]
> Subject: Re: Frustrating refusal to serve *some* pages, scripts,
> images.
> 
> Jun 8, 2009 3:35:15 PM org.apache.catalina.core.StandardWrapperValve
> invoke
> SEVERE: Servlet.service() for servlet default threw exception
> javax.servlet.ServletException: Servlet execution threw an exception

This is odd; I would have expected another stack trace of the original 
exception to be displayed, immediately following this one.

Why is this stack trace different from the one you posted before?  What 
changed?  The original one should have also had an additional "caused by" stack 
trace with it.  It's very odd that you don't seem to be getting those.

> Jun 8, 2009 3:35:00 PM org.apache.catalina.core.StandardContext
> addApplicationListener
> INFO: The listener "org.apache.tiles.web.startup.TilesListener" is
> already configured for this context. The duplicate definition has been
> ignored.

The above is a cosmetic bug in the version of Tomcat you're using and can be 
ignored.

> Jun 8, 2009 3:35:00 PM
> org.apache.tiles.context.ChainedTilesApplicationContextFactory init
> WARNING: Cannot find TilesContextFactory class
> org.apache.tiles.portlet.context.PortletTilesApplicationContextFactory

I'm not familiar with tiles, but the above doesn't look good.

> Jun 8, 2009 3:35:01 PM org.apache.catalina.core.StandardContext
> addApplicationListener
> INFO: The listener "listeners.ContextListener" is already configured
> for this context. The duplicate definition has been ignored.

Another cosmetic-only message.

> /I/ don't see anything, do you?

Just the TilesContextFactory warning.

 - Chuck


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY 
MATERIAL and is thus for use only by the intended recipient. If you received 
this in error, please contact the sender and delete the e-mail and its 
attachments from all computers.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to