Running jms-file example is raising Log4J/ActiveMQ error

• Key: CAMEL-450
• Type: Bug
• Status: Closed
• Resolution: Cannot Reproduce
• Priority: Minor
• Assignee: Unassigned
• Reporter: Glen Mazza
• Component/s: examples
• Affects Version/s: 1.3.0
• Fix Version/s: 1.3.0

Description

Running the JMS-file example[1] using Maven from a command window is raising an error stack (http://issues.apache.org/activemq/browse/AMQ-1132). ActiveMQ has an apparent bug in that it is trying to log to a hardcoded directory that doesn't exist on most machines.

[1] http://svn.apache.org/viewvc/activemq/camel/trunk/examples/camel-example-jms-file/

Comments

[Claus Ibsen]

Isn't this bug a ActiveMQ bug, and thus should be fixed in ActiveMQ?

I am not keen on creating a workaround in Camel for a bug in ActiveMQ where the workaround would be ugly.

[Claus Ibsen]

Glen I can not reproduce it at my local machine.

When I run mvn compile exec:java I do not get any ERROR level logging. This is using the log4j.properties from the trunk.

[Glen Mazza]

I stand corrected – I wasn't able to duplicate it off trunk either. Never mind – this issue is invalid. Sorry about that.