You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Dejan Bosanac (JIRA)" <ji...@apache.org> on 2010/09/15 10:43:41 UTC

[jira] Commented: (AMQ-2917) activemq script determines ACTIVEMQ_BASE too late, and thus always points to the data and conf directory off ACTIVEMQ_HOME :(

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

Dejan Bosanac commented on AMQ-2917:
------------------------------------

Hi Adrian,

I think this is a duplicate of https://issues.apache.org/activemq/browse/AMQ-2881, which is already solved on the trunk. Can you test it out to see if it helps in your case?

> activemq script determines ACTIVEMQ_BASE too late, and thus always points to the data and conf directory off ACTIVEMQ_HOME :(
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-2917
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2917
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.4.0
>            Reporter: Adrian Trenaman
>         Attachments: fix-activemq-script.patch
>
>
> As per the title, the activemq script is determining the conf/ and data/ directories off ACTIVEMQ_HOME, instead of off ACTIVEMQ_BASE. This has a nasty side effect in that you can't run two different broker instances on the same machine, as the script tries to store the PID for each in the sample place. Ouch! 
> Have attached a fix. 

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