Matthew Serrano wrote:
> I figured out how to replicate my issue:
>
> If I log in to my application, deploy a war file to webapps, and then
> refresh my page at the same time the app is automatically reloading, I
> can cause the error. This is fairly difficult to do consistently but
> given a fe
I figured out how to replicate my issue:
If I log in to my application, deploy a war file to webapps, and then refresh
my page at the same time the app is automatically reloading, I can cause the
error. This is fairly difficult to do consistently but given a few tries I can
make it happen. I ch
I think I found a way to replicate the issue: I autodeploy my war file (e.g.
copy updated war to webapps and let resin reload it). After a few deployments
this issue will occur so maybe there is some corruption caused by autodeploy?
matt
On Aug 16, 2010, at 9:57 AM, Matthew Serrano wrote:
> I
I am not intentionally making the call from another thread but would this be
the case if the server had restarted? Maybe there is some combination of the
session expiring and the server restarting that causes some issue? The code is:
HttpSession mySession = req.getSession(false);
if (mySession !=
Matthew Serrano wrote:
> I am running resin 4.0.7 and I store a user object in the session using
> "User_Bean" as a key. Everything works fine most of the time but it seems
> when my session expires and I have not logged out, every subsequent call to
> get this object returns some HashMap instea
