we have the same problem!
We found this helpful: http://www.openrdf.org/forum/mvnforum/viewthread?thread=1296
but does not actually resolve the problem.
The suggestion is to remove our copy of log4j1.2.8 library from our application, but this is not right as the application has been tested against this library.
It sound like jboss classloading nightmare is back again.
In jboss 4.0.3sp1 all of our application was working fine.
With 4.0.5 version, we had to deal with classloading isolation to to be able to use log4j.
And now, we have to remove log4j in to make ous application dependent to jboss log4j version.
I wonder if jboss guys are measuring the negative impact thoses changes bring to those who want to migrate.
It's becomming more and more painful to migrate from a version to another.
There is nowhere in the doc to find thoses changes.
So I'd like to say to jboss guys to please be as professionnal as they claim
while making new versions.
Did u able to solve it?