I have seen the "OnlyOnceErrorHandler" error happen when I have deployed an application that contains its own log4j.jar and commons-logging.jar files. Removing those files from my application solved the problem.
Thank you VERY much for your reply...
Yes, I think this could be the issue I am facing....but I am perplexed on a clean solution. If I rip out the log4j.jar file from my projects and remove the all references from the projects, I am not able to compile the source code. If delete the jar files already in the deployed project on JBoss, the server still sees it and throws an error.
What I think I need is a clean solution so I can build on my box and deploy the J2EE project over to JBOSS (also on my box) without and yanking of jars.
How do you do it?
Thanks as always for reading my post!
Note that the only steps I took were to remove the two jar files from my war/ear file. My code still uses commons logging with log4j, so I still compile with the commons logging jar in my classpath, I just don't deploy with it. At runtime, my code uses the commons logging and log4j jars provided by JBoss.