Hello:
Trying to run the server on Windows Server 2003
I gave up on Openfire because of SSL issues and an XML problem, I went
to Prosody yesterday. I followed the guide on the wiki.
The server will not federate with Acmwave. At first there would be a
long timeout before the "remote-server-not-found" error returned but I
found an issue with my SRV record (wave.wavewriter.org). Once I fixed
that, now the ping error return is immediate:
<iq type="error" to="wave.wavewriter.org" from="wave.acmewave.com"
id="7270-0">
<error type="cancel">
<remote-server-not-found xmlns="urn:ietf:params:xml:ns:xmpp-
stanzas"/>
</error>
</iq>
Exception in thread "pool-2-thread-1" java.lang.NullPointerException
Furthermore, I can run multiple clients on the local machine with the
server and they work fine - sharing a wave. However if I run the
client on another machine (inside my firewall), then I cannot
connect. At first, there was no indication of connection attempt on
either the Prosody or WRS console, but I found a blog which suggested
adding "component_interface = "0.0.0.0"."
After doing that, the prosody console now indicates an attempt to
connect:
socket debug server:lua accepted new client
connection from 192.168.0.12:59197 to 5275
jcp5090 info Incoming Jabber component
connection
jcp5090 info Disconnecting component,
<stream:error> is: xml-not-well-formed
socket debug server.lua: closed client
handler and removed socket from list
jcp5090 info component disconnected: nil
(stream error)
still, there is no indication of a connection attempt on the WRS
console.
"xml-not-well-formed" reminds me of the issue I was having with the
Openfire console that is the "XML Problem" mentioned above. I asked
for help at: http://code.google.com/p/wave-protocol/wiki/ConsoleClient
but got no replies (still asking for help there).
Furthermore, I tried updating the wave-protocol (my copy was about 3
weeks old) from mercurial this morning and now it will not build. I
posted that issue in a separate message.
This has been a slow process for me building this up on Windows Server
2003. I seem to be running into every issue that is out there.
(including debugging errors that STILL exist in the Windows build
instructions after I posted comments).
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---
