6:27 a.m.
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0, 3.1.5
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:35 a.m.
New subject: [JBoss JIRA] Updated: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Stanimir Stamenkov updated RF-3631:
-----------------------------------
Attachment: test-cluster-session.ear
Deploy into the the 'all' server configuration ($JBOSS_HOME/server/all/deploy),
then navigate to <http://server/cluster-session/test.seam>;. Open the same page in
10-20 windows - by Ctrl+clicking the "Test" heading link in Firefox, for
example. Watch the JBoss server console for a ConcurentModificationException error - give
it enough time to happen (e.g. 5 minutes). Here's full stack trace of the exception I
get with this example:
12:31:28,687 ERROR [JBossCacheService] externalizeSession(): exception occurred
externalizing session SessionBasedClusteredSession[id: 2682B8A2A5A776CF13C4D86E33218059
lastAccessedTime: 1212571888609 version: 289 lastOutdated: 0]
java.util.ConcurrentModificationException
at
org.apache.commons.collections.map.AbstractLinkedMap$LinkIterator.nextEntry(AbstractLinkedMap.java:555)
at
org.apache.commons.collections.map.AbstractLinkedMap$LinkMapIterator.next(AbstractLinkedMap.java:367)
at
org.apache.commons.collections.map.AbstractHashedMap.doWriteObject(AbstractHashedMap.java:1179)
at org.apache.commons.collections.map.LRUMap.doWriteObject(LRUMap.java:380)
at org.apache.commons.collections.map.LRUMap.writeObject(LRUMap.java:364)
at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at
org.apache.commons.collections.map.AbstractHashedMap.doWriteObject(AbstractHashedMap.java:1180)
at org.apache.commons.collections.map.LRUMap.doWriteObject(LRUMap.java:380)
at org.apache.commons.collections.map.LRUMap.writeObject(LRUMap.java:364)
at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at
java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1380)
at sun.reflect.GeneratedMethodAccessor122.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:917)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1339)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at
org.jboss.web.tomcat.service.session.SessionBasedClusteredSession.writeExternal(SessionBasedClusteredSession.java:175)
at
org.jboss.web.tomcat.service.session.JBossCacheService.externalizeSession(JBossCacheService.java:1027)
at
org.jboss.web.tomcat.service.session.JBossCacheService.putSession(JBossCacheService.java:316)
at
org.jboss.web.tomcat.service.session.JBossCacheClusteredSession.processSessionRepl(JBossCacheClusteredSession.java:121)
at
org.jboss.web.tomcat.service.session.JBossCacheManager.processSessionRepl(JBossCacheManager.java:1097)
at
org.jboss.web.tomcat.service.session.JBossCacheManager.storeSession(JBossCacheManager.java:652)
at
org.jboss.web.tomcat.service.session.InstantSnapshotManager.snapshot(InstantSnapshotManager.java:49)
at
org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(ClusteredSessionValve.java:98)
at
org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at
org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:157)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
at
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:446)
at java.lang.Thread.run(Thread.java:595)
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0, 3.1.5
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:41 a.m.
New subject: [JBoss JIRA] Commented: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=comments#action_12415525 ]
Stanimir Stamenkov commented on RF-3631:
----------------------------------------
The example basically consists of a Seam component ("sample") which has a
'list' property returning randomly generated items every time and a Facelets page
using <a4j:poll> component causing the list to re-render. Using this minimal
example I need more time (say 2-3 minutes) to hit the problem, but in my real application
it happens quite often even with only two windows/tabs opened.
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.2.0, 3.1.5
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:42 a.m.
New subject: [JBoss JIRA] Commented: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=comments#action_12415945 ]
Nick Belaevski commented on RF-3631:
------------------------------------
For 3.2.0.SR1:
java.util.ConcurrentModificationException
at java.util.LinkedHashMap$LinkedHashIterator.nextEntry(LinkedHashMap.ja
va:365)
at java.util.LinkedHashMap$EntryIterator.next(LinkedHashMap.java:384)
at java.util.LinkedHashMap$EntryIterator.next(LinkedHashMap.java:383)
at java.util.HashMap.writeObject(HashMap.java:1037)
at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:91
7)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
39)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
a:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at java.util.HashMap.writeObject(HashMap.java:1039)
at sun.reflect.GeneratedMethodAccessor96.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:91
7)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
39)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
a:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java
:1375)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
47)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
a:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.
java:1380)
at sun.reflect.GeneratedMethodAccessor103.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:91
7)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:13
39)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.jav
a:1290)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1079)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:302)
at org.jboss.web.tomcat.service.session.SessionBasedClusteredSession.wri
teExternal(SessionBasedClusteredSession.java:175)
at org.jboss.web.tomcat.service.session.JBossCacheService.externalizeSes
sion(JBossCacheService.java:1027)
at org.jboss.web.tomcat.service.session.JBossCacheService.putSession(JBo
ssCacheService.java:316)
at org.jboss.web.tomcat.service.session.JBossCacheClusteredSession.proce
ssSessionRepl(JBossCacheClusteredSession.java:121)
at org.jboss.web.tomcat.service.session.JBossCacheManager.processSession
Repl(JBossCacheManager.java:1097)
at org.jboss.web.tomcat.service.session.JBossCacheManager.storeSession(J
BossCacheManager.java:652)
at org.jboss.web.tomcat.service.session.InstantSnapshotManager.snapshot(
InstantSnapshotManager.java:49)
at org.jboss.web.tomcat.service.session.ClusteredSessionValve.invoke(Clu
steredSessionValve.java:98)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValv
e.java:84)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.j
ava:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.j
ava:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedC
onnectionValve.java:157)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineVal
ve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.jav
a:262)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java
:844)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.proce
ss(Http11Protocol.java:583)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:44
6)
at java.lang.Thread.run(Thread.java:595)
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:44 a.m.
New subject: [JBoss JIRA] Commented: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=comments#action_12415946 ]
Nick Belaevski commented on RF-3631:
------------------------------------
To reproduce:
1. run -c all
2. navigate to http://localhost:8080/cluster-session/test.seam
3. hold ctrl and quickly click link several times
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:46 a.m.
New subject: [JBoss JIRA] Updated: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Nick Belaevski updated RF-3631:
-------------------------------
Fix Version/s: 3.1.6
3.2.2
Assignee: Alexander Smirnov
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Alexander Smirnov
Fix For: 3.2.2, 3.1.x
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:46 a.m.
New subject: [JBoss JIRA] Updated: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Nick Belaevski updated RF-3631:
-------------------------------
Fix Version/s: 3.1.x
(was: 3.1.6)
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Alexander Smirnov
Fix For: 3.2.2, 3.1.x
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [JBoss JIRA] Commented: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=comments#action_12415948 ]
Nick Belaevski commented on RF-3631:
------------------------------------
Stanimir,
Thank you much for the sample!
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Alexander Smirnov
Fix For: 3.2.2, 3.1.x
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:57 p.m.
New subject: [JBoss JIRA] Updated: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Nick Belaevski updated RF-3631:
-------------------------------
Fix Version/s: 3.1.6
(was: 3.1.x)
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Alexander Smirnov
Fix For: 3.2.2, 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:11 p.m.
New subject: [JBoss JIRA] Assigned: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Nick Belaevski reassigned RF-3631:
----------------------------------
Assignee: Nick Belaevski (was: Alexander Smirnov)
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Nick Belaevski
Fix For: 3.2.2, 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:16 p.m.
New subject: [JBoss JIRA] Updated: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Nick Belaevski updated RF-3631:
-------------------------------
Fix Version/s: (was: 3.2.2)
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Nick Belaevski
Fix For: 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:30 p.m.
New subject: [JBoss JIRA] Resolved: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Nick Belaevski resolved RF-3631.
--------------------------------
Resolution: Done
Assignee: Tsikhon Kuprevich (was: Nick Belaevski)
Resolved for 3.1.x branch for now.
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Tsikhon Kuprevich
Fix For: 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:33 p.m.
New subject: [JBoss JIRA] Commented: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=comments#action_12416368 ]
Nick Belaevski commented on RF-3631:
------------------------------------
Context parameters handling added to RichFaces 3.1.x. state manager implementation:
org.ajax4jsf.SERIALIZE_SERVER_STATE
com.sun.faces.serializeServerState
org.apache.myfaces.SERIALIZE_STATE_IN_SESSION
Set any to true for alike (session serializing) environments.
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Tsikhon Kuprevich
Fix For: 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:44 p.m.
New subject: [JBoss JIRA] Updated: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Nick Belaevski updated RF-3631:
-------------------------------
Affects: [Documentation (Ref Guide, User Guide, etc.)]
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Tsikhon Kuprevich
Fix For: 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:22 a.m.
New subject: [JBoss JIRA] Updated: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Svetlana mukhina updated RF-3631:
---------------------------------
Component/s: docs updated
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Components: docs updated
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Tsikhon Kuprevich
Fix For: 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:47 a.m.
New subject: [JBoss JIRA] Assigned: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Aleksej Yanul reassigned RF-3631:
---------------------------------
Assignee: Aleksej Yanul (was: Tsikhon Kuprevich)
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Components: docs updated
Affects Versions: 3.1.5, 3.2.0
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Aleksej Yanul
Fix For: 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:15 a.m.
New subject: [JBoss JIRA] Closed: (RF-3631) ConcurrentModificationException during session serialization
[ http://jira.jboss.com/jira/browse/RF-3631?page=all ]
Aleksej Yanul closed RF-3631.
-----------------------------
ConcurrentModificationException during session serialization
------------------------------------------------------------
Key: RF-3631
URL: http://jira.jboss.com/jira/browse/RF-3631
Project: RichFaces
Issue Type: Bug
Components: docs updated
Affects Versions: 3.2.0, 3.1.5
Environment: JBboss 4.2.2.GA
Seam 2.0.2.SP1
JDK 1.5.0_15
Windows XP Pro SP2
Reporter: Stanimir Stamenkov
Assigned To: Aleksej Yanul
Fix For: 3.1.6
Attachments: test-cluster-session.ear
Concurrent requests cause java.util.ConcurrentModificationException during session
serialization in cluster environment.
I've initially posted this issue to the RichFaces users forum, but then posted to the
Clustering/JBoss, too:
http://www.jboss.com/index.html?module=bb&op=viewtopic&t=136590
where I've got feedback I'm on the right track my problem is probably caused by
the RichFaces (Ajax4Jsf) library. Basically the web session gets modified while it is
been serialized when concurrent requests are made. bstansberry(a)jboss.com have written:
"The session management layer does not prevent concurrent access to the session. The
session's internal data structures can deal with concurrency (e.g. the attribute map
is a ConcurrentHashMap) but if the objects you'll store in it are going to be accessed
concurrently, they'll need to be thread safe or have access to them
synchronized."
I've prepared minimal test case (I'm about to attach) demonstrating the problem.
I've tried it with both RichFaces 3.1.5.GA (part of Seam 2.0.2.SP1) and RichFaces
3.2.0.SR1 (which I'm using with my application).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6503
days inactive
6512
days old
richfaces-issues@lists.jboss.org
16 comments
4 participants
participants (4)
-
Aleksej Yanul (JIRA) -
Nick Belaevski (JIRA)
-
Stanimir Stamenkov (JIRA)
-
Svetlana mukhina (JIRA)