How did you start the server (were you restarting)?

I don't know if the server works anyway correctly in this situation

The server itself should work just fine, but it wouldn't be accessible on the problematic port. You can execute lsof -iTCP -sTCP:LISTEN -Pn to see which ports are being listened on.

I just shut down the server and restarted after some minutes, usually it works, when it happened I have executed:

# netstat -ltpn | grep 5280

but no results was given, that why I have assumed some kind of race condition in tigase setup binding

Could you share your complete (obfuscated) config.tdsl? Do you have any connection-manager/port configuration there?

excerpts from the config:

bosh {
    seeOtherHost (class: none) {}
}
c2s {
    connections {
        5222 {
            'new-connections-throttling' = 2000L
        }
    }
    seeOtherHost (class: none) {}
    'urn:xmpp:sm:3' () {
        active = true
    }
}
ws2s {
    connections {
        ports = [ 5290, 5291 ]
        5291 {
            socket = 'ssl'
            type = 'accept'
        }
    }
    seeOtherHost (class: none) {}
    'urn:xmpp:sm:3' {
        active = true
    }
}

@hantu85 do you think that reconfiguring CM beans to apply the configuration could cause such behaviour?

Yes, it could as port 5291 is listed "twice", once in the ports property and also in as a separate entry.

I would suggest to change this part of the config to look like the following one:

bosh {
    seeOtherHost (class: none) {}
}
c2s {
    connections {
        5222 {
            'new-connections-throttling' = 2000L
        }
    }
    seeOtherHost (class: none) {}
    'urn:xmpp:sm:3' () {
        active = true
    }
}
ws2s {
    connections {
        5291 () {
            socket = 'ssl'
            type = 'accept'
        }
    }
    seeOtherHost (class: none) {}
    'urn:xmpp:sm:3' {
        active = true
    }
}

We can skip ports section as port 5290 is enabled by default and we want just to enable and configure port 5291.

One thing - original exception was related to port 5280 (i.e. bosh), which doesn't list ports and only have specific see-other-host configuration.

Then it should not cause such behaviour.