![]() Please wait while updating issue type...
Could not save your changes
This issue has been changed since you started editing it
Data that has been changed is highlighted in red below. Undo your changes to see the updated information
You have changed this issue, but haven't saved your changes yet. To save it, press the Save changes button to the right
This issue is blocking the next release
![]() There are no comments
There is nothing attached to this issue
This issue has no duplicates
89b6791
Nov 11, 09:17 - Preceeded by ca887fcbda1d1c55872a651ca668f00d6729efe3
Log entry
fixed issue JPPF-557 Changed files
Affected issues
1015e1d
Nov 11, 09:16 - Preceeded by ec513edf36cba58efc56feb99d5b5ae8eae5b365
Log entry
fixed issue JPPF-557 Changed files
Affected issues
|
|||||||||||||||||||||||||||||||||||
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?
Flushing the ObjectOutputStream created by XStream, after writing the object in XstreamSerialization.serialize(), appears to fix the problem.
I will add non-regression tests for XStream (the same as for standard Java, JPPF and Kryo serializations) to ensure this kind of problem is detected ASAP.
Really delete this comment?
Really delete this comment?
Really delete this comment?
Really delete this comment?