How are you trying to remove all of the attributes from the session, and
could you not just call session.invalidate() ?
This can occur if, for example, you get the attribute names out of the
session in an enumeration, remove one of them from the session with a
removeAttribute and then try and interate through the enumeration. It gets
to the attribute that you've removed and then breaks, since it no longer
exists.
Cheers,
Simon
This email and any attachments are confidential and are intended only for
the addressee. If you are not the intended recipient of this email and have
received it in error, please notify the sender immediately by reply email
and then delete it from your system.
-----Original Message-----
From: Arun Jayaprakash [mailto:[EMAIL PROTECTED]]
Sent: 21 May 2001 08:56
To: Orion-Interest
Subject: java.util.ConcurrentModificationException
Hello everybody,
I recently switched over from Apache Tomcat v3.2.1 to Orion
v1.4.5. I deployed an application (that I had developed
with Tomcat) using Orion and did the necessary configuring.
The application works fine until the point when I logout.
Tomcat never gave any trouble, but Orion keeps throwing a
java.util.ConcurrentModificationException. This exception
occurs when I remove all the attributes in my session
object.
Can anybody tell me why this happens and how to remove it?
Thanks and regards,
Arun Jayaprakash.
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/
