This looks like a bug that was already fixed in Seam, but I did not think that the bug was
in Seam 1.2.1. Are you sure you are really using 1.2.1.
Anyway, it can be solved by upgrading to a more recent log4j.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4067571#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...