An exception "java.io.NotActiveException: Fields were never written" occurs when FacesMessage object is serialized in JBoss EAP 6 (one-off for JAVASERVERFACES-2853).
PATCH NAME:
BZ-960073
PRODUCT NAME:
JBoss Enterprise Application Platform (EAP)
VERSION:
6.0.1
SHORT DESCRIPTION:
An exception "java.io.NotActiveException: Fields were never written" occurs when FacesMessage object is serialized in JBoss EAP 6.
LONG DESCRIPTION:
See JAVASERVERFACES-2853 (https://java.net/jira/browse/JAVASERVERFACES-2853)
MANUAL INSTALL INSTRUCTIONS:
1. Unzip BZ-960073-patch.zip
2. Copy jboss-jsf-api_2.1_spec-2.1.19.1.Final-redhat-1.jar (located in jboss-jsf-api folder) to $JBOSS_HOME/modules/javax/faces/api/main
3. Copy module.xml (located in jboss-jsf-api folder) to $JBOSS_HOME/modules/javax/faces/api/main so that the new JAR is utilized.
4. Copy jsf-impl-2.1.19-redhat-1.jar (located in jsf-impl folder) to $JBOSS_HOME/modules/com/sun/jsf-impl/main
5. Copy module.xml (located in jsf-impl folder) to $JBOSS_HOME/modules/com/sun/jsf-impl/main so that the new JAR is utilized.
COMPATIBILITY:
N/A
DEPENDENCIES:
N/A
SUPERSEDES:
N/A
SUPERSEDED BY:
N/A
CREATOR:
Ilia Vassilev
DATE:
May 5, 2013
+++ This bug was initially created as a clone of Bug #957838 +++
Description of problem:
See https://java.net/jira/browse/JAVASERVERFACES-2853
--- Additional comment from on 2013-04-29 12:50:31 EDT ---
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~~
--- Additional comment from Paul Gier on 2013-05-02 17:06:53 EDT ---
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.
--- Additional comment from on 2013-05-02 17:48:11 EDT ---
Created attachment 742929[details]
one-off patch
--- Additional comment from on 2013-05-02 17:54:38 EDT ---
To QA: Please verify the patch
--- Additional comment from Paul Gier on 2013-05-02 18:15:52 EDT ---
PR for jboss-eap repo: https://github.com/jbossas/jboss-eap/pull/128
--- Additional comment from on 2013-05-05 22:37:16 EDT ---
Draft Release Note content added.
Setting NEEDINFO to get a technical review of the draft content.
Comment to approve or correct it.
--- Additional comment from Marek Schmidt on 2013-05-06 10:14:20 EDT ---
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