I am doing some root cause analysis here to determine the problem.
I removed all references to Seam @Logger and Seam Log in both SFSB's involved
in this use case.
I was still able to reproduce the log4j related exception after passivation
occurs and then running another test case:
Caused by: org.jboss.serial.exception.SerializationException: Could not create
instance of org.apache.log4j.Logger - org.apache.log4j.Logger
| at
org.jboss.serial.classmetamodel.ClassMetaData.newInstance(ClassMetaData.java:342)
| at
org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:239)
| at
org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
| at
org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
| at
org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643)
| at
org.jboss.serial.persister.RegularObjectPersister.readSlotWithFields(RegularObjectPersister.java:353)
| at
org.jboss.serial.persister.RegularObjectPersister.defaultRead(RegularObjectPersister.java:273)
| at
org.jboss.serial.persister.RegularObjectPersister.readData(RegularObjectPersister.java:241)
| at
org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.readObjectDescriptionFromStreaming(ObjectDescriptorFactory.java:412)
| at
org.jboss.serial.objectmetamodel.ObjectDescriptorFactory.objectFromDescription(ObjectDescriptorFactory.java:82)
| at
org.jboss.serial.objectmetamodel.DataContainer$DataContainerDirectInput.readObject(DataContainer.java:643)
| at
org.jboss.serial.persister.ObjectInputStreamProxy.readObjectOverride(ObjectInputStreamProxy.java:68)
| at java.io.ObjectInputStream.readObject(Unknown Source)
| at java.util.ArrayList.readObject(Unknown Source)
| ... 125 more
| Caused by: java.lang.InstantiationException: org.apache.log4j.Logger
| at java.lang.Class.newInstance0(Unknown Source)
| at java.lang.Class.newInstance(Unknown Source)
| at
org.jboss.serial.classmetamodel.ClassMetaData.newInstance(ClassMetaData.java:334)
| ... 138 more
I did a search for keyword "log4j" in my project and found a log4j.xml file in
the {projectName}/bootstrap folder. Not sure exactly what the bootstrap is
used for but I think it was new for Seam 2.0. Probably for bootstrapping JPA
for JavaSE project? Anyways, that log4j.xml and bootstrap folder are not in my
EAR in JBoss default/deploy folder.
Root cause is unknown at this time...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4106552#4106552
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4106552
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
