I have a problem with connections to jabber.org. I don’‘t see anybody come online in my roster if I don’'t block connections to/from jabber.org. In the debug.log i get the following:
2005.08.24 21:06:29 AS - Verifying key for host: jabber.org id: BD2C03C1B159
2005.08.24 21:06:29 AS - Key was: INVALID for host: jabber.org id: BD2C03C1B159
2005.08.24 21:06:29 AS - Connection closed for host: jabber.org id: BD2C03C1B159
what do these lines indicate?
Hey Stefan,
The info you are posting is not complete. Before the “AS - *” lines you should have some “OS - *” lines. Could you post again the debug info starting from the first OS line?
Thanks,
– Gato
Sorry, I am currently unable to reproduce the error.
When I reenable connections to jabber.org I now get a timeout:
debug.log:
2005.08.25 16:48:05 OS - Trying to connect to jabber.org:5269
2005.08.25 16:48:05 OS - Connection to jabber.org:5269 successfull
2005.08.25 16:48:05 OS - Sent dialback key to host: jabber.org id: 121D0C223975
from domain: jabber.reucon.net
2005.08.25 16:49:05 OS - Time out waiting for answer in validation from: jabber.org id: 121D0C223975 for domain: jabber.reucon.net
2005.08.25 16:49:05 Finishing Outgoing Server Reader. No session to close.
java.net.SocketException: Socket closed
at java.net.SocketInputStream.socketRead0(Native Method)
at java.net.SocketInputStream.read(SocketInputStream.java:129)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:411)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:453)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:183)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at org.xmlpull.mxp1.MXParser.fillBuf(MXParser.java:2971)
at org.xmlpull.mxp1.MXParser.more(MXParser.java:3025)
at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1144)
at org.xmlpull.mxp1.MXParser.nextToken(MXParser.java:1100)
at org.dom4j.io.XPPPacketReader.parseDocument(XPPPacketReader.java:268)
at org.jivesoftware.messenger.server.OutgoingServerSocketReader$1.run(OutgoingServ erSocketReader.java:91)
Maybe the root cause of that issue is a problem of jabber.org, but nevertheless such a problem of another jabber server should not cause Jive Messenger to hang in the way described above.
I’‘m experiencing the same problem with jabber.org - and I see this thread is from Aug 2005… any chance that you’'ve gotten your issue resolved?
Anyone else have any insight or suggestions on this?
My debug log:
2006.01.26 15:25:41 OS - Trying to connect to jabber.org:5269
2006.01.26 15:26:11 OS - Plain connection to jabber.org:5269 successful
2006.01.26 15:26:11 OS - Error,
java.lang.Exception: Failed to create connection to remote server
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSessionAndSendPac ket(OutgoingSessionPromise.java:139)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(OutgoingSess ionPromise.java:37)
at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(OutgoingSession Promise.java:91)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
2006.01.26 15:27:01 Finishing Outgoing Server Reader. No session to close.
java.net.SocketException: Socket closed
And the error logs attmpting to connect to Pandion.be:
2006.01.26 16:42:57 OS - Plain connection to pandion.be:5269 successful
2006.01.26 16:42:57 OS - Error,
java.lang.Exception: Failed to create connection to remote server
Hey Max,
What I see in common in both cases (jabber.org and pandion.be) is that your server is not getting any connection from the remote servers. Your server is the only one creating outgoing connections but no incoming connection seems to be possible. Therefore, my question for you would be to check that your server name is resolvable by a public DNS, that it points to your server and that port 5269 is opened in the firewall.
Regards,
– Gato