Return-Path: X-Original-To: apmail-geronimo-dev-archive@www.apache.org Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5C6D110A57 for ; Thu, 2 May 2013 16:40:18 +0000 (UTC) Received: (qmail 25126 invoked by uid 500); 2 May 2013 16:40:17 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 24470 invoked by uid 500); 2 May 2013 16:40:16 -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 List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 24246 invoked by uid 99); 2 May 2013 16:40:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 May 2013 16:40:16 +0000 Date: Thu, 2 May 2013 16:40:15 +0000 (UTC) From: "Jarek Gawor (JIRA)" To: dev@geronimo.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (GERONIMODEVTOOLS-810) Server status not updated as server hostname is changed in server configuration MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jarek Gawor created GERONIMODEVTOOLS-810: -------------------------------------------- Summary: Server status not updated as server hostname is changed in server configuration Key: GERONIMODEVTOOLS-810 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-810 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Here's are the steps to demonstrate the issue: 1) Stat a local server - serer status should be [Started] 2) Edit server configuration and change hostname to specify a server on a remote host. The remote server should be stopped. The server status should eventually be updated to [Stopped] but it does not change. That's happening because GEP cached a connection to the local server and won't release it until the local server is stopped somehow. Once the cached connection is released the server status will reflect the right status of the remote server. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira