[infinispan-issues] [JBoss JIRA] (ISPN-5983) Cannot connect via JMX to servers managed in domain mode

[Jiří Holuša (JIRA)]

Jiří Holuša created ISPN-5983:
---------------------------------

             Summary: Cannot connect via JMX to servers managed in domain mode
                 Key: ISPN-5983
                 URL: https://issues.jboss.org/browse/ISPN-5983
             Project: Infinispan
          Issue Type: Bug
          Components: Documentation-Servers, Server
    Affects Versions: 8.1.0.Beta1
            Reporter: Jiří Holuša


I was trying to connect remotely to Infinispan servers run in domain mode. I was following instructions that worked for me with Wildfly 10 (e.g. at https://goldmann.pl/blog/2013/04/16/jmx-connections-to-jboss-as/ ), but that didn't work with Infinispan servers. There is no documentation about how to do this and since it's not working the WildFly way, I mark this issue as bug.

After investigation, we (many thanks to [~lthon]) found out that it doesn't work with ISPN server, because WildFly uses http upgrade for this purpose via http-connector. The connector (by default commented in the domain.xml) requires undertow subsystem to work, however, ISPN server doesn't have it.

There are two possible solutions:
* add the undertow subsystem. The modules/ directory already has the jars, therefore it's only needed to add following to domain.xml and than you can connect to the server via JMX URL service:jmx:remote+http://localhost:8080. However, I wouldn't prefer this solution.
{code}
<subsystem xmlns="urn:jboss:domain:undertow:3.0">
    <buffer-cache name="default"/>
    <server name="default-server">
        <http-listener name="default" socket-binding="http"/>
        <host name="default-host" alias="localhost"/>
    </server>
    <servlet-container name="default"/>
</subsystem>
{code}

* second solution is to create remoting endpoint just the way it was before in JBoss AS 7, therefore add following to the domain.xml and then connect via JMX URL: service:jmx:remote://localhost:4447. This solution should be preferred IMHO.
{code}
 <connector name="remoting-connector" socket-binding="remoting" security-realm="ApplicationRealm"/>
{code}
{code}
<socket-binding name="remoting" port="4447"/>
{code}

I will soon issue a PR with the solution number 2 and appropriate update of documentation. Of course, these options should be disabled by default, by I think it would be nice to have them commented in the domain.xml.







--
This message was sent by Atlassian JIRA
(v6.4.11#64026)