Configuration of co-located backup server (activemq) in Wildfly10 using http-connector does not work in localhost in Windows

[wwang2016]

Hi,

I configured a co-located backup server in wildfly10 using netty-connector, and it worked in local machine (Windows10). I tested another instance with port offset (same local machine) together with this instance, and the cluster configuration worked fine.

When I was trying to test it in a vitualbox with multiple virtual machines (different IPs), I was able to simplify the connectors configuration so that I could just use http-connector/acceptor without the need to configure a netty-connector/acceptor. However, when I test the new configuration (without netty-connector/acceptor) in windows again, I got tons of warning, and the console printed out the warning like crazy. This was shortly after the server was started up. This issue never happened in the virutalbox VM, and I am worrying about if it could happen in production environment (different IPs) if I use the configuration without netty-connector/acceptor although I thought the virtualbox environment should be more closely related to production environment.

Tons of lines were printed out when I executed the following command:

netstat -ano | find /n "8080"

2016-09-12 09:41:43,125 WARN  [org.apache.activemq.artemis.core.server] (Thread-29 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@7e73d88b-1890859317)) AMQ222186: unable to authorise cluster control

2016-09-12 09:41:43,125 WARN  [org.apache.activemq.artemis.core.server] (Thread-23 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@7e73d88b-1890859317)) AMQ222186: unable to authorise cluster control

2016-09-12 09:41:43,125 WARN  [org.apache.activemq.artemis.core.server] (Thread-26 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@5c6c97cd-2083950753)) AMQ222186: unable to authorise cluster control

2016-09-12 09:41:43,627 WARN  [org.apache.activemq.artemis.core.client] (Thread-7 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@5c6c97cd-2083950753)) AMQ212025: did not connect the cluster connection to other nodes: java.lang.NullPointerException

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$PingRunnable.run(ClientSessionFactoryImpl.java:1174)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.schedulePing(ClientSessionFactoryImpl.java:905)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.establishNewConnection(ClientSessionFactoryImpl.java:1226)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:851)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:753)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:239)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:759)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:616)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:597)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl$4.run(ServerLocatorImpl.java:561)

  at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:100)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

  at java.lang.Thread.run(Thread.java:745)

2016-09-12 09:41:43,639 WARN  [org.apache.activemq.artemis.core.client] (Thread-29 (ActiveMQ-server-org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl$2@7e73d88b-1890859317)) AMQ212025: did not connect the cluster connection to other nodes: java.lang.NullPointerException

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl$PingRunnable.run(ClientSessionFactoryImpl.java:1174)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.schedulePing(ClientSessionFactoryImpl.java:905)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.establishNewConnection(ClientSessionFactoryImpl.java:1226)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnection(ClientSessionFactoryImpl.java:851)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.getConnectionWithRetry(ClientSessionFactoryImpl.java:753)

  at org.apache.activemq.artemis.core.client.impl.ClientSessionFactoryImpl.connect(ClientSessionFactoryImpl.java:239)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.createSessionFactory(ServerLocatorImpl.java:759)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:616)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl.connect(ServerLocatorImpl.java:597)

  at org.apache.activemq.artemis.core.client.impl.ServerLocatorImpl$4.run(ServerLocatorImpl.java:561)

  at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$ExecutorTask.run(OrderedExecutorFactory.java:100)

  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

  at java.lang.Thread.run(Thread.java:745)

2016-09-12 09:41:44,475 WARN  [org.apache.activemq.artemis.core.client] (activemq-failure-check-thread) AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from /10.25.25.104:54801. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

2016-09-12 09:41:44,484 INFO  [org.apache.activemq.artemis.core.server] (activemq-failure-check-thread) AMQ221021: failed to remove connection

2016-09-12 09:41:44,486 WARN  [org.apache.activemq.artemis.core.client] (activemq-failure-check-thread) AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from /10.25.25.104:54920. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

2016-09-12 09:41:44,495 INFO  [org.apache.activemq.artemis.core.server] (activemq-failure-check-thread) AMQ221021: failed to remove connection

2016-09-12 09:41:44,497 WARN  [org.apache.activemq.artemis.core.client] (activemq-failure-check-thread) AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from /10.25.25.104:54629. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

2016-09-12 09:41:44,506 INFO  [org.apache.activemq.artemis.core.server] (activemq-failure-check-thread) AMQ221021: failed to remove connection

2016-09-12 09:41:44,509 WARN  [org.apache.activemq.artemis.core.client] (activemq-failure-check-thread) AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from /10.25.25.104:54788. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

2016-09-12 09:41:44,517 INFO  [org.apache.activemq.artemis.core.server] (activemq-failure-check-thread) AMQ221021: failed to remove connection

2016-09-12 09:41:44,519 WARN  [org.apache.activemq.artemis.core.client] (activemq-failure-check-thread) AMQ212037: Connection failure has been detected: AMQ119014: Did not receive data from /10.25.25.104:55061. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

[jbertram]

I believe you can't use http-connector/acceptor with colocated brokers.  Stick with the netty-connector/acceptor configuration and you should be fine.

[wwang2016]

The reason I was trying to simplify the configuration is due to two receptors (http-connector and netty-connector) and two acceptors (http-acceptor and netty-acceptor).

Do I still need to configure http-connector if I only need the netty-connector and netty-acceptor?

Thanks,

wayne

[jbertram]

Do I still need to configure http-connector if I only need the netty-connector and netty-acceptor?

If you only need the netty-connector or netty-acceptor then now, you don't need the http-connector.

[mnovak]

Hi Wayne,

Justin is right, currently collocated topology with http-connectors/http-acceptors for master and slave(this is slave from another master/slave pair) is not supported as there are issues. If you use http-connectors/http-acceptors for master and netty-connectors/netty-acceptors for slave then it should work.

But generally only netty-connectors/netty-acceptors should work for collocated topology. Could you share your config?

Thanks,

Mirek

[wwang2016]

Hi Mirek,

I did not find this issue in a Virtualbox environment where I configured multiple VM with different IP addresses. Everything worked fine with only http-connector. I was almost ready to wrap up my project, and found the issue when I re-tested the http-connector only configuration in windows.

Basically, I switch back the configuration from using http-connector to netty-connector, then it worked fine in windows again (it worked in VMs too). I then remove all the definition about http-connector, and it still worked fine. So this became the final configuration that worked in both windows with port offset and VM in virtualbox environment. The configuration was basically your sample configuration with the http-connector part removed.

Thank,

Wayne

[mnovak]

Hi Wayne,

good to hear you made it to work.

Thanks,

Mirek

[wwang2016]

Hi Mirek,

It was a very good start from your sample configuration. JBoss documentation was not helpful. It was not possible to do it without information sharing among us.

I am quite busy today. But I will find a time to post a detailed section of the configuration in this thread soon.

Thanks,

Wayne