Bug 957838 - An exception "java.io.NotActiveException: Fields were never written" occurs when FacesMessage object is serialized in JBoss EAP 6.
Summary: An exception "java.io.NotActiveException: Fields were never written" occurs w...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: JSF
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ER7
: EAP 6.1.0
Assignee: ivassile
QA Contact: Marek Schmidt
URL:
Whiteboard:
Depends On:
Blocks: 960073
TreeView+ depends on / blocked
 
Reported: 2013-04-29 16:46 UTC by ivassile
Modified: 2018-12-01 15:22 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
The deserialization of `FacesMessage` objects would throw an exception (`java.io.NotActiveException`) in some circumstances. This occurred because the `ObjectOutputStream`'s `defaultWriteObject()` or `writeFields()` methods were not invoked during serialization as required by the JSF specification. These methods are now correctly called during serialization and the deserialization of `FacesMessage` objects now works as expected.
Clone Of:
: 960073 (view as bug list)
Environment:
Last Closed: 2013-07-18 13:52:06 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
one-off patch (2.34 MB, patch)
2013-05-02 21:48 UTC, ivassile 		no flags Details | Diff
View All

Description ivassile 2013-04-29 16:46:21 UTC 
Description of problem:
See https://java.net/jira/browse/JAVASERVERFACES-2853
Comment 1 ivassile 2013-04-29 16:50:31 UTC 
Email from Stan:

This only requires a change to the jar in javax.faces.api.  Here is the
released artifact for the new version, 2.1.19.1.
https://repository.jboss.org/nexus/index.html#nexus-search;gav~~~2.1.19.1.Final~~

The code is here:
https://github.com/jboss/jboss-jsf-api_spec/tree/2.1.19.1

This should be used in conjunction with the previously-released version
of the impl jar which is here:
https://repository.jboss.org/nexus/index.html#nexus-search;gav~~~2.1.19-jbossorg-1~~
Comment 2 Paul Gier 2013-05-02 21:06:53 UTC 
Brew build of jsf-api 2.1.19.1 with jars:
https://brewweb.devel.redhat.com/buildinfo?buildID=269945

Adding acks to check if this update is ok to include in 6.1.
Comment 3 ivassile 2013-05-02 21:48:11 UTC 
Created attachment 742929 [details]
one-off patch
Comment 4 ivassile 2013-05-02 21:54:38 UTC 
To QA: Please verify the patch
Comment 5 Paul Gier 2013-05-02 22:15:52 UTC 
PR for jboss-eap repo: https://github.com/jbossas/jboss-eap/pull/128
Comment 8 Scott Mumford 2013-05-06 02:37:16 UTC 
Draft Release Note content added.

Setting NEEDINFO to get a technical review of the draft content.

Comment to approve or correct it.
Comment 9 Marek Schmidt 2013-05-06 14:14:20 UTC 
I am confused, I believe this issue has been created as a one-off release for EAP 6.0.1, but now it looks like a EAP 6.1.0 issue. It can't be both, but we need both.

@Ilia, will you please clone the issue and make one of them a one-off issue, with the proper ON_QA state, so I can proceed with the QA-ACKing the one-off?

The EAP 6.0.1 one-off itself passes the tests. 

9cc100b0bb11e0c85ad39fdc2be72734  README.txt
aba3644142be3bdd78d9bee7b3c27ed3  jboss-jsf-api/jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar
f4f04455b984371c134c4c004985a599  jboss-jsf-api/module.xml
1bfea67291907b7c0cc57244a775147e  jsf-impl/jsf-impl-2.1.19-redhat-1.jar
6bce03a05537840ee6aab7d9c53e8ad2  jsf-impl/module.xml
Comment 11 ivassile 2013-05-06 14:44:50 UTC 
I originaly created this issue as one-off. 

@Marek: Created new one-off BZ: https://bugzilla.redhat.com/show_bug.cgi?id=960073
Comment 12 Paul Gier 2013-05-06 19:38:57 UTC 
Marek, sorry for the confusion, next time I'll create a separate bz right away when we decide to include a one off in the next eap release.
Comment 13 Scott Mumford 2013-05-10 03:20:33 UTC 
Updated Release Notes draft.
Comment 14 Tomas Remes 2013-05-14 15:12:45 UTC 
Verified at EAP 6.1.0.ER8 release.
Comment 15 Scott Mumford 2013-05-14 23:25:10 UTC 
Adding NEEDINFO to request verification of Release Note in Doc Text field above.
Comment 16 Tomas Remes 2013-05-15 06:14:31 UTC 
The object name is FacesMessage (not FacesMessages). It looks OK after this minor correction.
Note You need to log in before you can comment on or make changes to this bug.