On Sunday 13 January 2008 05:22:45 Sean Gilbertson wrote: > Hi all, > > Okay, so I'm developing a Jabber client for my Sidekick (phone/mobile > internet device), and I'm having issues when my code actually runs on > the phone. I'm thinking it's not an SDK issue, though; I'm thinking > that my connection to the Jabber server is getting messed up -- > especially because my code works fine in the simulator. > > So here's my current problem: When I send a <presence><status>My > status here!</status></presence> tag to the server, it immediately > sends me a <iq/> and then, immediately following that, a > </stream:stream>, which closes the connection. My input loop then > closes, and the whole thing is kaput. So, it appears that the Jabber > server I'm connected to is having some sort of problem with me, and I > can't tell what. > > Keep in mind that in the SDK simulator, the <presence/> block sends > fine, and then the server sends me an <iq/>, and then all of the > presence information for people on my Contact list -- which is what's > expected! And the stream is definitely not terminated. > > So, why would this happen? Anyone who can help me with it definitely > gets a triple-scoop ice cream on ME! > > Thanks so much!! > Sean Hello. You didn't specified what type of server you using (domainname or at least software version). Then it seems pretty unlikely that any compliant server will have such a behaivour - it may be that you are actually sending something different onto the wire. The best thing you can do to get a good reply to this list is to reproduce the problem with minimum number of packets possible and then send a dump of stream io here starting from the last packet that you got the answer for. You may use thing like tcpflow (may be ethereal too) for it if you do not use ssl/tls.
-- Respectfully Alexey Nezhdanov
