You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Phil Pickett (JIRA)" <ji...@apache.org> on 2010/08/27 22:05:40 UTC
[jira] Created: (AMQ-2881) ACTIVEMQ_HOME and ACTIVEMQ_BASE appear
not to be set correctly in scripts
ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly in scripts
-------------------------------------------------------------------------
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
Priority: Minor
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.
I am able to create
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AMQ-2881) 404 status for Broker Instance's admin
console - ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac resolved AMQ-2881.
--------------------------------
Fix Version/s: 5.4.1
Resolution: Fixed
A bit modified patch committed with svn revision 991184. Thanks!
> 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
> Assignee: Dejan Bosanac
> Fix For: 5.4.1
>
> 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.
[jira] Updated: (AMQ-2881) 404 status for Broker Instance's admin
console - ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly
Posted by "Phil Pickett (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (AMQ-2881) ACTIVEMQ_HOME and ACTIVEMQ_BASE appear
not to be set correctly in scripts
Posted by "Phil Pickett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Pickett updated AMQ-2881:
------------------------------
Priority: Major (was: Minor)
> ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly in scripts
> -------------------------------------------------------------------------
>
> 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, 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.
> I am able to create
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2881) ACTIVEMQ_HOME and ACTIVEMQ_BASE appear
not to be set correctly in scripts
Posted by "Phil Pickett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Pickett updated AMQ-2881:
------------------------------
Attachment: activemq
jetty.xml
> ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly in scripts
> -------------------------------------------------------------------------
>
> 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
> Priority: Minor
> Attachments: activemq, activemq.diffs, 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.
> I am able to create
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2881) 404 status for Broker Instance's admin
console - ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly
Posted by "Phil Pickett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Pickett updated AMQ-2881:
------------------------------
Summary: 404 status for Broker Instance's admin console - ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly (was: ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly in scripts)
> 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, 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.
> I am able to create
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AMQ-2881) 404 status for Broker Instance's admin
console - ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly
Posted by "Phil Pickett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Pickett updated AMQ-2881:
------------------------------
Description:
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.
was:
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.
I am able to create
> 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, 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.
[jira] Assigned: (AMQ-2881) 404 status for Broker Instance's admin
console - ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly
Posted by "Dejan Bosanac (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dejan Bosanac reassigned AMQ-2881:
----------------------------------
Assignee: Dejan Bosanac
> 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
> Assignee: Dejan Bosanac
> 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.
[jira] Updated: (AMQ-2881) ACTIVEMQ_HOME and ACTIVEMQ_BASE appear
not to be set correctly in scripts
Posted by "Phil Pickett (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-2881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Phil Pickett updated AMQ-2881:
------------------------------
Attachment: activemq.diffs
jetty.xml.diffs
> ACTIVEMQ_HOME and ACTIVEMQ_BASE appear not to be set correctly in scripts
> -------------------------------------------------------------------------
>
> 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
> Priority: Minor
> Attachments: activemq, activemq.diffs, 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.
> I am able to create
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.