Hi Niklas,

I'm sorry but I really don't have any details that would help you. I did not 
try logging on debug level becaus the first 'test'-tests I ran Vysper with 
default (debug) logging I got the following error two times - before figuring 
out, that I should change the logging level:

java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:92)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:136)
        at 
com.sun.net.ssl.internal.ssl.OutputRecord.writeBuffer(OutputRecord.java:297)
        at 
com.sun.net.ssl.internal.ssl.OutputRecord.write(OutputRecord.java:286)
        at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecordInternal(SSLSocketImpl.java:743)
        at 
com.sun.net.ssl.internal.ssl.SSLSocketImpl.writeRecord(SSLSocketImpl.java:731)
        at 
com.sun.net.ssl.internal.ssl.AppOutputStream.write(AppOutputStream.java:59)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:202)
        at sun.nio.cs.StreamEncoder.implFlushBuffer(StreamEncoder.java:272)
        at sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:276)
        at sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:122)
        at java.io.OutputStreamWriter.flush(OutputStreamWriter.java:212)
        at java.io.BufferedWriter.flush(BufferedWriter.java:236)
        at 
org.jivesoftware.smack.PacketWriter.writePackets(PacketWriter.java:193)
        at org.jivesoftware.smack.PacketWriter.access$000(PacketWriter.java:40)
        at org.jivesoftware.smack.PacketWriter$1.run(PacketWriter.java:76)

(but maybe this already helps you. ;-) )

Greetings,
Peter

----- Original Message -----
From: [email protected]
To: [email protected]
Date: 03.08.2011 16:54:24
Subject: Re: Vysper performance analysis


> Very interesting, thanks for notifying us! I'm sure the german version
> would be of interest as well, there are people around here who would
> have no problem understanding it :-)
> 
> Would you happen to have further details on the errors you got with
> the high frequency test cases?
> 
> /niklas



Reply via email to