You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "John Heitmann (JIRA)" <ji...@apache.org> on 2006/12/12 22:04:02 UTC
[jira] Created: (AMQ-1096) activemq-console only has limited
classpath/extensions directory functionality
activemq-console only has limited classpath/extensions directory functionality
------------------------------------------------------------------------------
Key: AMQ-1096
URL: https://issues.apache.org/activemq/browse/AMQ-1096
Project: ActiveMQ
Issue Type: Bug
Components: Broker
Affects Versions: 4.1.0
Reporter: John Heitmann
Priority: Minor
Attachments: logpatch.diff
Reproduction:
1) Untar the binary distribution.
2) Run bin/activemq and note what logging looks like (you should see output to the console)
3) Stop the broker.
4) mv conf/log4j.properties foo/log4j.properties
5) export CLASSPATH=/path/to/foo/
6) export ACTIVEMQ_CLASSPATH=/path/to/foo/
7) Run './activemq --extdir /path/to/foo
Now note there is no log output even though there are 3 different attempts to set the proper directory. This is a regression from 4.0 to 4.1.
There are 2 root problems in Main.java. First, 'classpaths' doesn't actually pull from the classpath. The only thing that ever gets added to classpaths is the hard coded 'conf' directory. Second, directories specified with --extdir have jars and zips added, but not the directories themselves.
The attached patch totally removes the vestigial classpaths, and fixes extdir to pull in directories. This means that step 7 now works, but steps 5 and 6 are still useless. I like having only one way to specify classpath, but I could see others wanting the CLASSPATH and ACTIVEMQ_CLASSPATH settings to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Resolved: (AMQ-1096) activemq-console only has limited
classpath/extensions directory functionality
Posted by "Adrian Co (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Co resolved AMQ-1096.
----------------------------
Resolution: Fixed
Fix added to r495172
Added a activemq.classpath system property to extend the classpath of activemq
By default it contains activemq.home/conf.
It can be extended by specifying additional paths via the ACTIVEMQ_CLASSPATH environment variable separated by semi-colons.
> activemq-console only has limited classpath/extensions directory functionality
> ------------------------------------------------------------------------------
>
> Key: AMQ-1096
> URL: https://issues.apache.org/activemq/browse/AMQ-1096
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.1.0
> Reporter: John Heitmann
> Assigned To: Adrian Co
> Priority: Minor
> Attachments: logpatch.diff
>
>
> Reproduction:
> 1) Untar the binary distribution.
> 2) Run bin/activemq and note what logging looks like (you should see output to the console)
> 3) Stop the broker.
> 4) mv conf/log4j.properties foo/log4j.properties
> 5) export CLASSPATH=/path/to/foo/
> 6) export ACTIVEMQ_CLASSPATH=/path/to/foo/
> 7) Run './activemq --extdir /path/to/foo
> Now note there is no log output even though there are 3 different attempts to set the proper directory. This is a regression from 4.0 to 4.1.
> There are 2 root problems in Main.java. First, 'classpaths' doesn't actually pull from the classpath. The only thing that ever gets added to classpaths is the hard coded 'conf' directory. Second, directories specified with --extdir have jars and zips added, but not the directories themselves.
> The attached patch totally removes the vestigial classpaths, and fixes extdir to pull in directories. This means that step 7 now works, but steps 5 and 6 are still useless. I like having only one way to specify classpath, but I could see others wanting the CLASSPATH and ACTIVEMQ_CLASSPATH settings to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Assigned: (AMQ-1096) activemq-console only has limited
classpath/extensions directory functionality
Posted by "Adrian Co (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQ-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adrian Co reassigned AMQ-1096:
------------------------------
Assignee: Adrian Co
> activemq-console only has limited classpath/extensions directory functionality
> ------------------------------------------------------------------------------
>
> Key: AMQ-1096
> URL: https://issues.apache.org/activemq/browse/AMQ-1096
> Project: ActiveMQ
> Issue Type: Bug
> Components: Broker
> Affects Versions: 4.1.0
> Reporter: John Heitmann
> Assigned To: Adrian Co
> Priority: Minor
> Attachments: logpatch.diff
>
>
> Reproduction:
> 1) Untar the binary distribution.
> 2) Run bin/activemq and note what logging looks like (you should see output to the console)
> 3) Stop the broker.
> 4) mv conf/log4j.properties foo/log4j.properties
> 5) export CLASSPATH=/path/to/foo/
> 6) export ACTIVEMQ_CLASSPATH=/path/to/foo/
> 7) Run './activemq --extdir /path/to/foo
> Now note there is no log output even though there are 3 different attempts to set the proper directory. This is a regression from 4.0 to 4.1.
> There are 2 root problems in Main.java. First, 'classpaths' doesn't actually pull from the classpath. The only thing that ever gets added to classpaths is the hard coded 'conf' directory. Second, directories specified with --extdir have jars and zips added, but not the directories themselves.
> The attached patch totally removes the vestigial classpaths, and fixes extdir to pull in directories. This means that step 7 now works, but steps 5 and 6 are still useless. I like having only one way to specify classpath, but I could see others wanting the CLASSPATH and ACTIVEMQ_CLASSPATH settings to work.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://issues.apache.org/activemq/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira