Feed aggregator

API and development: RE: Connection time optimizations

Tigase XMPP Server Board - Fri, 02/05/2016 - 08:35

I have found that Smack Java client deals with it in a different way

https://igniterealtime.org/issues/browse/SMACK-622

they use this document http://tools.ietf.org/html/draft-cridland-xmpp-session-01
with 'optional' marker.

do you have any view on it?

Categories: Tigase Forums

Installation and maintenance: RE: No extra certificates

Tigase XMPP Server Board - Thu, 02/04/2016 - 10:16

Tigase can generate it's own pem certificates which will be in the /certs folder of the installation directory. You may use your own in pem format if you wish put in that directory. Alternatively, you may load certificates using a REST command.

Have a look through this section http://docs.tigase.org/tigase-server/snapshot/Administration_Guide/html/#ServerCertificates as well to get you started.

Categories: Tigase Forums

Installation and maintenance: No extra certificates

Tigase XMPP Server Board - Thu, 02/04/2016 - 09:32

Hi,
Can you tell where to tune exactly which certificates (SSL) uses a server at connection setup.
Thank you

Categories: Tigase Forums

API and development: RE: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 07:28

ha ha ha!!!! DOH :-)

Categories: Tigase Forums

API and development: RE: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 07:27

you have:
ws22s/watchdog_ping_type[S]=xmpp

there is no ws22s but ws2s ;-)

Categories: Tigase Forums

API and development: RE: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 07:25

I've set it like this, and my TCP client gets XMPP ping, but my WS client gets whitespaces.. hmmmm

@c2s/watchdog_delay[L]=60000
c2s/watchdog_timeout[L]=60000
c2s/watchdog_ping_type[S]=xmpp

ws2s/watchdog_delay[L]=60000
ws2s/watchdog_timeout[L]=60000
ws22s/watchdog_ping_type[S]=xmpp@

Categories: Tigase Forums

API and development: RE: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 07:03

Okie dokie. I just tested it and it seems to work.. The fun part of it is that its sending whitespace ping to the WS client instead of XMPP pings (which I receive on the TCP client).

Categories: Tigase Forums

API and development: RE: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 07:01

While ws2s is similar to c2s (and it extends it implementation wise) it's still a separate component with all what it entails - among which is separate configuration :-)

Categories: Tigase Forums

API and development: RE: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 06:56

Hi W,

Thanks for your fast reply! :-)
Yes I knew that it was a bit unnecessary for BOSH as I wrote, but should c2s also apply for WS streams? or does it not count as real socket connections?..
I'll add both to the property file.

Categories: Tigase Forums

API and development: RE: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 06:49

If you prefix property with "c2s/" it applies only to regular socket connections. You can either configure watchdog separately for ws2s/. Also - watchdog is disabled for BOSH as it doesn't make sense to check those connections using watchdog - appropriate checking is inherent in BOSH itself.

Categories: Tigase Forums

API and development: WebSocket / BOSH ping problem

Tigase XMPP Server Board - Thu, 02/04/2016 - 06:42

Hi,

I have a strange problem, in the way I get pings to the different clients.
I have several client which have different transports - some are running BOSH, some WS (WebSockets) and some normal TCP.

My properties for ping is like so:

c2s/watchdog_delay[L]=60000
c2s/watchdog_timeout[L]=60000
c2s/watchdog_ping_type[S]=xmpp

So for TCP I receive the ping and can answer back with a pong - but for WS I do not receive such a IQ stanza. So it gets terminated after my watchdog timeout.
The same for BOSH, but I believe that BOSH does not need such a ping feature since its request/response model.

My WS is setup like so:

--comp-class-1 = tigase.server.websocket.WebSocketClientConnectionManager
--comp-name-1 = ws2s
ws2s/connections/ports[i]=5290,5291
ws2s/connections/5291/socket=ssl
ws2s/connections/5291/type=accept

I can se that I am present with all my clients.. so they should receive a ping like the TCP one.
Stream management is enabled (XEP-0198) and I am running Tigase server 7.0.2-b3821/563fcf81 (in single node mode - no cluster and directly on the server).

-Cheers!

/Steffen

