Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 13753 invoked from network); 5 Nov 2004 03:45:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 5 Nov 2004 03:45:09 -0000 Received: (qmail 53425 invoked by uid 500); 5 Nov 2004 03:44:38 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 53368 invoked by uid 500); 5 Nov 2004 03:44:37 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@geronimo.apache.org Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 53339 invoked by uid 99); 5 Nov 2004 03:44:37 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [192.18.33.10] (HELO exchange.sun.com) (192.18.33.10) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 04 Nov 2004 19:44:34 -0800 Received: (qmail 1253 invoked from network); 5 Nov 2004 03:44:32 -0000 Received: from localhost (HELO nagoya) (127.0.0.1) by nagoya.betaversion.org with SMTP; 5 Nov 2004 03:44:32 -0000 Message-ID: <2001700809.1099626272801.JavaMail.apache@nagoya> Date: Thu, 4 Nov 2004 19:44:32 -0800 (PST) From: "Aaron Mulder (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Created: (GERONIMO-440) Installing package in offline mode should fail if server is running Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Installing package in offline mode should fail if server is running ------------------------------------------------------------------- Key: GERONIMO-440 URL: http://nagoya.apache.org/jira/browse/GERONIMO-440 Project: Apache Geronimo Type: Improvement Components: deployment Versions: 1.0-M2 Reporter: Aaron Mulder The deployment feature of building an executable package and installing it into the server's configuration store should not work if the server is running. We don't want to allow the deploy tool and the server to make conflicting changes, etc. The easy way to detect if the server is running would be to try to connect to its JMX remoting interface, but this throws a security exception. Probably it would be good enough to detect the security exception as opposed to a "nothing listening on that port" or "whatever's there isn't Geronimo". But none of that will help if the server is running and listening on a nonstandard port. Perhaps the server should have a lock file while running or something like that. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://nagoya.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira