Hey guys,
The problem has been fixed. BTW, I also fixed another s2s problem we were having so download the next nightly build and let me know how it goes.
Thanks,
– Gato
The nightly build does not reject the additional s2s connection (yay!), but there is another problem. I still cannot connect to a MUC room on my JM server from my jabberd 1.4 server. I see this in the JM debug log:
2005.09.20 09:12:27 AS - Verifying key for host: ecotroph.net id: 2eeee4347fb92c1cb0d6082a19ac7a691fd421f8
2005.09.20 09:12:27 AS - Key was: VALID for host: ecotroph.net id: 2eeee4347fb92c1cb0d6082a19ac7a691fd421f8
2005.09.20 09:12:27 OS - Validation GRANTED from: ecotroph.net id: 2eeee4347fb92c1cb0d6082a19ac7a691fd421f8 for domain: fury.blacka.com
2005.09.20 09:12:27 Finishing Outgoing Server Reader. Closing session: org.jivesoftware.messenger.server.OutgoingServerSession@4e1a70b8 status: 1 address: ecotroph.net id: 2eeee4347fb92c1cb0d6082a19ac7a691fd421f8
java.io.EOFException: no more data available - expected end tag
(JD14 is my jabberd 1.4.3 server, JM is my test version of Jive Messager 2005-09-20).
Which obviously looks like JD14 freaks out at the “The room is locked…” message.