Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 30407 invoked from network); 13 Dec 2005 22:10:26 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Dec 2005 22:10:26 -0000 Received: (qmail 67861 invoked by uid 500); 13 Dec 2005 22:10:22 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 67633 invoked by uid 500); 13 Dec 2005 22:10:18 -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 67621 invoked by uid 99); 13 Dec 2005 22:10:17 -0000 X-ASF-Spam-Status: No, hits=1.3 required=10.0 tests=SPF_FAIL X-Spam-Check-By: apache.org Received: from [192.87.106.226] (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 13 Dec 2005 14:10:17 -0800 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 2170F1BC for ; Tue, 13 Dec 2005 23:09:46 +0100 (CET) Message-ID: <2088440115.1134511786083.JavaMail.jira@ajax.apache.org> Date: Tue, 13 Dec 2005 23:09:46 +0100 (CET) From: "John Sisson (JIRA)" To: dev@geronimo.apache.org Subject: [jira] Updated: (GERONIMO-1352) RMI port number is not specified in URL for JMXConnector in server config.xml files In-Reply-To: <1454925253.1134510827227.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/GERONIMO-1352?page=all ] John Sisson updated GERONIMO-1352: ---------------------------------- Description: The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. Currently if a user changes the RMI port number they will get exceptions at startup. I tried changing the JMXConnector URL to specify the port but it was not used. Basically this means if a site has port 1099 in use, they cannot run Geronimo. was: The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. Currently if a user changes the RMI port number they will get exceptions at startup. > RMI port number is not specified in URL for JMXConnector in server config.xml files > ----------------------------------------------------------------------------------- > > Key: GERONIMO-1352 > URL: http://issues.apache.org/jira/browse/GERONIMO-1352 > Project: Geronimo > Type: Bug > Components: startup/shutdown, usability > Reporter: John Sisson > Assignee: John Sisson > Fix For: 1.0 > > The port number should be specified in the JMXConnector URL so that a user can search and replace the current port number (e.g. 1099) with the new value. > Currently the JMXConnector URL does not specified the port number therefore it always uses the default port. > Currently if a user changes the RMI port number they will get exceptions at startup. > I tried changing the JMXConnector URL to specify the port but it was not used. Basically this means if a site has port 1099 in use, they cannot run Geronimo. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira