Robert,

This is already fixed and running in the current 4.0 available in CVS.
The current controller dtd looks like:

<!ATTLIST Controller
 name                  CDATA #IMPLIED
 jdbcIpAddress         CDATA "0.0.0.0"
 jdbcPort              CDATA "25322"
 backlogSize           CDATA "10"
 allowAdditionalDriver (true | false) "true"
>

<!ELEMENT JmxSettings (SSL?)>
<!ATTLIST JmxSettings
 jmxIpAddress    CDATA "0.0.0.0"
 jmxRegistryPort CDATA "1090"
 jmxServerPort   CDATA "0"
 login           CDATA #IMPLIED
 password        CDATA #IMPLIED
>

This way we have a clear separation between JMX and controller settings.

Best,
Emmanuel


This might be better to change in 4.0 if it looks like real surgery. Some of this code is quite delicate.

Thanks, Robert

On 9/29/08 1:04 PM, "Emmanuel Cecchet" <[EMAIL PROTECTED]> wrote:

    Hi Markus,

    >>> is there a way to access the controller via jmx from a remote host?
    >>> I've tried the default jmx url
    >>> 'service:jmx:rmi:///jndi/rmi://host:1090/jmxrmi' but that does
    not work.
    >>> I'm getting a connection refused.
    >>> A simple telnet to the host and port does work, so there is no
    firewall
    >>> blocking in between.
    >>>
    >>>
    >> Yes, if your JMX server is bound to 127.0.0.1 it will only
    accept local
    >> connections.
    >> If you are using Sequoia 2.10, try to put the public IP address
    of the
    >> machine in the ipAddress attribute of the RmiJmxAdaptor element
    of the
    >> controller config file.
    >>
    > I've tried to add an ipAddress element to the RmiJmxAdaptor but the
    > attribute is not valid (it also does not occure in the dtd for the
    > controllerfile in version 2.10.10).
    > Therefore I added it to the controller element which does work
    and log
    > the following line:
    >
    > 2008-09-29 10:22:29,314 INFO  controller.core.Controller JMX is
    enabled
    > 2008-09-29 10:22:29,329 INFO  controller.core.Controller Starting JMX
    > server on host: 217.114.70.68
    > 2008-09-29 10:22:29,329 WARN  controller.core.Controller Could
    not parse
    > RMI Server Port 'null
    >
    > But the connection to the server from remote is not possible.
    > Any additional help?
    >
    Oh yes, that code is messy in 2.10.10. You can try to override the
    ipAddress in the Controller element (JMX should also get its IP
    address
    from there). The null serverPort can be overriden by setting
    serverPort
    in the RmiJmxAdaptor element  (see
    https://forge.continuent.org/jira/browse/SEQUOIA-1058). Make sure you
    have the right DTD in your classpath.

    Hope this helps,
    Emmanuel

    --
    Emmanuel Cecchet
    FTO @ Frog Thinker
    Open Source Development & Consulting
    --
    Web: http://www.frogthinker.org
    email: [EMAIL PROTECTED]
    Skype: emmanuel_cecchet

    _______________________________________________
    Sequoia mailing list
    [email protected]
    https://forge.continuent.org/mailman/listinfo/sequoia



--
Robert Hodges, CTO, Continuent, Inc.
Email:  [EMAIL PROTECTED]
Mobile:  +1-510-501-3728  Skype:  hodgesrm
------------------------------------------------------------------------

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia


--
Emmanuel Cecchet
FTO @ Frog Thinker Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet

_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to