HornetQ bound to all interfaces (0.0.0.0) - unable to setup JMS bridge in this way between two 'Wildfly-8.2.1Final' instances

[branku]

Hello,

in my scenario a new IP is assigned to a server when it becomes a primary one ( in our failover solution ).

Clients ( JMS bridges in this case ) use this 'new IP' to connect to whatever server is a primary one to establish this JMS bridge. ( <jms-bridge> contains this 'new IP' ).

However,  since the server does not have this IP when it is starting ( as it is a fail-over server ), I cannot bind HornetQ to listen on this address.

I tried make it listen on "0.0.0.0", but in this way JMS bridge cannot be established for some reason, although I can see the communication attempts.

JMS bridge client:

2015-12-08 09:54:21,631 INFO  [org.hornetq.jms.server] (pool-3-thread-3) HQ121000: Failed to set up JMS bridge connections. Most probably the source or target servers are unavailable. Will retry after a pause of 1,000 ms

2015-12-08 09:54:52,944 WARN  [org.hornetq.jms.server] (pool-3-thread-3) HQ122010: Failed to connect JMS Bridge: javax.jms.JMSException: Failed to create session factory

        at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:673) [hornetq-jms-client-2.4.5.Final.jar:]

        at org.hornetq.jms.client.HornetQConnectionFactory.createConnection(HornetQConnectionFactory.java:112) [hornetq-jms-client-2.4.5.Final.jar:]

        at org.hornetq.jms.bridge.impl.JMSBridgeImpl.createConnection(JMSBridgeImpl.java:1141) [hornetq-jms-server-2.4.5.Final.jar:]

        at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjects(JMSBridgeImpl.java:1337) [hornetq-jms-server-2.4.5.Final.jar:]

        at org.hornetq.jms.bridge.impl.JMSBridgeImpl.setupJMSObjectsWithRetry(JMSBridgeImpl.java:1471) [hornetq-jms-server-2.4.5.Final.jar:]

        at org.hornetq.jms.bridge.impl.JMSBridgeImpl.access$2200(JMSBridgeImpl.java:76) [hornetq-jms-server-2.4.5.Final.jar:]

        at org.hornetq.jms.bridge.impl.JMSBridgeImpl$FailureHandler.run(JMSBridgeImpl.java:2079) [hornetq-jms-server-2.4.5.Final.jar:]

        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_65]

        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_65]

        at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_65]

Caused by: HornetQNotConnectedException[errorType=NOT_CONNECTED message=HQ119007: Cannot connect to server(s). Tried with all available servers.]

        at org.hornetq.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:905) [hornetq-core-client-2.4.5.Final.jar:]

        at org.hornetq.jms.client.HornetQConnectionFactory.createConnectionInternal(HornetQConnectionFactory.java:669) [hornetq-jms-client-2.4.5.Final.jar:]

        ... 9 more

JMS bridge server:

2015-12-08 10:10:29,199 INFO  [org.jboss.as.naming] (default task-10) JBAS011806: Channel end notification received, closing channel Channel ID 3ad9049a (inbound) of Remoting connection 57b327d8 to /192.168.103.31:34485

When I bind HornetQ subsystem to specific 192.168.*.* address everything works great.

Can anyone please think of a workaround or why exactly it is that HornetQ is unable to work with 0.0.0.0 correctly? Please note that I am not limited to using http communication if that is the source of the problem.

( I am 'jms bridging' identical wildfly server versions - 8.2.1.Final ). Configurations are identical, apart from the <jms-bridge> part, where IP addresses differ - both addresses are these 'new IP' or virtual IPs.

Many thanks,

b.

[branku]

Configurations are identical, apart from the <jms-bridge> part, where IP addresses differ - both addresses are these 'new IP' or virtual IPs.

Please ignore this sentence which may be confusing. We are bridging both ways, but that is not related to this problem I believe.

b.

[jaysensharma]

When you bind hornetQ on address 0.0.0.0  then do you see following kind of INFO message in your Logs?

   @LogMessage(level = Logger.Level.INFO)
   @Message(id = 121006, value = "Invalid \"host\" value \"0.0.0.0\" detected for \"{0}\" connector. Switching to \"{1}\"." +
         " If this new address is incorrect please manually configure the connector to use the proper one." ,
         format = Message.Format.MESSAGE_FORMAT)
   void invalidHostForConnector(String name, String newHost);

See:  hornetq/HornetQJMSLogger.java at 2a29601ecd96b1e117551ff7df0349b601d4c082 · jbertram/hornetq · GitHub

[jaysensharma]

Please ignore... The above comment ... as i do not see the class "HornetQJMSLogger" in WildFly 8.2.1

But for hornetQ client  the 0.0.0.0 address does not make any sense.

[branku]

Hello,

I bind the server to 0.0.0.0 not the client. The jms bridge client is configured to connect to the mentioned 'new' common IP.

[jbertram]

I bind the server to 0.0.0.0 not the client. The jms bridge client is configured to connect to the mentioned 'new' common IP.

That's not entirely true.  The JMS bridge is using 192.168.103.30:8080 for the JNDI lookup, but the connector it gets back from the JNDI lookup will be using 0.0.0.0 because that's what you have configured for it to use.  Here's how the configuration works:

• JMS client (i.e. the bridge in your case) looks up and uses a particular connection factory, e.g. "jms/RemoteConnectionFactory".
• Said connection factory is configured to use a particular connector, e.g. "http-connector".
• The connector is configured with a particular socket-binding, e.g. "jms-http".
• The socket-binding is configured to use a particular interface, e.g. "jms-http-interface".
• The interface is configured to use a particular inet-address, e.g. 0.0.0.0 in your case.

That means in your configuration a JMS client will ultimately try to connect to 0.0.0.0 which, of course, isn't valid for a client.  Therefore you need to configure the connection factory to ultimately use a valid address.

BTW, this has been covered on the forums in multiple places.

[branku]

Thank you for your reply.

Can I instead provide the jms-bridge with a locally defined connector ( i.e. avoid remote JNDI lookup  ) ? That would be the quickest and cleanest solution imo.

Many thanks.

[jbertram]

Can I instead provide the jms-bridge with a locally defined connector ( i.e. avoid remote JNDI lookup  ) ? That would be the quickest and cleanest solution imo.

No. The JMS bridge is a JMS bridge.  You can't configure it with HornetQ implementation details.  You can only use standard JMS (along with JNDI which is discussed in the spec).

That said, if you're configuring a bridge between two instances of HornetQ you could use a "core" bridge.  That would be simpler, I think.  The JMS bridge is really meant to enable integration between different JMS providers (e.g. HornetQ and SonicMQ).