You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/04/11 10:49:52 UTC
[jira] Commented: (CAMEL-450) Running jms-file example is raising
Log4J/ActiveMQ error
[ https://issues.apache.org/activemq/browse/CAMEL-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42203#action_42203 ]
Claus Ibsen commented on CAMEL-450:
-----------------------------------
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.
> Running jms-file example is raising Log4J/ActiveMQ error
> --------------------------------------------------------
>
> Key: CAMEL-450
> URL: https://issues.apache.org/activemq/browse/CAMEL-450
> Project: Apache Camel
> Issue Type: Bug
> Components: examples
> Affects Versions: 1.3.0
> Reporter: Glen Mazza
> Priority: Minor
>
> 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/
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.