wood burning stoves 2.0
The moose likes JBoss/WildFly and the fly likes packaging log4j.properties file Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Products » JBoss/WildFly
Bookmark "packaging log4j.properties file" Watch "packaging log4j.properties file" New topic

packaging log4j.properties file

Pras Po

Joined: Oct 27, 2008
Posts: 3
I have an application which wraps around log4j logger to be used by several clients. The logger is configured to send messages to a JMS topic using JMSAppender.

There are 2 portions to the application, 1 a client library which is to be used by all clients and the server portion which processes messages from JMS.

I am unable to get the clients to send messages to JMS.
The structure of my jar files are :

| |_test
| ||_logger.class (Class with all Static methods)
| |
| |_Server.class (MDB which processes JMS Messages)
| |_lib
| |
| |_log4j.jar

| |_test
|_logger.class (Class with all Static methods)

when another ejb uses the logging-client.jar and calls the logger, its unable to send messages to the JMS.

What am I doing wrong?
Peter Johnson

Joined: May 14, 2008
Posts: 5852

Pras, welcome to JavaRanch!

JBossAS comes with Log4J embedded, and thus all log4j configuration is done via the server/xxx/conf/jboss-log4j.xml file. Essentially, your log4j configuration file is ignored.

You can work around this in one of two ways. First, you could add your logging configuration to jboss-log4j.xml. Second, you could follow these instructions from Jaikiran.

JBoss In Action
I agree. Here's the link: http://aspose.com/file-tools
subject: packaging log4j.properties file
jQuery in Action, 3rd edition