[ 
https://issues.apache.org/activemq/browse/AMQ-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42043#action_42043
 ] 

Glen Mazza commented on AMQ-1132:
---------------------------------

This is an annoying, ugly bug.  Even the Camel samples[1] are returning this 
error trace before continuing:

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: /target/test.log (No such file or directory)
        at java.io.FileOutputStream.openAppend(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
        at org.apache.log4j.FileAppender.setFile(FileAppender.java:289)
        at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:163)
        at 
org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:256)
        at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:132)
        at 
org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:96)
        at 
org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:654)
        at 
org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:612)
        at 
org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:509)
        at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:415)
        at 
org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:441)
        at 
org.apache.log4j.helpers.OptionConverter.selectAndConfigure(OptionConverter.java:468)
        at org.apache.log4j.LogManager.<clinit>(LogManager.java:122)
        at org.apache.log4j.Logger.getLogger(Logger.java:104)
        at 
org.apache.commons.logging.impl.Log4JLogger.getLogger(Log4JLogger.java:229)
        at 
org.apache.commons.logging.impl.Log4JLogger.<init>(Log4JLogger.java:65)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at 
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at 
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
        at 
org.apache.commons.logging.impl.LogFactoryImpl.newInstance(LogFactoryImpl.java:529)
        at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:235)
        at 
org.apache.commons.logging.impl.LogFactoryImpl.getInstance(LogFactoryImpl.java:209)
        at org.apache.commons.logging.LogFactory.getLog(LogFactory.java:351)
        at 
org.apache.camel.impl.DefaultCamelContext.<clinit>(DefaultCamelContext.java:64)
        at 
org.apache.camel.example.jmstofile.CamelJmsToFileExample.main(CamelJmsToFileExample.java:44)

If it would mean turning off this error, perhaps best to go to stdout by 
default as the OP says or just trapping this message with a more user-friendly 
exception.

[1] 
http://svn.apache.org/viewvc/activemq/camel/trunk/examples/camel-example-jms-file/
 (run "mvn clean install" followed by mvn exec:java.)

> activeio test package inclusion and logging properties
> ------------------------------------------------------
>
>                 Key: AMQ-1132
>                 URL: https://issues.apache.org/activemq/browse/AMQ-1132
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: incubation
>            Reporter: Dejan Bosanac
>            Priority: Minor
>             Fix For: 5.2.0
>
>
> When you include activemq-core as a dependency on an empty project, even 
> simplest examples fails with
> java.io.FileNotFoundException: /target/test.log (No such file or directory)
> exception.
> First of all, the core package includes dependency on activeio-core test jar 
>     <dependency>
>       <groupId>${pom.groupId}</groupId>
>       <artifactId>activeio-core</artifactId>
>       <optional>false</optional>
>       <type>test-jar</type>
>     </dependency>
> for which I'm not sure is needed.
> Second, in this test activeio package logging.properties is configured so 
> that root logger writes into ${basedir}/target/test.log, which causes 
> application to fail. It would be better to set it to write to stdout by 
> default.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to