[SM-854] LogService uses hard-coded path to the log4j.xml file

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1
• Fix Version/s: 3.1.2, 3.2
• Component/s: servicemix-core
• Assignee: Thomas Termin
• Reporter: Bruce Snyder
• Created: 21/Feb/07 22:11
• Updated: 26/Jul/07 14:05
• Resolved: 26/Jul/07 14:05

Description

The path the log4j.xml file is hard-coded to conf/log4j.xml. If ServiceMix is started from inside the bin directory, ServiceMix won't be able to locate this file and logging will not work properly. Below is the output from a started in the bin directory:

$ ./servicemix
servicemix: JAVA_HOME not set; results may vary
java version "1.5.0_07"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-164)
Java HotSpot(TM) Client VM (build 1.5.0_07-87, mixed mode, sharing)

Starting Apache ServiceMix ESB: 3.1-incubating-SNAPSHOT

Loading Apache ServiceMix from servicemix.xml on the CLASSPATH
INFO - ConnectorServerFactoryBean - JMX connector available at: service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
INFO - JBIContainer - ServiceMix 3.1-incubating-SNAPSHOT JBI Container (ServiceMix) is starting
INFO - JBIContainer - For help or more informations please see: http://incubator.apache.org/servicemix/
INFO - ComponentMBeanImpl - Initializing component: #SubscriptionManager#
INFO - DeploymentService - Restoring service assemblies
INFO - JBIContainer - ServiceMix JBI Container (ServiceMix) started
INFO - JDBCAdapterFactory - Database driver recognized: [apache_derby_embedded_jdbc_driver]
ERROR - LogTask - java.io.FileNotFoundException: conf/log4j.xml (No such file or directory)