Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <782317478.1218578510223.JavaMail.jira@brutus>
Date: Tue, 12 Aug 2008 15:01:50 -0700 (PDT)
From: "Jarek Gawor (JIRA)" <jira@apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-4238) JMX over SSL improvements
In-Reply-To: <2128163176.1218569504430.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12622001#action_12622001 ] 

Jarek Gawor commented on GERONIMO-4238:
---------------------------------------

Committed changes to trunk (revision 685332) and branches/2.1 (revision 685333) that took care of 2) and 3). stop-server gshell command already worked with a secure JMX server but start-server did not. That's fixed now.


> JMX over SSL improvements
> -------------------------
>
>                 Key: GERONIMO-4238
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-4238
>             Project: Geronimo
>          Issue Type: Improvement
>      Security Level: public(Regular issues) 
>          Components: general
>    Affects Versions: 2.1.2, 2.2
>            Reporter: Jarek Gawor
>
> 1) After the non-secure JMX server is disabled, the server won't start up because the org.apache.geronimo.configs/clustering module fails to find the JMX server. Not sure why the clustering module needs the JMX server in the first place but we should allow the server to work ok with a secure JMX server.
> 2) Shutdown command needs to support --secure option.
> 3) Test if gshell start-server/stop-server work ok with a secure JMX server.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.