I'm using 1.0b4, and I'm having an annoyingly intermittent problem with some JML logins. This is as far as I've got:
It appears that sometimes, the MSN server will choke on (part of) an address book, send back a "241" error with an XML payload ("chunk data", I think JML calls it?), but still send "ADL <TrID> OK" afterwards.
Now, it looks like when that's happening, JML is somehow failing to absorb the chunk data, because right after being notified of the 241, I immediately get an error looking like this: 'unknown message: <ml ><d n="gmail.com"><cn="USERNAME_REDACTED" l="0" /></d></ml>ADL 6 OK'
It looks to me as though the XML payload of the 241 error is not being absorbed, and is messing up the parsing of the next command. I've poked around a bit in the source, and have got as far as noting that there is a special case in net.sf.jml.protocol.incoming.IncomingError which sets "isChunkSupported" to true for error 241. So some developer was obviously aware of this - but it appears not to be working as designed.
Regrettably, I can't reproduce this - my account works fine, as does that of all the friends I've tried so far. The above information is peeled out of debug logs from other people, whose accounts I can't just hijack to try it out. (Likewise, tcpdump would be something of an invasion of privacy, not to mention the "sipping from the firehose" problem). But if someone suggests any further anonymous debugging information to pull out, I could probably manage.
I would be very grateful for any help.
Meredydd
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi! I'm having the exact same problem... -_-
I'm testing Jitsi 2.4 and the nightly version 2.5.5250, which uses this library (dont know which version).
I know this is an really old thread, but if you are still interested in logs with the error you mentioned, I could provide them.
I'm eager to find a solution to this problem... but I don't know a bit about Java v_v
Regards!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I'm using 1.0b4, and I'm having an annoyingly intermittent problem with some JML logins. This is as far as I've got:
It appears that sometimes, the MSN server will choke on (part of) an address book, send back a "241" error with an XML payload ("chunk data", I think JML calls it?), but still send "ADL <TrID> OK" afterwards.
Now, it looks like when that's happening, JML is somehow failing to absorb the chunk data, because right after being notified of the 241, I immediately get an error looking like this: 'unknown message: <ml ><d n="gmail.com"><cn="USERNAME_REDACTED" l="0" /></d></ml>ADL 6 OK'
It looks to me as though the XML payload of the 241 error is not being absorbed, and is messing up the parsing of the next command. I've poked around a bit in the source, and have got as far as noting that there is a special case in net.sf.jml.protocol.incoming.IncomingError which sets "isChunkSupported" to true for error 241. So some developer was obviously aware of this - but it appears not to be working as designed.
Regrettably, I can't reproduce this - my account works fine, as does that of all the friends I've tried so far. The above information is peeled out of debug logs from other people, whose accounts I can't just hijack to try it out. (Likewise, tcpdump would be something of an invasion of privacy, not to mention the "sipping from the firehose" problem). But if someone suggests any further anonymous debugging information to pull out, I could probably manage.
I would be very grateful for any help.
Meredydd
Hi! I'm having the exact same problem... -_-
I'm testing Jitsi 2.4 and the nightly version 2.5.5250, which uses this library (dont know which version).
I know this is an really old thread, but if you are still interested in logs with the error you mentioned, I could provide them.
I'm eager to find a solution to this problem... but I don't know a bit about Java v_v
Regards!