-
Bug
-
Resolution: Done
-
Major
-
1.4.10.Final
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.
- is incorporated by
-
JBEAP-15295 JBoss Marshalling - Vector marshalling not serialized
- Closed
-
JBEAP-16469 [GSS](7.2.z) JBMAR-222 - JBoss Marshalling - Vector marshalling not serialized
- Closed
-
WFCORE-4432 Upgrade JBoss Marshalling from 2.0.6.Final to 2.0.7.Final
- Resolved