Bugs item #1051007, was opened at 2004-10-20 13:04 Message generated for change (Comment added) made by starksm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1051007&group_id=22866
Category: Clustering Group: v4.0 >Status: Closed >Resolution: Fixed Priority: 5 Submitted By: Scott M Stark (starksm) >Assigned to: Scott M Stark (starksm) Summary: jgroups logging is broken Initial Comment: The jgroups use of the commons logging package is resulting in useless log categories: [EMAIL PROTECTED] I'm getting tired of N different wrappers for the same feature. We currently have the jboss logger, log4j, commons logging, and avalon logkit. This needs to be cleaned up. ---------------------------------------------------------------------- >Comment By: Scott M Stark (starksm) Date: 2004-10-24 09:05 Message: Logged In: YES user_id=175228 There was an invalid commons.logging config file in the ebxmlrr-service.sar. Removing this fixes the problem but we need to be configuring the commons logging layer in the Log4jService to ensure the logging frameworks used by jboss are in a known state. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=376685&aid=1051007&group_id=22866 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
