like a
Vector.
/Arup
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: 08 September 2005 04:51
To: Tomcat Users List
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
From: Len Popp [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat/JVM hangs
On 9/7/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: Len Popp [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
So if I want to *safely* call session.setAttribute or
session.getAttribute
I have to make sure the calls
coming late to the party with:
http://blogs.opensymphony.com/plightbo/archives/000175.html
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On 9/7/05, GB Developer [EMAIL PROTECTED] wrote:
coming late to the party with:
http://blogs.opensymphony.com/plightbo/archives/000175.html
I had read your blog when you originally posted it, and thought it was
the most interesting blog I had read in months. IMO, given the average
size of the
--- Remy Maucherat [EMAIL PROTECTED] wrote:
On 9/7/05, GB Developer
[EMAIL PROTECTED] wrote:
coming late to the party with:
http://blogs.opensymphony.com/plightbo/archives/000175.html
I had read your blog when you originally posted it,
and thought it was
the most interesting blog I
. September 2005 21:11
An: Tomcat Users List
Betreff: Re: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
--- Remy Maucherat [EMAIL PROTECTED] wrote:
On 9/7/05, GB Developer
[EMAIL PROTECTED] wrote:
coming late to the party with:
http://blogs.opensymphony.com/plightbo
From: Wade Chandler [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
so it's not just a getAttribute call or even
50 million of them alone going to cause HashMap to
lock, but rather the Object being in an intermediate
step when get is called
--- Caldarale, Charles R
[EMAIL PROTECTED] wrote:
From: Wade Chandler
[mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat/JVM hangs in
session.getAttribute / HashMap.get()
so it's not just a getAttribute call or even
50 million of them alone going to cause HashMap to
lock, but rather
how I can work around this. Am I missing something? Or do
the Tomcat guys have to fix it?
--
Len
On 9/6/05, Caldarale, Charles R [EMAIL PROTECTED] wrote:
From: Arup Vidyerthy [mailto:[EMAIL PROTECTED]
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
Does this mean
From: Len Popp [mailto:[EMAIL PROTECTED]
Subject: Re: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
Inside Tomcat, references to the hashmap in question are synchronized
on the hashmap object itself, StandardSession.attributes (see
org.apache.catalina.session.StandardSession
I have seen instances of a HashMap whose entries got circularly
linked, I assume, due to updates which where not thread safe.
Any thread using a get() on such a HashMap will spin forever
chasing its tail.
Cheers,
Larry
-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
On Tue, 2005-09-06 at 08:47 -0400, Larry Isaacs wrote:
I have seen instances of a HashMap whose entries got circularly
linked, I assume, due to updates which where not thread safe.
Any thread using a get() on such a HashMap will spin forever
chasing its tail.
Cheers,
Larry
Could be
-Original Message-
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: Tuesday, September 06, 2005 9:03 AM
To: Tomcat Users List
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
On Tue, 2005-09-06 at 08:47 -0400, Larry Isaacs wrote:
I have seen instances
If I understand you correctly your scenario is:
HashMap Entry has a linked list of X entries at one position
and entry[Y] is poiting to the first entry instead of next or null?
Correct.
But how can that happen? a JVM / Core Api bug?
The error is likely in webapp code, since the
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
and replace all req.getSession().setAttribute(beanName, beanValue) in
code with the call to this method (same for remove) and I've solved my
problem?
Unfortunately, you
regards...
Arup Vidyerthy.
-Original Message-
From: Caldarale, Charles R [mailto:[EMAIL PROTECTED]
Sent: 06 September 2005 15:54
To: Tomcat Users List
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Subject: RE
2005 15:54
To: Tomcat Users List
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
and replace all req.getSession().setAttribute(beanName, beanValue
From: Arup Vidyerthy [mailto:[EMAIL PROTECTED]
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
Does this mean that all session.setAttribute() and
session.getAttribute() should always be synchronised
That's the conclusion I'm reluctantly coming
On Tue, 2005-09-06 at 11:00 -0500, Caldarale, Charles R wrote:
From: Arup Vidyerthy [mailto:[EMAIL PROTECTED]
Subject: RE: Tomcat/JVM hangs in session.getAttribute / HashMap.get()
Does this mean that all session.setAttribute() and
session.getAttribute() should always be synchronised
It seems possible to be that one user simply pressing the reload button
a few times quickly while the same page is not yet loaded can cause sync
problems to his own session; and you can't control the user.
Err... does anybody have a replacement class for HttpServlet ? A simple
access
20 matches
Mail list logo
