Back to bug 1032312
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Brad Maxwell | 2013-11-20 00:22:59 UTC | Link ID | JBoss Issue Tracker JBMAR-156 | |
| Brad Maxwell | 2013-11-20 00:24:04 UTC | Blocks | 1032313 | |
| Brad Maxwell | 2013-11-20 00:24:47 UTC | Blocks | 1032313 | |
| Brad Maxwell | 2013-11-21 23:00:48 UTC | Blocks | 1032313 | |
| Brad Maxwell | 2013-11-21 23:01:46 UTC | Status | NEW | MODIFIED |
| Blocks | 1032313 | |||
| Paul Gier | 2013-12-04 15:07:48 UTC | Blocks | 1032313 | |
| Brad Maxwell | 2014-01-09 05:17:01 UTC | Depends On | 1050791 | |
| Brad Maxwell | 2014-01-09 05:30:07 UTC | Blocks | 1050791 | |
| Depends On | 1050791 | |||
| mark yarborough | 2014-01-13 13:33:04 UTC | Target Release | --- | EAP 6.2.1 |
| CC | myarboro | |||
| Summary | Protocol incompatibility between serializable classes with different non-serializable superclasses | [GSS] (6.2.x) Protocol incompatibility between serializable classes with different non-serializable superclasses | ||
| Brad Maxwell | 2014-01-13 13:34:18 UTC | Blocks | 1027004 | |
| Summary | [GSS] (6.2.x) Protocol incompatibility between serializable classes with different non-serializable superclasses | Protocol incompatibility between serializable classes with different non-serializable superclasses | ||
| Brad Maxwell | 2014-01-13 13:35:44 UTC | Summary | Protocol incompatibility between serializable classes with different non-serializable superclasses | [GSS] (6.2.x) Protocol incompatibility between serializable classes with different non-serializable superclasses |
| Brad Maxwell | 2014-01-13 13:42:06 UTC | Blocks | 1050791 | |
| mark yarborough | 2014-01-13 14:00:00 UTC | Depends On | 1052204 | |
| Carlo de Wolf | 2014-01-16 15:13:56 UTC | Target Milestone | --- | CR1 |
| Scott Mumford | 2014-01-20 05:56:01 UTC | CC | smumford | |
| Vaclav Tunka | 2014-01-20 22:18:00 UTC | Status | MODIFIED | ON_QA |
| Scott Mumford | 2014-01-23 02:33:33 UTC | CC | bmaxwell | |
| Flags | needinfo?(bmaxwell) | |||
| David M. Lloyd | 2014-01-23 13:37:32 UTC | Doc Text | Cause: The marshalling layer is introducing extra, unnecessary data pertaining to non-serializable classes into the serialization stream. Consequence: In the best case, performance is slightly reduced. In the worst case, the user will get ClassNotFoundExceptions and other errors between different JVMs. Fix: The extra data is truncated as it should be. Result: The protocol is more performant, and is again compatible between JVMs that have different class hierarchies for the same class. | |
| Flags | needinfo?(bmaxwell) | |||
| Scott Mumford | 2014-01-24 00:10:36 UTC | Doc Text | Cause: The marshalling layer is introducing extra, unnecessary data pertaining to non-serializable classes into the serialization stream. Consequence: In the best case, performance is slightly reduced. In the worst case, the user will get ClassNotFoundExceptions and other errors between different JVMs. Fix: The extra data is truncated as it should be. Result: The protocol is more performant, and is again compatible between JVMs that have different class hierarchies for the same class. | It was found that in previous versions of JBoss EAP 6, the marshalling layer was introducing superfluous data pertaining to non-serializable classes into the serialization stream. This was causing a range of undesirable behaviors ranging from reduced performance to ClassNotFoundExceptions and other errors between different JVMs. This release of the product sees the extra data truncated as it should be. The protocol is now more performant and is again compatible between JVMs that have different class hierarchies for the same class. |
| Ladislav Thon | 2014-01-27 14:39:20 UTC | Status | ON_QA | VERIFIED |
| CC | lthon | |||
| mark yarborough | 2014-02-24 20:14:53 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-02-24 15:14:53 UTC |
Back to bug 1032312