While evaluating Resin 4.0.16 we are seeing something that makes me
really concerned. It appears as if after a redeploy there can be two
instances of our main app running.
I was made aware of this by noticing that timed servlets (run-at ...
/) were having concurrency issues and logging the
On 04/04/2011 12:43 AM, Mattias Jiderhamn wrote:
While evaluating Resin 4.0.16 we are seeing something that makes me
really concerned. It appears as if after a redeploy there can be two
instances of our main app running.
I was made aware of this by noticing that timed servlets (run-at ...
Scott Ferguson wrote (2011-04-04 18:47):
On 04/04/2011 12:43 AM, Mattias Jiderhamn wrote:
While evaluating Resin 4.0.16 we are seeing something that makes me
really concerned. It appears as if after a redeploy there can be two
instances of our main app running.
I was made aware of this by
On 04/04/2011 10:02 AM, Mattias Jiderhamn wrote:
Scott Ferguson wrote (2011-04-04 18:47):
On 04/04/2011 12:43 AM, Mattias Jiderhamn wrote:
While evaluating Resin 4.0.16 we are seeing something that makes me
really concerned. It appears as if after a redeploy there can be two
instances of
This problem seems to be more pervasive in Resin 4.0.16 pro. I am now
seeing other application classes that the Resin EnvironmentClassLoader
is trying to load but it can't find them. I am getting the error
java.lang.ClassNotFoundException because the
EnvironmentClassLoader[resin-system:] is
I am wondering if this problem is related to the HTTP session timing
out. In the ROOT web application, we have the session time out set to
70 minutes:
WEB-INF/web.xml
session-config
session-timeout70/session-timeout
/session-config
I received another ClassNotFoundException from the
On 04/04/2011 11:39 AM, Keith Fetterman wrote:
I am wondering if this problem is related to the HTTP session timing
out. In the ROOT web application, we have the session time out set to
70 minutes:
WEB-INF/web.xml
Possibly. I've filed it as a bug.
The Java deserializer requires a
On 04/04/2011 10:02 AM, Mattias Jiderhamn wrote:
Scott Ferguson wrote (2011-04-04 18:47):
On 04/04/2011 12:43 AM, Mattias Jiderhamn wrote:
While evaluating Resin 4.0.16 we are seeing something that makes me
really concerned. It appears as if after a redeploy there can be two
instances of
Hi Scott,
Thanks filing this as a bug. I ran some more tests and it looks like
its related to the HTTP session timing out or being invalidated. If a
request for that session occurs after the timeout, I see the
EnvironmentClassLoader exceptions.
Keith
On 04/04/2011 11:55 AM, Scott Ferguson
