This is all  on Windows:  Client running on Vista, Host on Windows
Server 2003:

I think the key to this is on the Prosody Console output bown at the
bottom of this post:  The message:  XML is not well formed.

I saw something similar to this when trying to run with Openfire but
gave up on Openfire because of SSL certificate hell.

Run-Client batch file:

set WAVE_SERVER_DOMAIN_NAME=wavewriter.org
set WAVE_SERVER_HOSTNAME=wave.wavewriter.org
set WAVE_SERVER_PORT=5269
set username=ad...@%wave_server_domain_name%

java -jar dist/fedone-client-console-0.2.jar %USERNAME%
%WAVE_SERVER_HOSTNAME% %WAVE_SERVER_PORT%


Client output:


C:\Users\Allen\Documents\Projects\wave-devel\wave-protocol>set
WAVE_SERVER_DOMAI
N_NAME=wavewriter.org

C:\Users\Allen\Documents\Projects\wave-devel\wave-protocol>set
WAVE_SERVER_HOSTN
AME=roboserver

C:\Users\Allen\Documents\Projects\wave-devel\wave-protocol>set
WAVE_SERVER_PORT=
5269

C:\Users\Allen\Documents\Projects\wave-devel\wave-protocol>set
username=ad...@wa
vewriter.org

C:\Users\Allen\Documents\Projects\wave-devel\wave-protocol>java -jar
dist/fedone
-client-console-0.2.jar [email protected] roboserver 5269
←[25;1H
←[s←[1;1H←[J                                       |

                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
                                       |
←[25;1h←[[email protected]> ←[0m←[u←[[email protected]> ←
[0mExceptio
n in thread "pool-1-thread-1" java.lang.IllegalStateException: Payload
(18365970
52 bytes) too large for buffer (32768 bytes)
        at
org.waveprotocol.wave.examples.fedone.rpc.SequencedProtoChannel$1.run
(SequencedProtoChannel.java:117)
        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)



PROSODY CONSOLE output:

socket                         debug    server.lua: accepted new
client connecti
on from 192.168.0.12:53250 to 5269
s2sin318                       info     Incoming s2s connection
s2sin318                       debug    sending: <?xml version='1.0'?>
s2sin318                       debug    sending: <stream:stream id=''
xmlns:stream='http://etherx.jabber.org/streams' version='1.0'
xmlns='jabber:server'>
s2sin318                       info     Disconnecting (unknown host)
[s2sin_unauthed], <stream:error> is: xml-not-well-formed
s2sin318                       debug    sending: <stream:error><xml-
not-well-formed xmlns='urn:ietf:params:xml:ns:xmpp-streams'/></
stream:error>
s2sin318                       debug    sending: </stream:stream>
socket                         debug    server.lua: closed client
handler and removed socket from list
s2sin318                       info     s2s disconnected: nil->nil
(stream error)
s2sin318                       info     Destroying incoming session
nil->nil



--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to