Throwable in cluster mode

Julia Zashchitina
Added about 4 years ago


We are running tigase 7.0.0 in cluster mode. We ran tests on local environment and on amazon ec2, with one cluster node and using several cluster nodes. In all test cases we have the following error in logs:

2015-03-17 16:44:16.081 [pool-18-thread-3]  S2SAbstractProcessor.generateStreamError()  FINEST: Called from: 
    at tigase.server.xmppserver.proc.S2SAbstractProcessor.generateStreamError(
    at tigase.server.xmppserver.proc.StreamOpen.streamOpened(
    at tigase.server.xmppserver.S2SConnectionManager.xmppStreamOpened(
    at tigase.server.xmppserver.S2SConnectionManager.xmppStreamOpened(
    at tigase.xmpp.XMPPIOService.xmppStreamOpened(
    at tigase.xmpp.XMPPDomBuilderHandler.startElement(
    at tigase.xml.SimpleParser.parse(
    at tigase.xmpp.XMPPIOService.processSocketData(
    at java.util.concurrent.Executors$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$

Could you please suggest what's wrong and how to fix it? You can see and more detailed log in the attachment. Thanks in advance.

Replies (3)

Added by Wojciech Kapcia TigaseTeam about 4 years ago

You have configured Tigase to use domain as virtual-host, and it looks like you are trying to connect to ubuntu14 domain, which results in host-unknown error.

2015-03-17 16:44:16.081 [pool-18-thread-3]  S2SConnectionManager.xmppStreamOpened()  FINER: CID: null, null, type: accept, Socket: nullSocket[addr=/,port=60661,localport=5269], jid: null, Stream opened: {to=ubuntu14, xmlns:stream=, from=DOMAIN, xmlns=jabber:server, xmlns:db=jabber:server:dialback, version=1.0}
2015-03-17 16:44:16.082 [pool-18-thread-3]  S2SAbstractProcessor.generateStreamError()  FINEST: CID: null, null, type: accept, Socket: nullSocket[addr=/,port=60661,localport=5269], jid: null, Sending stream error: <stream:error><host-unknown xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></stream:error></stream:stream>

Added by Igor Khomenko about 4 years ago

Looks like I got the same issue here

But in my case I don't use --cluster-mode = true and looks like Tigase is trying to connect it itself. How it can be?


Added by Artur Hefczyc TigaseTeam about 4 years ago

Igor, this is usually a result of misconfiguration on the network layer, in particular the hostname and DNS area.