Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 330265 - STOP.PORT and STOP.KEY behave incorrectly when paired with --exec in a modified start.ini
Summary: STOP.PORT and STOP.KEY behave incorrectly when paired with --exec in a modifi...
Status: RESOLVED FIXED
Alias: None
Product: Jetty
Classification: RT
Component: server (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: 7.1.x   Edit
Assignee: Greg Wilkins CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-15 11:51 EST by Chad Johnson CLA
Modified: 2010-11-17 17:41 EST (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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