Using bin/activemq init script uses current directory for resolving paths
-------------------------------------------------------------------------
Key: AMQ-3762
URL: https://issues.apache.org/jira/browse/AMQ-3762
Project: ActiveMQ
Issue Type: Bug
Components: Connector
Affects Versions: 5.5.1
Environment: Linux 3.0.0-14-virtual #23-Ubuntu SMP Mon Nov 21 21:09:11
UTC 2011 x86_64 x86_64 x86_64 GNU/Linux
Reporter: Larry Meadors
I think I found a bug in the the bin/activemq script. It's simple to
fix, and looks like someone was just trying to be too careful. :)
When trying to determine the Active MQ installation dir, it does this:
saveddir=`pwd`
...then later it does this:
cd "$saveddir"
In my case, I call the script from my home directory, and then when it
tries to <import resource="jetty.xml"/>, it fails because there is no
jetty.xml in my home directory.
I changed the script to do this:
#saveddir=`pwd`
...
#cd "$saveddir"
...and now it works perfectly.
That saveddir variable is actually not needed at all. When you call a
script that has "#!/bin/sh" as the 1st line, it invokes a new shell,
so after the script finishes, that shell is closed and you go back to
the calling shell, and cd was never called there.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
