Re: Bug votes needed..you really should read this..Tomcat/JVM hangs in session.getAttribute / HashMap.get()

2005-09-07 Thread Leon Rosenberg
I've send a similar mail to the struts-users mailing list. Maybe other
affected jakarta projects should be notified too.

Leon
 

> -Ursprüngliche Nachricht-
> Von: Wade Chandler [mailto:[EMAIL PROTECTED] 
> Gesendet: Mittwoch, 7. September 2005 23:05
> An: Tomcat Users List
> Betreff: Re: Bug votes needed..you really should read 
> this..Tomcat/JVM hangs in session.getAttribute / HashMap.get() 
> 
> This bug doesn't only affect code where you access the 
> session using session.getAttribute("") or 
> session.setAttribute("",""), but also affects jsp tags such 
> as jsp:useBean with scope="session".  I'm guessing that pages 
> using EL and accessing the session are going to be broken as 
> well I didn't look that far, but if you are using the jsp 
> page context and using the methods 
> JspContext.get/setAttribute and using SESSION_SCOPE you will 
> be affected by the bug.
> 
> The big picture here is that we can't control the users, and 
> if they make multiple threads access the session they can and 
> more than likely crash your server.  Remember if you access 
> the session from your application they can hit reload a few 
> times and cause this or if you use frames.  They could even 
> have more than one browser instance opened.  One the CPU will 
> start to get used up, and two your Tomcat threads will run out.
> 
> Affected versions:
> Tomcat 5.0.x
> Tomcat 5.5.x
> 
> If you don't have a bugzilla account maybe you can set one up 
> and vote for the bug.  It helps all of us to vote for bugs.  
> So, read up on it, and make a decision.  Don't read only a 
> few comments about the bug as the entire picture isn't 
> discussed.  Read them all and know what the issue is.  Here 
> is the bug:
> 
> http://issues.apache.org/bugzilla/show_bug.cgi?id=36541
> 
> Again, setup a bugzilla account and vote for this bug.
>  If an application doesn't use the session at all it won't be 
> affected, but remember if you use sessions and notice your 
> Tomcat crashing or hanging then this is probably your issue.
> 
> Wade
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Bug votes needed..you really should read this..Tomcat/JVM hangs in session.getAttribute / HashMap.get()

2005-09-07 Thread Wade Chandler
This bug doesn't only affect code where you access the
session using session.getAttribute("") or
session.setAttribute("",""), but also affects jsp tags
such as jsp:useBean with scope="session".  I'm
guessing that pages using EL and accessing the session
are going to be broken as well I didn't look that far,
but if you are using the jsp page context and using
the methods JspContext.get/setAttribute and using
SESSION_SCOPE you will be affected by the bug.

The big picture here is that we can't control the
users, and if they make multiple threads access the
session they can and more than likely crash your
server.  Remember if you access the session from your
application they can hit reload a few times and cause
this or if you use frames.  They could even have more
than one browser instance opened.  One the CPU will
start to get used up, and two your Tomcat threads will
run out.

Affected versions:
Tomcat 5.0.x
Tomcat 5.5.x

If you don't have a bugzilla account maybe you can set
one up and vote for the bug.  It helps all of us to
vote for bugs.  So, read up on it, and make a
decision.  Don't read only a few comments about the
bug as the entire picture isn't discussed.  Read them
all and know what the issue is.  Here is the bug:

http://issues.apache.org/bugzilla/show_bug.cgi?id=36541

Again, setup a bugzilla account and vote for this bug.
 If an application doesn't use the session at all it
won't be affected, but remember if you use sessions
and notice your Tomcat crashing or hanging then this
is probably your issue.

Wade

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]