-
Bug
-
Resolution: Done
-
Major
-
7.1.0.ER2
-
None
After update to CP06, it seeing java.io.NotSerializableException: org.apache.commons.logging.JBossLog
Caused by: java.io.NotSerializableException: org.apache.commons.logging.JBossLog at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:253) at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:128) at org.jboss.marshalling.cloner.SerializingCloner.cloneFields(SerializingCloner.java:393) at org.jboss.marshalling.cloner.SerializingCloner.initSerializableClone(SerializingCloner.java:309) at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:251) at org.jboss.marshalling.cloner.SerializingCloner.clone(SerializingCloner.java:128) at org.jboss.as.ejb3.remote.LocalEjbReceiver.clone(LocalEjbReceiver.java:330) ... 67 more
Looks that org.apache.commons.logging.JBossLog should be serializable.
- clones
-
JBEAP-12248 [GSS](7.0.z) java.io.NotSerializableException: org.apache.commons.logging.JBossLog after update to EAP 7 CP06
-
- Closed
-
- is incorporated by
-
WFCORE-3082 Upgrade commons-logging-jboss-logmanager from 1.0.0.Final to 1.0.1.Final
-
- Resolved
-
-
JBEAP-11931 (7.1.0) Upgrade to WildFly Core to 3.0.0.Beta30
-
- Closed
-