Categories: Tigase Forums

API and development: RE: Tigase 7.x REST API problems

Tigase XMPP Server Board - Thu, 02/04/2016 - 06:31

Hi W,

Sorry about the slow reply - I totally forgot this outstanding.
Yes you are correct. I can disable it by removing the wars, which is fine.

Categories: Tigase Forums

Installation and maintenance: RE: Cluster Configuration Not Working

Tigase XMPP Server Board - Thu, 02/04/2016 - 03:51

Yes both time and timezone are same. When single node running, it says connection refused with other node. I setup a default tigase and tried it again.

With default config (without --cluster-nodes=), there is no sign of other node in the log. I have following warning for same node,
Config
--comp-class-1 = tigase.muc.MUCComponent
--virt-hosts = im.domain
--user-db-uri = xxxxxxxxxxxxxxxxx
--user-db = mysql
--admins =
--comp-name-4 = message-archive
--comp-name-3 = proxy
config-type = --gen-config-def
--comp-name-2 = pubsub
--comp-name-1 = muc
--cluster-mode = true
--sm-plugins = +message-archive-xep-0136
--debug = server
--comp-class-4 = tigase.archive.MessageArchiveComponent
--comp-class-3 = tigase.socks5.Socks5ProxyComponent
--comp-class-2 = tigase.pubsub.PubSubComponent

LOG
2016-02-04 19:43:00.557 [main] ClusterConnectionManager.itemAdded() WARNING: Incorrect ClusterRepoItem, skipping connection attempt: ip-10-0-1-16.ap-southeast-1.compute.internal:07f1d104c8bc9b1a892cf2dd1d52e5a4fdddb4d76a97a02d80b0aa074520c78c:5277:0:0.0:0.0

[ec2-user@ip-10-0-1-16 ~]$ hostname
ip-10-0-1-16.ap-southeast-1.compute.internal

When i add --cluster-nodes= in the config, getting NullPointerException as below
Config
--cluster-nodes= ip-10-0-1-16.ap-southeast-1.compute.internal,ip-10-0-2-17.ap-southeast-1.compute.internal
(or)
--cluster-nodes=ip-10-0-1-16.ap-southeast-1.compute.internal:00e649c8de086c1d4c381b90e7eb290e5b34a2b09c2bbe0560592b953c1f787d:5277,ip-10-0-2-17.ap-southeast-1.compute.internal:256aa5f455e08a7c2a030dd0fc5ad2e731d93e2655062b58455ea6491410f1a1:5277

