powered by Jive Software

Socks5 Bytestreams Proxy showing up twice

=) That should say it all. I vaguely recall that “at first” I was only getting one copy of the proxy.jabber.vorpalcloud.org instance, but now I’'m definitely seeing two.

Simple bug or something else I might be doing?

Interesting, restarting the server didn’'t make the duplicate go away.

Well the server actually crashed out from under me, but still. =)

Something else crashed as well so I’‘m not 100% sure it’‘s not the system’'s fault.

Hey Daniel,

Do you see any errors in your log files? Anything similar when your server crashed? Did you turn on or off the proxy, or is do you have any idea on how I could go about recreating this? The unusual thing is that it is still there when you restart.

Thanks,

Alex

Before it crashed, the last event in the log was:

2006.04.03 01:22:26 [org.jivesoftware.wildfire.server.OutgoingServerSession.crea

teOutgoingSession(OutgoingServerSession.java:315)] Error creating secured outgoi

ng session to remote server: jabber.org(DNS lookup: jabber.org:5269)

org.xmlpull.v1.XmlPullParserException: could not determine namespace bound to el

ement prefix stream (position: START_DOCUMENT seen stream:error@1:14)

at org.xmlpull.mxp1.MXParser.parseStartTag(MXParser.java:1816)

at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1479)

at org.jivesoftware.wildfire.net.MXParser.nextImpl(MXParser.java:331)

at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093)

at org.jivesoftware.wildfire.server.OutgoingServerSession.createOutgoing

Session(OutgoingServerSession.java:283)

at org.jivesoftware.wildfire.server.OutgoingServerSession.authenticateDo

main(OutgoingServerSession.java:139)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.createSession

AndSendPacket(OutgoingSessionPromise.java:126)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise.access$300(Ou

tgoingSessionPromise.java:37)

at org.jivesoftware.wildfire.server.OutgoingSessionPromise$1$1.run(Outgo

ingSessionPromise.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.04.03 01:22:27 [org.jivesoftware.wildfire.net.SocketReader.run(SocketReader

.java:161)] Connection closed before session established

Socket[addr=/208.245.212.98,port=48986,localport=5269]

nothing really there to tell me what happened. It might have been in the stdout or stderr logs, but they’‘re already been overwritten. =/ Clearly it’‘s all jabber.org’'s fault. ;D ;D ;D

As for the proxy stuff, I don’'t see anything in the logs about it.

Hey Daniel:

Think I found a solution to fix the issue you were seeing initially.

JM-626

Let me know if with the new release you see this problem anymore.

Cheers,

Alex

Indeed =D Looks good!

Also, as for the crash, I’'ve got something else going on that I think may have been the root cause of the crash. Investigating… =) Will post a separate thread if I see it.