Jboss EAP 6.0.0 with hornetq, Hornetq configuration disappears.

[nishant_ag14]

Hi,

We are running Jboss EAP 6 in our application. WE have multiple nodes of Jboss eap 6 running in domain mode. there is a single domain controller.

We have few modes dedicated as JMS servers where we do not deploy any application and the Jboss is only used as JMS server, we are using inbuilt hornetq as JMS provider.

Other nodes in the cluster connect to these JMS Servers as producers or consumers (MDB).

All of this is managed by a single domain controller. we have defined 2 profile one for JMS Server where we only do hornetq server related configuration in jms subsystem. Other profile is for JMS producer/consumer where apart from other configuration we also do hornetq configuration like below in domain.xml of domain controller:

<hornetq-server>

    <security-enabled>false</security-enabled>

    <connectors>

        <connector name="netty-connector">

            <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

            <param key="host" value="10.133.2.122"/>

            <param key="port" value="5545"/>

            <param key="use-nio" value="true"/>

        </connector>

        <connector name="netty-connector127">

            <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

            <param key="host" value="10.133.2.127"/>

            <param key="port" value="5545"/>

            <param key="use-nio" value="true"/>

        </connector>

    </connectors>

    <jms-connection-factories>

        <pooled-connection-factory name="hornetq-ra">

            <transaction mode="xa"/>

            <connectors>

                <connector-ref connector-name="netty-connector"/>

                <connector-ref connector-name="netty-connector127"/>

            </connectors>

            <entries>

                <entry name="jms/avaya/spirit/ConnectionFactory"/>

                <entry name="java:/JmsXA"/>

            </entries>

            <use-global-pools>false</use-global-pools>

            <scheduled-thread-pool-max-size>10</scheduled-thread-pool-max-size>

            <thread-pool-max-size>-1</thread-pool-max-size>

        </pooled-connection-factory>

    </jms-connection-factories>

</hornetq-server>

In the above configuraiton we have defined netty connectors for each of the JMS servers and the referred to those connectors in the pooled connection factory so that MDB can connect to these JMS servers.

Everythig works great and all server connect to other as expected. But if we make any change in domain controller UI so that domain.xml has to change (eg. change deployment, change log level etc.) then as the domain.xml is written by domain controller UI then the above configuration is not persisted to file as it is and it gets converted like below:

<hornetq-server>

    <security-enabled>false</security-enabled>

    <connectors>

        <connector name="netty-connector">

            <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

            <param key="host" value="10.133.2.122"/>

            <param key="port" value="5545"/>

            <param key="use-nio" value="true"/>

        </connector>

        <connector name="netty-connector127">

            <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>

            <param key="host" value="10.133.2.127"/>

            <param key="port" value="5545"/>

            <param key="use-nio" value="true"/>

        </connector>

    </connectors>

</hornetq-server>

So you will see that my JMS factory details is gone. So it I have to restart my domain controller and subsequently other nodes then it gives problem because of this config change.

could you suggest what may be going wring here? or am i doing something wrong?

If you need more details please let me know.

-Nishant

[jaikiran]

From what I remember, there was a bug fix for this. You should contact the support team (via the support portal) to get a patch or to upgrade to a newer EAP6 version.

[nishant_ag14]

I requested customer support portal and this is a bug https://issues.jboss.org/browse/AS7-5538 which is resolved in 6.1.0 and there is a workaround as well.

however the workaround partially solves the problem as i had <transaction mode="local"/> in pooled connection factory that became <transaction mode="xa"/> after it is persisted

[jaikiran]

Nishant Agrawal wrote:

however the workaround partially solves the problem as i had <transaction mode="local"/> in pooled connection factory that became <transaction mode="xa"/> after it is persisted

Can you please explain a bit more about this? Also, if this is happening against your EAP paid version then checking with the support team would be better since they might remember whether a fix/patch is available for it.