You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2009/03/29 18:47:50 UTC

[jira] Commented: (SYNAPSE-526) Add server connector to make use of existing MBeans

    [ https://issues.apache.org/jira/browse/SYNAPSE-526?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12693585#action_12693585 ] 

Asankha C. Perera commented on SYNAPSE-526:
-------------------------------------------

Hi Eric

The patch fails against the current trunk.. could you clarify and update the patch

thanks
asankha

asankha@asankha:~/code/synapse/modules/core$ patch -p0 --dry-run < /tmp/JmxAdapter.patch 
(Stripping trailing CRs from patch.)
patching file src/main/java/org/apache/synapse/Axis2SynapseController.java
Hunk #1 FAILED at 23.
Hunk #2 FAILED at 51.
Hunk #3 FAILED at 74.
Hunk #4 FAILED at 154.
Hunk #5 FAILED at 260.
Hunk #6 FAILED at 292.
6 out of 6 hunks FAILED -- saving rejects to file src/main/java/org/apache/synapse/Axis2SynapseController.java.rej
(Stripping trailing CRs from patch.)
patching file src/main/java/org/apache/synapse/SynapseConstants.java
(Stripping trailing CRs from patch.)
patching file src/main/java/org/apache/synapse/JmxAdapter.java


> Add server connector to make use of existing MBeans
> ---------------------------------------------------
>
>                 Key: SYNAPSE-526
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-526
>             Project: Synapse
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Eric Hubert
>            Priority: Minor
>             Fix For: 1.3
>
>         Attachments: JmxAdapter.patch
>
>
> Hi,
> currently Synapse does not create a JMX server connector to enable the user to make use of the existing MBeans via JConsole or any other JMX-compliant management solution. The attached patch introduces a small JMXAdapter class to create an RMI registry using a specified JNDI port in synapse.properties (synapse.jmx.jndiPort). Only if this port is specified it will create the registry and start the server connector. If the user additionally specifies a fixed RMI port in synapse.properties (synapse.jmx.rmiPort) instead of using a dynamic RMI port Synapse will use the specified port thus allowing a firewalled setup (you have to open both ports in your firewall).
> The Javadoc of the class explains the connect syntax:
> service:jmx:rmi:///jndi/rmi://<hostname>:<jndiPort>/synapse or service:jmx:rmi://<hostname>:<rmiPort>/jndi/rmi://<hostname>:<jndiPort>/synapse
> This patch shall just demonstrate the basic idea. I'm of course willing to contribute further work on this (including documentation). The best place in the startup and shutdown phase of Synapse should be discussed. I'm going to start a separate discussion on the order of actions in the Synapse startup phase anyway.

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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org