Any further word on this?
I created a listener that implements both HttpSessionAttributeListener and
ServletContextAttributeListener (code below). It exposed a few other classes
we were putting into the session.
However, I continue to get the log4j NonSerializable exceptions without any
i
I'm afraid the problem still exists. However, it was hidden for a while behind
another serialization problem regarding java.lang.reflect.Method. Seems we/some
of the frameworks we use are putting this into the Session. After searching for
quite a long time I kind of gave up and just removed the
Did you find if this was the solution? I am getting the same problem but with
Logger rather than Level. I have made a log4j-boot based on log4j 1.2.13 but I
still get a doezen replication errors on every page load.
Thanks.
View the original post :
http://www.jboss.com/index.html?module=bb&op
I couldn't find a place where we would directly insert the Level class into the
Session. Though this probably doesn't mean we don't do it indirectly somewhere.
However, I replaced log4j-boot.jar in JBoss with my own version, and so far the
problem has not shown again in the logs. Time will show
You probably have an object in your application trying to store
org.apache.log4j.Level instance in the session and that's why you're seeing the
stack trace below.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3987949#3987949
Reply to the post :
http://www.j
