This week's book giveaway is in the Mac OS forum.
We're giving away four copies of a choice of "Take Control of Upgrading to Yosemite" or "Take Control of Automating Your Mac" and have Joe Kissell on-line!
See this thread for details.
The moose likes JBoss/WildFly and the fly likes Logging problem log4j:ERROR Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "Logging problem log4j:ERROR" Watch "Logging problem log4j:ERROR" New topic
Author

Logging problem log4j:ERROR

Srikanth Adapa
Ranch Hand

Joined: Aug 21, 2008
Posts: 56
Hi,
I am testing an application to implement clustering. Everything is seeming good. But I found a session related exception. Please check with the following command console status:


Please let me know if I need to make any settings or changes in my jboss server, as I am getting the similar exception for every test case in echo2, I ve checked. And any problem with the class loader??


Thank you in advance.
Jaikiran Pai
Marshal

Joined: Jul 20, 2005
Posts: 10141
    
165

Are you packaging log4j jar file in your application? If yes, then remove that jar file from your application package. JBoss already ships with a log4j jar.


[My Blog] [JavaRanch Journal]
Srikanth Adapa
Ranch Hand

Joined: Aug 21, 2008
Posts: 56
Thats fine Mr. Kiran.
I could solve the log4j error. But I ve a big exception stack trace while clustering. Would you please suggest me something.

Srikanth Adapa
Ranch Hand

Joined: Aug 21, 2008
Posts: 56
When the application is running on a single machine everything is fine. But coming to clustering issue, I even got the similar type of exception pointing to a class in the application. As read from the forum, I came to know that this exception generally occur due to absence of related library files. But everything is fine here. please observer the exception stack trace as




Thanking you in advance!!
 
GeeCON Prague 2014
 
subject: Logging problem log4j:ERROR