Have you tried using the non-wrapper script (in the root folder) as opposed to wrapper?

We'll look into the issue with the wrappper script.

Thanks for the report.
Edwin

i tried it but had problems configuring it to rename the context which is quite easy in the wrapper.

Best,

Caspar.

You can rename the context of the default startup script by changing the RUN_CMD line in the bamboo.sh file:

RUN_CMD="java -Xms256m -Xmx512m -XX:MaxPermSize=256m -Djava.awt.headless=true -classpath $CLASSPATH -Dorg.mortbay.xml.XmlParser.NotValidating=true -Djetty.port=8085 com.atlassian.bamboo.server.Server 8085 ./webapp /"

to

RUN_CMD="java -Xms256m -Xmx512m -XX:MaxPermSize=256m -Djava.awt.headless=true -classpath $CLASSPATH -Dorg.mortbay.xml.XmlParser.NotValidating=true -Djetty.port=8085 com.atlassian.bamboo.server.Server 8085 ./webapp /MY_CONTEXT"

The context path is the last argument in the line, with default being "/" - the root.

Cheers,
Edwin

This issue is now fixed and should be shipped in the next Bamboo release.

We changed the Bamboo start-up script to use "uname -m" (exclusively) to determine the system architecture.

Cheers,
Ajay