Incorrect log record level (#1023)

Artur Hefczyc opened 6 years ago

We have lots of entries in Tigase logs which look like this:

2019-04-23 15:30:08.930 [ConnectionOpenThread]  ConnectionOpenThread.addAllWaiting()  WARNING: Error: creating connection for: {cert-required-domain=404.city, cid=pandion.im@404.city, ifc=[Ljava.lang.String;@28802efb, local-hostname=pandion.im, port-no=5269, remote-hostname=404.city, remote-ip=2001:41d0:2:fa3e:0:0:0:2, s2s-connection-key=S2S: null, socket=plain, srv-type=_xmpp-server._tcp, type=connect}
java.net.SocketException: Network is unreachable
	at sun.nio.ch.Net.connect0(Native Method)
	at sun.nio.ch.Net.connect(Net.java:454)
	at sun.nio.ch.Net.connect(Net.java:446)
	at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:648)
	at tigase.net.ConnectionOpenThread.addISA(ConnectionOpenThread.java:291)
	at tigase.net.ConnectionOpenThread.addPort(ConnectionOpenThread.java:311)
	at tigase.net.ConnectionOpenThread.addAllWaiting(ConnectionOpenThread.java:239)
	at tigase.net.ConnectionOpenThread.run(ConnectionOpenThread.java:208)
	at java.lang.Thread.run(Thread.java:748)

However, these are not really WARNING level events. I think these should be at most INFO or FINE.

Please change the log level for these records.

Related
- ClassNotFoundException: tigase.monitor.tasks.LoggerMonitorEvent (#1018) Closed

Activities

Andrzej Wójcik (Tigase) commented 6 years ago

@wojtek Wasn't is solved by #tigaseim-78? I see that this tasks reports exactly the same issue...
Wojciech Kapcia (Tigase) commented 6 years ago

Seems so, closing
Login to comment

Type	Bug
Priority	Normal
Assignee	Andrzej Wójcik (Tigase)
Spent time	0
Subsystem	s2s

Issue Votes (0)

Watchers (0)

Reference

tigase/_server/server-core#1023