[AMQ-3762] Using bin/activemq init script uses current directory for resolving paths

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Abandoned
• Affects Version/s: 5.5.1
• Component/s: Broker

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

• Assignee: Unassigned
• Reporter: Larry E. Meadors
• Created: 12/Mar/12 13:15
• Updated: 13/Mar/22 14:02
• Resolved: 13/Mar/22 14:02

Description

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.