9:40 p.m.
Hi!
I can't find workaround for my problem.
I am configuring JBoss cluster in Domian mode. I have One domain
controller host and Three Slave hosts. All hosts are running on Centos
6.4 64bit.
Now I need to add one more JBoss Slave instance, but running on Ubuntu.
And I have the following issue:
When starting JBoss trying to connect to controller and connection
fails. After 5 attempts JBoss stops:
14:17:37,832 INFO [org.jboss.modules] (main) JBoss Modules version
1.2.0.Final-redhat-1
14:17:37,900 INFO [org.jboss.as.process.Host Controller.status] (main)
JBAS012017: Starting process 'Host Controller'
[Host Controller] 14:17:38,349 INFO [org.jboss.modules] (main) JBoss
Modules version 1.2.0.Final-redhat-1
[Host Controller] 14:17:38,512 INFO [org.jboss.msc] (main) JBoss MSC
version 1.0.4.GA-redhat-1
[Host Controller] 14:17:38,574 INFO [org.jboss.as] (MSC service thread
1-6) JBAS015899: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) starting
[Host Controller] 14:17:39,042 INFO [org.xnio] (MSC service thread 1-2)
XNIO Version 3.0.7.GA-redhat-1
[Host Controller] 14:17:39,051 INFO [org.xnio.nio] (MSC service thread
1-2) XNIO NIO Implementation Version 3.0.7.GA-redhat-1
[Host Controller] 14:17:39,067 INFO [org.jboss.remoting] (MSC service
thread 1-2) JBoss Remoting version 3.2.16.GA-redhat-1
[Host Controller] 14:17:39,123 INFO [org.jboss.as.remoting] (MSC
service thread 1-18) JBAS017100: Listening on 192.168.0.4:19999
[Host Controller] 14:17:44,288 WARN [org.jboss.as.host.controller]
(Controller Boot Thread) JBAS010900: Could not connect to remote domain
controller 192.168.3.30:9999: java.net.ConnectException: JBAS012144:
Could not connect to remote://192.168.3.30:9999. The connection timed out
[Host Controller] 14:17:50,292 WARN [org.jboss.as.host.controller]
(Controller Boot Thread) JBAS010900: Could not connect to remote domain
controller 192.168.3.30:9999: java.net.ConnectException: JBAS012144:
Could not connect to remote://192.168.3.30:9999. The connection timed out
[Host Controller] 14:17:56,294 WARN [org.jboss.as.host.controller]
(Controller Boot Thread) JBAS010900: Could not connect to remote domain
controller 192.168.3.30:9999: java.net.ConnectException: JBAS012144:
Could not connect to remote://192.168.3.30:9999. The connection timed out
[Host Controller] 14:18:02,297 WARN [org.jboss.as.host.controller]
(Controller Boot Thread) JBAS010900: Could not connect to remote domain
controller 192.168.3.30:9999: java.net.ConnectException: JBAS012144:
Could not connect to remote://192.168.3.30:9999. The connection timed out
[Host Controller] 14:18:08,300 WARN [org.jboss.as.host.controller]
(Controller Boot Thread) JBAS010900: Could not connect to remote domain
controller 192.168.3.30:9999: java.net.ConnectException: JBAS012144:
Could not connect to remote://192.168.3.30:9999. The connection timed out
[Host Controller] 14:18:14,306 ERROR [org.jboss.as.host.controller]
(Controller Boot Thread) JBAS010901: Could not connect to master.
Aborting. Error was: java.lang.IllegalStateException: JBAS010951: Could
not connect to master in 5 attempts within 30000 ms
[Host Controller] 14:18:14,340 INFO [org.jboss.as] (MSC service thread
1-6) JBAS015950: JBoss EAP 6.1.0.GA (AS 7.2.0.Final-redhat-8) stopped in
28ms
14:18:14,676 INFO [org.jboss.as.process.Host Controller.status] (reaper
for Host Controller) JBAS012010: Process 'Host Controller' finished with
an exit status of 99
14:18:14,678 INFO [org.jboss.as.process] (Thread-8) JBAS012016:
Shutting down process controller
14:18:14,679 INFO [org.jboss.as.process] (Thread-8) JBAS012015: All
processes finished; exiting
Domain controller shows nothing. (TRACE logging mode shows plenty of
information, for example info about security key exchange and so on)
I checked and disabled iptables and selinux on all hosts. TCPDUMP tells
that hosts are communicating when JBOss trying to connect.
When starting JBoss Domain Controller on Ubuntu Host, Slave Hosts on
Centos and Ubuntu connecting without problems.
But I need to start only slave JBoss in my production environment.
I cannot figure out where the problem is? In centos or in Ubuntu?
I also tried Debian 7 host, the situation is similar to Ubuntu.
Help is appreciated! Thanks!
--
Sysadmin DCAK
mailto:kia@dcak.ru