Messages in the log files that leave me stumped (novice)

Openfire Openfire Support
1

All,

I am a bit of a novice with Wildfire/spark and this is my first Jabber/XMPP experience outside of google talk.

I have Wildfire 3.0.1 and Spark clients 2.0.1.

I have the server tied in using AD for group and auth membership, as well as vCard.

Using the internal database connector, as I had lil luck with MSSQL.

My question relates to messages I see in my error log and warning logs.

Error Log:

2006.09.12 15:09:01

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=3016,localport=5269]

2006.09.12 15:09:01

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=3017,localport=5269]

2006.09.12 18:10:20

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.12 22:04:06

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.13 08:21:58

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.13 08:35:25

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.13 08:35:29

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=4985,localport=5269]

2006.09.13 08:35:29

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=4982,localport=5269]

2006.09.13 08:44:46

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1195,localport=5269]

2006.09.13 08:44:46

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1196,localport=5269]

2006.09.13 08:58:19

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.13 08:58:25

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1202,localport=5269]

2006.09.13 08:58:25

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1203,localport=5269]

2006.09.13 09:35:58

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.13 09:36:04

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1230,localport=5269]

2006.09.13 09:36:04

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1231,localport=5269]

2006.09.13 10:12:34

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.13 10:12:37

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1258,localport=5269]

2006.09.13 10:12:37

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1259,localport=5269]

2006.09.13 10:14:24

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

2006.09.13 10:47:21

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1278,localport=5269]

2006.09.13 10:47:21

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1279,localport=5269]

2006.09.13 10:56:10

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1284,localport=5269]

2006.09.13 10:56:10

[

|org.jivesoftware.wildfire.net.BlockingReadingMode.run(BlockingReadingMode.java: 104)]Connection closed before session established

Socket[http://addr=/161.221.128.142,port=1285,localport=5269]

2006.09.13 11:40:35

[

|org.jivesoftware.wildfire.roster.Roster.<init>(Roster.java:161)]Groups () include non-existent username (cn=nttest,cn=users,dc=hq,dc=bn-corp,dc=com)

Warning log:

2006.09.12 15:09:01 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@f32dde socket: Socket[http://addr=/161.221.128.142,port=3016,localport=5269] session: null

2006.09.13 08:35:29 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@ff87dc socket: Socket[http://addr=/161.221.128.142,port=4982,localport=5269] session: null

2006.09.13 08:44:46 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@1fa1ba1 socket: Socket[http://addr=/161.221.128.142,port=1195,localport=5269] session: null

2006.09.13 08:58:25 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@16f8789 socket: Socket[http://addr=/161.221.128.142,port=1202,localport=5269] session: null

2006.09.13 09:36:04 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@7ae165 socket: Socket[http://addr=/161.221.128.142,port=1230,localport=5269] session: null

2006.09.13 10:12:37 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@be6858 socket: Socket[http://addr=/161.221.128.142,port=1258,localport=5269] session: null

2006.09.13 10:47:21 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@e2bc8d socket: Socket[http://addr=/161.221.128.142,port=1278,localport=5269] session: null

2006.09.13 10:56:10 Closing session due to incorrect hostname in stream header. Host: wse. Connection: org.jivesoftware.wildfire.net.SocketConnection@ee5d13 socket: Socket[http://addr=/161.221.128.142,port=1284,localport=5269] session: null

Any help in understanding these messages and how to satify them so they dont appear.

Thanks in advance

2

Hi WVK,

Does your problem happens to be similar to what has been discussed here? There is a potential cause of connection loops if the DNS/host lookup and the xmpp.domain of your Wildfire are configured in certain ways. The loops is normally triggered by the connecting clients. Besides xmpp.domain and DNS, there are several other things you might want to check. In Spark login screen, you’‘ll have to make sure that the “Server:” box is exactly the xmpp.domain. If that doesn’'t help, maybe changing some options when you click the “Advanced” button could give you some hints.

Hope that helps.

3

Thank you for your insight. I have tested it using the FQDN to the wildfire server and it appears to have fixed the issue. I had my clients using the shortname to the server, instead of the long FQDN.

I will let you know if I have any further issue.

Thanks