In Jboss7.1.1 final HA environment created using standalone-full-ha.xml, standby node not consuming message from Hornet Queue or topic

[veenaonnet]

Hi,

I have setup HA enviroment using standalone-full-ha.xml and jgroups.

It is showing both nodes as cluster members. Also messages sent using jgroup are working fine.

However standby node is not consuming any message from the Hornet queue. All messages are consumed by Active node only. Same issue is there with topic.

Am I missing anything in configuration?

My standalone-full-ha JMS configuration is :

   <subsystem xmlns="urn:jboss:domain:messaging:1.1">
            <hornetq-server>
                <clustered>true</clustered>
                <persistence-enabled>true</persistence-enabled>
                <cluster-user>admin</cluster-user>
                <cluster-password>omneon</cluster-password>
                <journal-file-size>102400</journal-file-size>
                <journal-min-files>2</journal-min-files>

                <connectors>
                    <netty-connector name="netty" socket-binding="messaging"/>
                    <netty-connector name="netty-throughput" socket-binding="messaging-throughput">
                        <param key="batch-delay" value="50"/>
                    </netty-connector>
                    <in-vm-connector name="in-vm" server-id="0"/>
                </connectors>

                <acceptors>
                    <netty-acceptor name="netty" socket-binding="messaging"/>
                    <netty-acceptor name="netty-throughput" socket-binding="messaging-throughput">
                        <param key="batch-delay" value="50"/>
                        <param key="direct-deliver" value="false"/>
                    </netty-acceptor>
                    <in-vm-acceptor name="in-vm" server-id="0"/>
                </acceptors>

                <broadcast-groups>
                    <broadcast-group name="bg-group">
                        <group-address>228.200.101.199</group-address>
                        <group-port>9876</group-port>
                        <broadcast-period>5000</broadcast-period>
                        <connector-ref>
                            netty
                        </connector-ref>
                    </broadcast-group>

<discovery-groups>
                    <discovery-group name="dg-group">
                        <group-address>228.200.101.199</group-address>
                        <group-port>9876</group-port>
                        <refresh-timeout>10000</refresh-timeout>
                    </discovery-group>
                </discovery-groups>

                <cluster-connections>
                    <cluster-connection name="msf-cluster-10.200.101.199">
                        <address>jms</address>
                        <connector-ref>netty</connector-ref>
                        <discovery-group-ref discovery-group-name="dg-group"/>
                    </cluster-connection>
                </cluster-connections>

                <security-settings>
                    <security-setting match="#">
                        <permission type="send" roles="guest"/>
                        <permission type="consume" roles="guest"/>
                        <permission type="createNonDurableQueue" roles="guest"/>
                        <permission type="deleteNonDurableQueue" roles="guest"/>
                    </security-setting>
                </security-settings>

                <address-settings>
                    <address-setting match="#">
                        <dead-letter-address>jms.queue.DLQ</dead-letter-address>
                        <expiry-address>jms.queue.ExpiryQueue</expiry-address>
                        <redelivery-delay>0</redelivery-delay>
                        <max-size-bytes>10485760</max-size-bytes>
                        <address-full-policy>BLOCK</address-full-policy>
                        <message-counter-history-day-limit>10</message-counter-history-day-limit>
                        <redistribution-delay>1000</redistribution-delay>
                    </address-setting>
                </address-settings>

                <jms-connection-factories>

                <connection-factory name="InVmConnectionFactory">
                        <connectors>
                            <connector-ref connector-name="in-vm"/>
                        </connectors>
                        <entries>
                            <entry name="java:/ConnectionFactory"/>
                        </entries>
                    </connection-factory>
                    <connection-factory name="RemoteConnectionFactory">
                        <connectors>
                            <connector-ref connector-name="netty"/>
                        </connectors>
                        <entries>
                            <entry name="RemoteConnectionFactory"/>
                            <entry name="java:jboss/exported/jms/RemoteConnectionFactory"/>
                        </entries>
                    </connection-factory>
                    <pooled-connection-factory name="hornetq-ra">
                        <transaction mode="xa"/>
                        <connectors>
                            <connector-ref connector-name="in-vm"/>
                        </connectors>
                        <entries>
                            <entry name="java:/JmsXA"/>
                        </entries>
                    </pooled-connection-factory>
                </jms-connection-factories>

                <jms-destinations>
                    <jms-queue name="testQueue">
                        <entry name="queue/test"/>
                        <entry name="java:jboss/exported/jms/queue/test"/>
                    </jms-queue>

-----

Thanks,

Veena

[veenaonnet]

The issue is because I am using bind address as 0.0.0.0 which becomes same for all the cluster members. If I use server node IP as a bind address it works fine.

However I need to use 0.0.0.0 so that UI is accessible from VIP as well individual server IPs.

Is there any startup parameter I can use to specify bind address to be used by HornetQ?

[jbertram]

Try this...

Replace:

<netty-connector name="netty" socket-binding="messaging"/>

with:

<connector name="netty">
   <factory-class>org.hornetq.core.remoting.impl.netty.NettyConnectorFactory</factory-class>
   <param key="host" value="my-public-ip-hostname"/>
   <param key="port" value="5445"/>
</connector>

inside <hornetq-server><connectors> inside your standalone-full.xml

[veenaonnet]

Thanks Justin.

Do I need to change acceptor also? Is it required?

<acceptor name="netty">

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

     <param key="host" value="my-public-ip-hostname"/> 

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

</acceptor> 

[jbertram]

Based on your previous comment you are already binding your acceptor to 0.0.0.0 so that answer to your question is - no.

[veenaonnet]

Thanks Justin for your help.

[aditya-vajra]

Hi Frnz ,

I want to increase time spent in processing the large message more than what the JbossAS7 configuration allows. Is there any way  to set the "readtimeout" in JBOSS configuration to increase the time that the system spends on reading a message, so the entire message is read completely.

Thanks in advance