tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Thomas <>
Subject Re: ClassCastException org.apache.jasper.runtime.ELContextImpl cannot be cast to org.apache.jasper.el.ELContextImpl
Date Fri, 10 Aug 2012 09:04:25 GMT
On 10/08/2012 05:13, Dale Ogilvie wrote:

> It does concern me that there was a known issue that was fixed, and here
> I am seeing this EL impl instance sharing between apps in the "fixed
> version".

It is certainly worth looking at to see what is going on. It might be
that there is another reference being retained somewhere or it could be
something the Jetty code is interfering with.

> Mark's "Don't do that" in terms of loading container jars in apps
> generally is a solution, but the trick is we didn't create the problem
> intentionally. We got scuppered by a maven dependency and Tomcat didn't
> protect us. Ideally bad behaviour of an app should not break the other
> apps in the container.

There are always ways for one app to impact another. CPU, I/O, network
traffic etc. Ways to separate apps in order of increasing separation:
- use a security manager (likely to have expensive side-effects)
- separate JVMs
- separate VMs
- separate physical machines
- separate networks

In most cases separate JVMs will suffice.


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message