i forgot where i read it, but there is a provision somewhere in one of the jboss admin docs that tells you what to change in one of your xml config files pkg'd with your war so that if you decide to use your own log4j config file you can deploy your own log4j jar file as well so that jboss doesn't try use logging configured for jboss on to the war deployment itself.
you also have to update the jboss-service.xml config of the jboss server to tell it to use it's own logging config file which is usually the log4j xml already used, and changing its name to jboss-log4j.xml and updating the reference of it in the jboss-service.xml file.
I have read the wiki document that you are talking about.
But still getting the same deployment error of log4j.jar
when I take it out, complete logging is going in my application log file
(including jboss & my app war)
Please help me out
Any Help on this??
Not a portal issue. Perhaps post in one of the JBoss AS forums?