You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Tzvetanov Grigorov (Jira)" <ji...@apache.org> on 2019/10/09 13:08:01 UTC
[jira] [Resolved] (WICKET-6704) JavaSerializer.serialize causes the
JVM crash !
[ https://issues.apache.org/jira/browse/WICKET-6704?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Tzvetanov Grigorov resolved WICKET-6704.
-----------------------------------------------
Fix Version/s: 7.16.0
9.0.0-M4
8.7.0
Resolution: Fixed
> JavaSerializer.serialize causes the JVM crash !
> -----------------------------------------------
>
> Key: WICKET-6704
> URL: https://issues.apache.org/jira/browse/WICKET-6704
> Project: Wicket
> Issue Type: Bug
> Components: wicket-core
> Affects Versions: 8.5.0
> Environment: Windows 7, but probably it's NOT OS dependant
> Reporter: Joe K
> Assignee: Martin Tzvetanov Grigorov
> Priority: Major
> Fix For: 8.7.0, 9.0.0-M4, 7.16.0
>
> Attachments: WicketObjects_stacktrace_1.jpg, jvm-crash_from_wicket.zip
>
>
> * when trying to serialize my custom object with a non-serializable field by JavaSerializer.serialize the JVM crashes instead of throwing the regular NotSerializableException !
> * when trying to serialize THE SAME object by java ObjectOutputStream then it's handled correctly and NotSerializableException is thrown
> * I'm attaching the very simple source code (Maven project), 1st test simulates the wicket issue (JVM crash) and 2nd test simulates the correct handling by java ObjectOutputStream
> * the attached example is just the simplification of very large project which is massively used by the users, so in fact it's critical for us
>
> * java: 1.8 (probably doesn't matter, tested on 1.8.0_162 and 1.8.0_221)
> * wicket: 8.5.0 (probably the problem is also in other versions)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)