[prev in list] [next in list] [prev in thread] [next in thread] 

List:       activemq-dev
Subject:    [jira] Updated: (AMQ-2881) 404 status for Broker Instance's admin
From:       "Phil Pickett (JIRA)" <jira () apache ! org>
Date:       2010-08-30 18:05:40
Message-ID: 23627861.3981283191540438.JavaMail.jira () thor
[Download RAW message or body]


     [ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Phil Pickett updated AMQ-2881:
------------------------------

    Attachment: AMQ-2881.patch

Attaching patch for bin/activemq, bin/activemq.bat, and conf/jetty.xml

> 404 status for Broker Instance's admin console - ACTIVEMQ_HOME and ACTIVEMQ_BASE \
>                 appear not to be set correctly
> ---------------------------------------------------------------------------------------------------------------
>  
> Key: AMQ-2881
> URL: https://issues.apache.org/activemq/browse/AMQ-2881
> Project: ActiveMQ
> Issue Type: Bug
> Affects Versions: 5.4.0
> Reporter: Phil Pickett
> Attachments: activemq, activemq.diffs, AMQ-2881.patch, jetty.xml, jetty.xml.diffs
> 
> 
> In a new AMQ 5.4 installation, I am using a command like "bin/activemq create \
> Broker2" to create a new instance.  There are problems bringing up the admin and \
> other consoles for the new instance due to what seem to be problems in the scripts \
> related to $ACTIVEMQ_HOME and $ACTIVEMQ_BASE. I've been able to get this working by \
> changing references to ${activemq.base} to ${activemq.home} for the webapps in the \
> conf/jetty.xml.  It seems to me that the webapps are probably not instance-specific \
> so I believe this makes sense.  I left the directory set to ${activemq.base} for \
> the jetty-realm.properties file thinking these properties are probably \
> instance-specific. I also modified the bin/activemq script to set the \
> ACTIVEMQ_CLASSPATH to \
> "${ACTIVEMQ_BASE}/conf:${ACTIVEMQ_HOME}/conf;${ACTIVEMQ_CLASSPATH}" so that \
> instance-specific config files are picked up before the more generic config files. \
> With these changes in place I am able to create multiple broker instances, set \
> unique openwire and jetty ports in the instance's conf/activemq.xml and \
> conf/jetty.xml, start the instances, and open their administrative consoles. My \
> modified bin/activemq and conf/jetty.xml files are attached along with the \
> differences to the 5.4 version.

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


[prev in list] [next in list] [prev in thread] [next in thread]