You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Jarek Gawor (JIRA)" <ji...@apache.org> on 2008/08/12 21:31:44 UTC
[jira] Created: (GERONIMO-4238) JMX over SSL improvements
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.
[jira] Commented: (GERONIMO-4238) JMX over SSL improvements
Posted by "Jarek Gawor (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (GERONIMO-4238) JMX over SSL improvements
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang reassigned GERONIMO-4238:
-------------------------------------
Assignee: Shawn Jiang
> 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
> Assignee: Shawn Jiang
> Attachments: 4238#1.trunk.patch
>
>
> 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.
[jira] Updated: (GERONIMO-4238) JMX over SSL improvements
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated GERONIMO-4238:
----------------------------------
Fix Version/s: 2.2.1
> 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
> Assignee: Shawn Jiang
> Fix For: 2.2.1
>
> Attachments: 4238#1.trunk.patch, G4238_g21.patch
>
>
> 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.
[jira] Updated: (GERONIMO-4238) JMX over SSL improvements
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated GERONIMO-4238:
----------------------------------
Patch Info: [Patch Available]
> 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
> Assignee: Shawn Jiang
> Attachments: 4238#1.trunk.patch
>
>
> 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.
[jira] Updated: (GERONIMO-4238) JMX over SSL improvements
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated GERONIMO-4238:
----------------------------------
Attachment: G4238_g21.patch
This is the patch for 2.1 branch.
> 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
> Assignee: Shawn Jiang
> Attachments: 4238#1.trunk.patch, G4238_g21.patch
>
>
> 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.
[jira] Closed: (GERONIMO-4238) JMX over SSL improvements
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang closed GERONIMO-4238.
---------------------------------
Fix Version/s: 2.1.5
Resolution: Fixed
#2 #3 were fixed.
#1 is a duplicate of https://issues.apache.org/jira/browse/GERONIMO-5148
> 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
> Assignee: Shawn Jiang
> Fix For: 2.2.1, 2.1.5
>
> Attachments: 4238#1.trunk.patch, G4238_g21.patch
>
>
> 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.
[jira] Updated: (GERONIMO-4238) JMX over SSL improvements
Posted by "Shawn Jiang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-4238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shawn Jiang updated GERONIMO-4238:
----------------------------------
Attachment: 4238#1.trunk.patch
This is the patch to fix #1 problem in trunk. If it's OK, I'll make a patch for G21 branch. Thanks.
> 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
> Attachments: 4238#1.trunk.patch
>
>
> 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.