-
Bug
-
Resolution: Done
-
Major
-
7.0.4.GA
-
None
-
Release Notes
-
Regression
-
-
-
-
-
-
-
+
-
RiverMarshaller implements its own custom serialization for java.util.Vector that is not thread safe.
Vector's own writeObject is thread safe.
This causes ConcurrentModificationExceptions when serializing a Vector that is modified by another thread, which will not occur with JDK serialization that calls Vector's own writeObject.
The same applies to java.util.Stack which extends Vector.
- clones
-
JBEAP-15295 JBoss Marshalling - Vector marshalling not serialized
- Closed
- incorporates
-
JBMAR-222 Vector serialization not synchronized
- Resolved
- is incorporated by
-
JBEAP-16470 [GSS](7.2.z) Upgrade JBoss Marshalling from 2.0.6 to 2.0.7
- Closed