Bug 364924

Description Éric Daigneault 2011-11-27 21:16:02 EST

Build Identifier: jetty-7.2.2.v20101205 tried many builds up to last 8.x milestone)

When putting a dash in the path preceded by a space and --exec option is enabled in the .ini file (or the command Line) the VM will fail to start citing an unknown argument "-".

The problem was reliably reproduced with multiple builds starting from 7.2.2 all the way to the last nightly build of 8.  Possibly earlier builds are failing as well though I have not tried them).

Now knowing the problem it is quite easy to find a workaround however since spaces in paths should normally be supported this problem incurred a long and frustrating troubleshooting experience.  I am flagging this as critical because the whole system simply does not start, however the workaround is very simple...   just remove the spaces in the path.

The problem was reliably reproduced on different windows system (XP, 7, 7x64 2008, 2008r2) both with 32 and 64 bits VM (all in the 6 range from Oracle).

the following question on SO describes the problem
http://stackoverflow.com/questions/8255563/jetty-cannot-start-unable-to-create-the-virtual-machine-when-i-add-the-exec/8259148#8259148


Reproducible: Always

Steps to Reproduce:
1. Get a Jetty build (any from 7.2.2)
2. expand the archive in a folder and edit the name such that it contains a space followed by a dash (ex "jetty-7.2.2.v20101205 - prod").
3. Edit the ini file and enable the --exec option
4. make sure you have a war (the test war delivered with the archive will do)
5. start jetty (java -jar start.jar)
6. failed

The procedure was reliably applied to multiple builds and the defective behavior was reproduced every times.