[jira] Updated: (LOOM-13) Start/Stop Loom Scripts

The following issue has been updated:

    Updater: peter royal (mailto:[email protected])
       Date: Wed, 14 Apr 2004 8:49 PM
    Changes:
             Fix Version changed to future
             Fix Version changed from 1.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/secure/ViewIssue.jspa?key=LOOM-13&page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=LOOM-13

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: LOOM-13
    Summary: Start/Stop Loom Scripts
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: loom
   Fix Fors:
             future

   Assignee: 
   Reporter: Mauro Talevi

    Created: Wed, 30 Jul 2003 5:08 AM
    Updated: Wed, 14 Apr 2004 8:49 PM

Description:
Expand the Loom scripts on platforms where it is supported so that you can start Loom in background and also stop when it is running in background via something like;
 
$LOOM_HOME/bin/start.sh
$LOOM_HOME/bin/stop.sh
 
Possible ways of saying shutdown include;
1. storing the process ID somewhere and sending kill message to process
2. communicating via JMX to say shutdown
3. communicating via tcp to say shutdown
4. enhancing wrapper project (http://wrapper.sourceforge.net/) so that there is a java monitor process that will monitor the "real" Loom instance. Then we could require wrapper as part of all Loom installs but not require that native daemons be present
 
(4) is the best option.
(3) requires that we pass some sort of "key" or magic cookie between server and client process so that the program that sends shutdown message has to have access to file in Loom directory (Thus offering a vague form of security)



---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira