hmmm....that's not doing it either. I removed my log4j entry, put it in a file called log4j-services.xml in the deploy directory. I get the exact same error on startup. I confirmed that jboss-service.xml has no log4j entry. I updated the log4j.xml file (jboss reloaded it) and now the logging works.
So, having the log4j-service.xml file in the deploy directory doesn't change the log4j functionality. I'm getting the message in my topic like expected. It has to be another dependency. Unfortunately, I'm unfamiliar with the dependencies. The two I have (one for the topic and one for the invocation layer) aren't fixing the problem. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886494#3886494 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886494 ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
