Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330265

Summary: STOP.PORT and STOP.KEY behave incorrectly when paired with --exec in a modified start.ini
Product: [RT] Jetty Reporter: Chad Johnson <chadjamesjohnson>
Component: serverAssignee: Greg Wilkins <gregw>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: jetty-inbox
Version: unspecified   
Target Milestone: 7.1.x   
Hardware: Macintosh   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Chad Johnson CLA 2010-11-15 11:51:39 EST 
Build Identifier: jetty-7.2.0.v20101020

When the start.ini is modified with an --exec prefix STOP.PORT and STOP.KEY are behaving incorrectly.  These two settings are indeed being honored but when the stop action is fired it is only stopping the parent process and not the actual child process that represents the web app server.

Reproducible: Always

Steps to Reproduce:
1. Modify the start.ini with an --exec prefix and STOP.PORT / STOP.KEY values
2. Start jetty
3. Attempt to stop jetty with --stop
4. Only the parent java process stops.  Leaving the primary Jetty process running.
Comment 1 Greg Wilkins CLA 2010-11-17 17:41:40 EST 
fixed in r2534