XARecoveryConfig error.
I have a simple JMS cluster, live/backup configuration.
I get the following error when the live server is not running and bringing up the backup server:
15:53:10,952 WARN [org.hornetq.jms.server] (MSC service thread 1-4) HQ122018: Could not start recovery discovery on XARecoveryConfig [transportConfiguration = [TransportConfiguration(name=85ddb239-ded0-11e4-9ea2-6516c6c66c4b, factory=org-hornetq-core-remoting-impl-netty-NettyConnectorFactory) ?port=5445&host=xx-x-xxx-xxx], discoveryConfiguration = null, username=null, password=****], we will retry every recovery scan until the server is available
I want the backup server to become 'live' if the live server is down. I can't get around this error, though. Has anybody run into this?
The following is the hornetq configuration in the standalone xml file:
<hornetq-server>
<persistence-enabled>true</persistence-enabled>
<security-enabled>false</security-enabled>
<backup>true</backup>
<allow-failback>false</allow-failback>
<failover-on-shutdown>true</failover-on-shutdown>
<shared-store>false</shared-store>
<journal-type>ASYNCIO</journal-type>
<journal-file-size>5024000</journal-file-size>
<journal-min-files>2</journal-min-files>
<check-for-live-server>true</check-for-live-server>
<backup-group-name>mediation-backup-group</backup-group-name>
<connectors>
<netty-connector name="netty" socket-binding="messaging">
<param key="use-nio" value="true"/>
</netty-connector>
<netty-connector name="netty-throughput" socket-binding="messaging-throughput">
<param key="batch-delay" value="50"/>
</netty-connector>
<netty-connector name="primary-mediation" socket-binding="primary-mediation-binding"/>
<netty-connector name="secondary-mediation" socket-binding="secondary-mediation-binding"/>
<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>
<cluster-connections>
<cluster-connection name="mediation-ha-cluster">
<address>jms</address>
<connector-ref>primary-mediation</connector-ref>
<static-connectors>
<connector-ref>
secondary-mediation
</connector-ref>
</static-connectors>
</cluster-connection>
</cluster-connections>
<address-settings>
<address-setting match="#">
<dead-letter-address>jms.queue.DLQ</dead-letter-address>
<expiry-address>jms.queue.ExpiryQueue</expiry-address>
<redelivery-delay>5000</redelivery-delay>
<max-delivery-attempts>-1</max-delivery-attempts>
<max-size-bytes>100485760</max-size-bytes>
<address-full-policy>PAGE</address-full-policy>
<message-counter-history-day-limit>10</message-counter-history-day-limit>
</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="java:jboss/exported/jms/RemoteConnectionFactory"/>
</entries>
</connection-factory>
<connection-factory name="mediationrx">
<connectors>
<connector-ref connector-name="primary-mediation"/>
</connectors>
<entries>
<entry name="java:/MediationConnectionFactoryRx"/>
</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>
<pooled-connection-factory name="mediation">
<transaction mode="xa"/>
<connectors>
<connector-ref connector-name="primary-mediation"/>
</connectors>
<entries>
<entry name="java:/MediationConnectionFactory"/>
</entries>
</pooled-connection-factory>
</jms-connection-factories>
</hornetq-server>