LOG :
2016-02-04 19:38:21.779 [pool-15-thread-9] ClusterConnectionManager.xmppStreamOpened() INFO: Stream opened: {id=ed631115-96c1-48de-a700-52635eff650b, to=ip-10-0-1-16.ap-southeast-1.compute.internal, xmlns:stream=http://etherx.jabber.org/streams, from=ip-10-0-2-17.ap-southeast-1.compute.internal, xmlns=tigase:cluster}, service: null, type: connect, Socket: nullSocket[addr=ip-10-0-2-17.ap-southeast-1.compute.internal/10.0.2.17,port=5277,localport=46064], jid: null
2016-02-04 19:38:21.780 [pool-15-thread-9] XMPPIOService.processSocketData() INFO: null, type: connect, Socket: nullSocket[addr=ip-10-0-2-17.ap-southeast-1.compute.internal/10.0.2.17,port=5277,localport=46064], jid: null, Incorrect XML data: <stream:stream xmlns='tigase:cluster' xmlns:stream='http://etherx.jabber.org/streams' from='ip-10-0-2-17.ap-southeast-1.compute.internal' to='ip-10-0-1-16.ap-southeast-1.compute.internal' id='ed631115-96c1-48de-a700-52635eff650b'>, stopping connection: null, exception:
java.lang.NullPointerException
at tigase.cluster.ClusterConnectionManager.xmppStreamOpened(ClusterConnectionManager.java:573)
at tigase.xmpp.XMPPIOService.xmppStreamOpened(XMPPIOService.java:801)
at tigase.xmpp.XMPPDomBuilderHandler.startElement(XMPPDomBuilderHandler.java:280)
at tigase.xml.SimpleParser.parse(SimpleParser.java:314)
at tigase.xmpp.XMPPIOService.processSocketData(XMPPIOService.java:686)
at tigase.net.IOService.call(IOService.java:252)
at tigase.net.IOService.call(IOService.java:94)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
2016-02-04 19:38:21.780 [pool-15-thread-9] ConnectionManager.serviceStopped() FINER: cl-comp Connection stopped: null, type: connect, Socket: nullSocket[unconnected], jid: null

Categories: Tigase Forums

Installation and maintenance: RE: Cluster Configuration Not Working

Tigase XMPP Server Board - Thu, 02/04/2016 - 02:58

Are the times on both machines synchronised and in the same timezone? Can you check all the logs for the informations about reloading cluster nodes configuration (ideally with removed --cluster-nodes= entry). Does the entries in cluster_nodes show up when only single node is running?

Categories: Tigase Forums

Installation and maintenance: RE: Users not seems in database when create user using Spark Client...

Tigase XMPP Server Board - Thu, 02/04/2016 - 02:43

Server configuration is described in the documentation - Tigase XMPP Server init.properties Configuration.

Mentioned changes should be done in etc/init.properties file in which you have line --sm-plugins=+message-archive-xep-0136,-jabber:iq:auth,-urn:ietf:params…. You should modify this line and put a # at the beginning. or remove this line completely

Categories: Tigase Forums

Installation and maintenance: RE: hostname requirements

Tigase XMPP Server Board - Thu, 02/04/2016 - 02:38

robert davis wrote:

Thus, the requirement would be the system hostname must resolve in DNS and of course be unique. Not that the hostname=FQDN.

Furthermore, if every node FQDN is defined in each node's /etc/hosts and /etc/nsswitch.conf is set to hosts: files then you wouldn't need the box registered in DNS, correct?

Left relevant parts - yes, it has to be unique and then given hostname has to resolve correctly to the cluster nodes so if you set the hostname of the machine and then configure resolving on other machines (using /etc/hosts) to correct IPs then it will work just fine.

Please keep in mind and check in Tigase logs (logs/tigase-console.log) the hostname that Tigase picked up.

Categories: Tigase Forums

Installation and maintenance: RE: Cluster Configuration Not Working

Tigase XMPP Server Board - Thu, 02/04/2016 - 02:08

Additional Info : connection and hostname seems don't have any issue.

Debug Info :

[ec2-user@ip-10-0-1-16 ~]$ hostname ip-10-0-1-16.ap-southeast-1.compute.internal [ec2-user@ip-10-0-1-16 ~]$ telnet ip-10-0-2-17.ap-southeast-1.compute.internal 5277 Trying 10.0.2.17... Connected to ip-10-0-2-17.ap-southeast-1.compute.internal. Escape character is '^]'. ^CConnection closed by foreign host. [ec2-user@ip-10-0-2-17 ~]$ hostname ip-10-0-2-17.ap-southeast-1.compute.internal [ec2-user@ip-10-0-2-17 ~]$ telnet ip-10-0-1-16.ap-southeast-1.compute.internal 5277 Trying 10.0.1.16... Connected to ip-10-0-1-16.ap-southeast-1.compute.internal. Escape character is '^]'. ^CConnection closed by foreign host. [ec2-user@ip-10-0-1-16 ~]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.0.1.16 ip-10-0-1-16.ap-southeast-1.compute.internal 10.0.2.17 ip-10-0-2-17.ap-southeast-1.compute.internal [ec2-user@ip-10-0-2-17 ~]$ cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.0.1.16 ip-10-0-1-16.ap-southeast-1.compute.internal 10.0.2.17 ip-10-0-2-17.ap-southeast-1.compute.internal
Categories: Tigase Forums

Installation and maintenance: Cluster Configuration Not Working

Tigase XMPP Server Board - Thu, 02/04/2016 - 02:00

Our current cluster configuration works perfectly. We are trying to setup tigase in a new environment (in aws), tigase works but cluster nodes are not recognised. cluster_nodes are empty, PSI service discovery doesn't return any cluster nodes. I have attached our configuration and log below. Please advice. We use tigase 7.0.0.

init.properties :

config-type = --gen-config-def --virt-hosts = im.domain --user-db-uri = xxxxxxxxxxxxxxxx --user-db = mysql --admins = admin@im.domain --cluster-mode = true --cluster-nodes= ip-10-0-1-16.ap-southeast-1.compute.internal,ip-10-0-2-17.ap-southeast-1.compute.internal #(Note : When I remove this line, auto discovery also not working) --max-queue-size= 500000 --sm-plugins=+urn:xmpp:sm:3,-presence,+message-archive-xep-0136,+jabber:iq:auth,+urn:ietf:params:xml:ns:xmpp-sasl,+urn:ietf:params:xml:ns:xmpp-bind,+urn:ietf:params:xml:ns:xmpp-session,+jabber:iq:register,-jabber:iq:roster,+roster-presence,+jabber:iq:privacy,+jabber:iq:version,+http://jabber.org/protocol/stats,+starttls,+vcard-temp,+http://jabber.org/protocol/commands,+jabber:iq:private,-basic-filter,-domain-filter,-pep,-zlib,+jabber:iq:last --debug=server,cluster --comp-name-6 = http --comp-name-5 = push --comp-name-4 = pubsub --comp-name-3 = message-archive --comp-name-2 = proxy --comp-name-1 = ext --comp-class-1 = tigase.server.ext.ComponentProtocol --external=muc.im.domain:tigase:listen:5270 --comp-class-3 = tigase.archive.MessageArchiveComponent --comp-class-2 = tigase.socks5.Socks5ProxyComponent --comp-class-4 = tigase.pubsub.PubSubComponent --comp-class-5 = com.ncs.onechat.PushComponent --comp-class-6 = tigase.http.HttpMessageReceiver

LOG (10.0.1.16) :

2016-02-04 17:25:32.560 [scheduler_pool-5-thread-1-cl-comp] ConnectionManager$1.run() FINE: Reconnecting service for component: cl-comp, to remote host: ip-10-0-2-17.ap-southeast-1.compute.internal on port: 5277 2016-02-04 17:25:32.560 [scheduler_pool-5-thread-1-cl-comp] ConnectionManager$1.run() FINE: Reconnecting service for component: cl-comp, to remote host: ip-10-0-2-17.ap-southeast-1.compute.internal on port: 5277 2016-02-04 17:25:32.562 [ConnectionOpenThread] ConnectionManager$ConnectionListenerImpl.accept() FINEST: Accept called for service: null@null, port_props: {socket=plain, port-no=5277, service-connected-task-future=tigase.cluster.ClusterConnectionManager$ServiceConnectedTimerTask@2f9bc4ca, remote-host=ip-10-0-2-17.ap-southeast-1.compute.internal, routing-table=[Ljava.lang.String;@1b94c231, sessionID=7a079e53-d2af-4435-80e2-39ba0894b917, local-host=ip-10-0-1-16.ap-southeast-1.compute.internal, secret=5afd0245d0884704b987d31d6c324feec661b6bd7972fb6ee7283348be305802, hostname-key=ip-10-0-2-17.ap-southeast-1.compute.internal, ifc=[Ljava.lang.String;@28688f7b, type=connect, max-reconnects=99999999} 2016-02-04 17:25:32.604 [ConnectionOpenThread] ConnectionManager.serviceStarted() FINER: [[cl-comp]] Connection started: null, type: connect, Socket: nullSocket[addr=ip-10-0-2-17.ap-southeast-1.compute.internal/10.0.2.17,port=5277,localport=33149], jid: null 2016-02-04 17:25:32.604 [ConnectionOpenThread] ClusterConnectionManager.serviceStarted() INFO: cluster connection opened: 10.0.2.17, type: connect, id=10.0.1.16_33149_10.0.2.17_5277 2016-02-04 17:25:32.604 [ConnectionOpenThread] ClusterConnectionManager.serviceStarted() INFO: cid: null, sending: <stream:stream xmlns='tigase:cluster' xmlns:stream='http://etherx.jabber.org/streams' from='ip-10-0-1-16.ap-southeast-1.compute.internal' to='ip-10-0-2-17.ap-southeast-1.compute.internal'> 2016-02-04 17:25:32.604 [ConnectionOpenThread] ConnectionManager$ConnectionListenerImpl.accept() FINEST: Accept called for service: null@null, port_props: {socket=plain, port-no=5277, service-connected-task-future=tigase.cluster.ClusterConnectionManager$ServiceConnectedTimerTask@13a0abcf, remote-host=ip-10-0-2-17.ap-southeast-1.compute.internal, routing-table=[Ljava.lang.String;@196fad1a, sessionID=0e30a0bb-000e-4c51-b5b2-282e968bdf1e, local-host=ip-10-0-1-16.ap-southeast-1.compute.internal, secret=5afd0245d0884704b987d31d6c324feec661b6bd7972fb6ee7283348be305802, hostname-key=ip-10-0-2-17.ap-southeast-1.compute.internal, ifc=[Ljava.lang.String;@454d6695, type=connect, max-reconnects=99999999} 2016-02-04 17:25:32.605 [ConnectionOpenThread] ClConSQLRepository.reload() FINEST: Last reload performed in 43, skipping: 2016-02-04 17:25:32.605 [ConnectionOpenThread] ConnectionManager.serviceStarted() FINER: [[cl-comp]] Connection started: null, type: connect, Socket: nullSocket[addr=ip-10-0-2-17.ap-southeast-1.compute.internal/10.0.2.17,port=5277,localport=33150], jid: null 2016-02-04 17:25:32.605 [ConnectionOpenThread] ClusterConnectionManager.serviceStarted() INFO: cluster connection opened: 10.0.2.17, type: connect, id=10.0.1.16_33150_10.0.2.17_5277 2016-02-04 17:25:32.605 [ConnectionOpenThread] ClusterConnectionManager.serviceStarted() INFO: cid: null, sending: <stream:stream xmlns='tigase:cluster' xmlns:stream='http://etherx.jabber.org/streams' from='ip-10-0-1-16.ap-southeast-1.compute.internal' to='ip-10-0-2-17.ap-southeast-1.compute.internal'> 2016-02-04 17:25:32.605 [ConnectionOpenThread] ConnectionManager$ConnectionListenerImpl.accept() FINEST: Accept called for service: null@null, port_props: {type=accept, socket=plain, ifc=[Ljava.lang.String;@e8fb7a8, remote-host=localhost, required=false, port-no=5277} 2016-02-04 17:25:32.605 [ConnectionOpenThread] ClConSQLRepository.reload() FINEST: Last reload performed in 43, skipping: 2016-02-04 17:25:32.605 [ConnectionOpenThread] ConnectionManager.serviceStarted() FINER: [[cl-comp]] Connection started: null, type: accept, Socket: nullSocket[addr=/10.0.2.17,port=49058,localport=5277], jid: null 2016-02-04 17:25:32.605 [ConnectionOpenThread] ClusterConnectionManager.serviceStarted() INFO: cluster connection opened: 10.0.2.17, type: accept, id=10.0.1.16_5277_10.0.2.17_49058 2016-02-04 17:25:32.605 [ConnectionOpenThread] ConnectionManager$ConnectionListenerImpl.accept() FINEST: Accept called for service: null@null, port_props: {type=accept, socket=plain, ifc=[Ljava.lang.String;@e8fb7a8, remote-host=localhost, required=false, port-no=5277} 2016-02-04 17:25:32.605 [ConnectionOpenThread] ClConSQLRepository.reload() FINEST: Last reload performed in 43, skipping: 2016-02-04 17:25:32.606 [ConnectionOpenThread] ConnectionManager.serviceStarted() FINER: [[cl-comp]] Connection started: null, type: accept, Socket: nullSocket[addr=/10.0.2.17,port=49059,localport=5277], jid: null 2016-02-04 17:25:32.606 [ConnectionOpenThread] ClusterConnectionManager.serviceStarted() INFO: cluster connection opened: 10.0.2.17, type: accept, id=10.0.1.16_5277_10.0.2.17_49059 2016-02-04 17:25:32.625 [pool-18-thread-9] ClusterConnectionManager.xmppStreamOpened() INFO: Stream opened: {to=ip-10-0-1-16.ap-southeast-1.compute.internal, xmlns:stream=http://etherx.jabber.org/streams, from=ip-10-0-2-17.ap-southeast-1.compute.internal, xmlns=tigase:cluster}, service: null, type: accept, Socket: nullSocket[addr=/10.0.2.17,port=49058,localport=5277], jid: null 2016-02-04 17:25:32.625 [pool-18-thread-9] ClusterConnectionManager.updateConnectionDetails() FINEST: ClusterRepoItem: null, port_props: {port-no=5277, socket=plain, service-connected-task-future=tigase.cluster.ClusterConnectionManager$ServiceConnectedTimerTask@42a1b124, remote-host=ip-10-0-2-17.ap-southeast-1.compute.internal, routing-table=[Ljava.lang.String;@574d4a9, sessionID=91a674f9-863f-41bd-8d4b-f9b42870c94d, hostname-key=ip-10-0-2-17.ap-southeast-1.compute.internal, ifc=[Ljava.lang.String;@e8fb7a8, type=accept, required=false, max-reconnects=0} 2016-02-04 17:25:32.626 [pool-18-thread-2] ClusterConnectionManager.xmppStreamOpened() INFO: Stream opened: {to=ip-10-0-1-16.ap-southeast-1.compute.internal, xmlns:stream=http://etherx.jabber.org/streams, from=ip-10-0-2-17.ap-southeast-1.compute.internal, xmlns=tigase:cluster}, service: null, type: accept, Socket: nullSocket[addr=/10.0.2.17,port=49059,localport=5277], jid: null 2016-02-04 17:25:32.626 [pool-18-thread-2] ClusterConnectionManager.updateConnectionDetails() FINEST: ClusterRepoItem: null, port_props: {port-no=5277, socket=plain, service-connected-task-future=tigase.cluster.ClusterConnectionManager$ServiceConnectedTimerTask@71283984, remote-host=ip-10-0-2-17.ap-southeast-1.compute.internal, routing-table=[Ljava.lang.String;@7d84326, sessionID=a56a56c8-5314-4acf-8625-5693c7349897, hostname-key=ip-10-0-2-17.ap-southeast-1.compute.internal, ifc=[Ljava.lang.String;@e8fb7a8, type=accept, required=false, max-reconnects=0} 2016-02-04 17:25:32.627 [pool-18-thread-6] ConnectionManager.serviceStopped() FINER: [[cl-comp]] Connection stopped: null, type: accept, Socket: nullSocket[unconnected], jid: null 2016-02-04 17:25:32.627 [pool-18-thread-6] ClusterConnectionManager.serviceStopped() FINEST: serviceStopped: result=true / size=0 / connPool={ip-10-0-2-17.ap-southeast-1.compute.internal=[]} / serv=null, type: accept, Socket: nullSocket[unconnected], jid: null / conns=[] / type=accept 2016-02-04 17:25:32.627 [pool-18-thread-4] ClusterConnectionManager.xmppStreamOpened() INFO: Stream opened: {id=1607f9af-4556-4cd9-8895-fd4f236c8357, to=ip-10-0-1-16.ap-southeast-1.compute.internal, xmlns:stream=http://etherx.jabber.org/streams, from=ip-10-0-2-17.ap-southeast-1.compute.internal, xmlns=tigase:cluster}, service: null, type: connect, Socket: nullSocket[addr=ip-10-0-2-17.ap-southeast-1.compute.internal/10.0.2.17,port=5277,localport=33149], jid: null 2016-02-04 17:25:32.627 [pool-18-thread-4] ConnectionManager.serviceStopped() FINER: [[cl-comp]] Connection stopped: null, type: connect, Socket: nullSocket[unconnected], jid: null 2016-02-04 17:25:32.627 [pool-18-thread-4] ClusterConnectionManager.serviceStopped() FINEST: serviceStopped: result=true / size=0 / connPool={ip-10-0-2-17.ap-southeast-1.compute.internal=[]} / serv=null, type: connect, Socket: nullSocket[unconnected], jid: null / conns=[] / type=connect 2016-02-04 17:25:32.627 [pool-18-thread-4] ConnectionManager.reconnectService() FINER: Reconnecting service for: cl-comp, scheduling next try in 5secs, cid: null@null, props: {port-no=5277, socket=plain, service-connected-task-future=tigase.cluster.ClusterConnectionManager$ServiceConnectedTimerTask@6499fc57, remote-host=ip-10-0-2-17.ap-southeast-1.compute.internal, routing-table=[Ljava.lang.String;@3985e75a, sessionID=1607f9af-4556-4cd9-8895-fd4f236c8357, local-host=ip-10-0-1-16.ap-southeast-1.compute.internal, secret=5afd0245d0884704b987d31d6c324feec661b6bd7972fb6ee7283348be305802, hostname-key=ip-10-0-2-17.ap-southeast-1.compute.internal, ifc=[Ljava.lang.String;@28688f7b, type=connect, max-reconnects=99999999} 2016-02-04 17:25:32.628 [pool-18-thread-5] ClusterConnectionManager.xmppStreamOpened() INFO: Stream opened: {id=4c72de96-b70e-4691-bc38-da4e097dd64f, to=ip-10-0-1-16.ap-southeast-1.compute.internal, xmlns:stream=http://etherx.jabber.org/streams, from=ip-10-0-2-17.ap-southeast-1.compute.internal, xmlns=tigase:cluster}, service: null, type: connect, Socket: nullSocket[addr=ip-10-0-2-17.ap-southeast-1.compute.internal/10.0.2.17,port=5277,localport=33150], jid: null 2016-02-04 17:25:32.628 [pool-18-thread-7] ConnectionManager.serviceStopped() FINER: [[cl-comp]] Connection stopped: null, type: accept, Socket: nullSocket[unconnected], jid: null 2016-02-04 17:25:32.628 [pool-18-thread-7] ClusterConnectionManager.serviceStopped() FINEST: serviceStopped: result=true / size=0 / connPool={ip-10-0-2-17.ap-southeast-1.compute.internal=[]} / serv=null, type: accept, Socket: nullSocket[unconnected], jid: null / conns=[] / type=accept 2016-02-04 17:25:32.628 [pool-18-thread-5] ConnectionManager.serviceStopped() FINER: [[cl-comp]] Connection stopped: null, type: connect, Socket: nullSocket[unconnected], jid: null 2016-02-04 17:25:32.628 [pool-18-thread-5] ClusterConnectionManager.serviceStopped() FINEST: serviceStopped: result=true / size=0 / connPool={ip-10-0-2-17.ap-southeast-1.compute.internal=[]} / serv=null, type: connect, Socket: nullSocket[unconnected], jid: null / conns=[] / type=connect 2016-02-04 17:25:32.628 [pool-18-thread-5] ConnectionManager.reconnectService() FINER: Reconnecting service for: cl-comp, scheduling next try in 5secs, cid: null@null, props: {port-no=5277, socket=plain, service-connected-task-future=tigase.cluster.ClusterConnectionManager$ServiceConnectedTimerTask@617e337, remote-host=ip-10-0-2-17.ap-southeast-1.compute.internal, routing-table=[Ljava.lang.String;@a463301, sessionID=4c72de96-b70e-4691-bc38-da4e097dd64f, local-host=ip-10-0-1-16.ap-southeast-1.compute.internal, secret=5afd0245d0884704b987d31d6c324feec661b6bd7972fb6ee7283348be305802, hostname-key=ip-10-0-2-17.ap-southeast-1.compute.internal, ifc=[Ljava.lang.String;@454d6695, type=connect, max-reconnects=99999999}
Categories: Tigase Forums

Installation and maintenance: RE: Users not seems in database when create user using Spark Client...

Tigase XMPP Server Board - Thu, 02/04/2016 - 00:06

It would be really better for me if you can give some guideline for what to comment/disable in which files as i'm not much aware about this process.

It will be really surely appreciable.

Categories: Tigase Forums

Pages

Get in touch

We provide software products, consulting and custom development services

Tigase, Inc.
100 Pine Street, Suite 1250
San Francisco, CA 94111, USA
Phone: (415) 315 9771

Follow us on:

Twitter

Back to Top