Not logged in. · Lost password · Register
Forum: agsXMPP RSS
Page: previous  1  2 
Avatar
bartbert #16
Member since Sep 2005 · 22 posts
Group memberships: Members
Show profile · Link to this post
The reason you were seeing "127.0.0.1" in my earlier output is because that was the "name" of the server in JiveMessenger (I guess that was the default). I changed it to "dilbert" but am still having the same problems.

I haven't downloaded the latest from SVN yet, but I created a project using the code that you provided, and here's the output that I'm getting:

OnWriteXml: <stream:stream to='test.gnauck.dyndns.org' xmlns='jabber:component:a
ccept' xmlns:stream='http://etherx.jabber.org/streams'>

OnReadXml: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" from="
test.gnauck.dyndns.org" id="51cf21c7" >

OnWriteXml: <handshake xmlns="jabber:component:accept">837fd994a793c58641f53583d
cfe9f2ee97b5aec</handshake>

OnReadXml: <handshake xmlns="jabber:component:accept" />

OnLogin

OnReadXml: <iq xmlns="jabber:component:accept" from="component.dilbert" id="151-
0" to="test.gnauck.dyndns.org.dilbert" type="get"><query xmlns="http://jabber.or
g/protocol/disco#info" /></iq>


OnWriteXml: </stream:stream>

OnReadXml: </stream>

OnClose


And open the Connection again
OnWriteXml: <stream:stream to='test.gnauck.dyndns.org' xmlns='jabber:component:a
ccept' xmlns:stream='http://etherx.jabber.org/streams'>

OnReadXml: <stream:stream xmlns:stream="http://etherx.jabber.org/streams" from="
test.gnauck.dyndns.org" >

OnWriteXml: <handshake xmlns="jabber:component:accept">e2f142ff6ea2d4ad8c63b3a0a
a0e08d34ce33c82</handshake>

OnReadXml: <stream:error xmlns:stream="http://etherx.jabber.org/streams"><confli
ct xmlns="urn:ietf:params:xml:ns:xmpp-streams" /></stream:error>

OnReadXml: </stream>

OnClose

Unable to write data to the transport connection.

So it seems to be the same issue I was having. The first call to Open works fine, but subsequent ones do not. I will pull down the latest code from SVN and try it again.
Avatar
bartbert #17
Member since Sep 2005 · 22 posts
Group memberships: Members
Show profile · Link to this post
I pulled down the latest code from SVN, but I'm still not having any success. I'm starting to wonder if has more to do with a setting in Jive Messenger. I mean the code is working for you, and I created a project using your code and only changed the server name and password.  Anyway, here's the output that I'm getting:

Opening connection...
OnWriteXml

<stream:stream to='conference' xmlns='jabber:component:accept' xmlns:stream='http://etherx.jabber.org/streams'>
OnReadXml
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" from="conference" id="6bbf94f1" >
OnWriteXml
<handshake xmlns="jabber:component:accept">beb7afd58e5edbc5976abb0375a83fc936e375e7</handshake>
OnReadXml
<handshake xmlns="jabber:component:accept" />
OnLogin
OnReadXml

<iq xmlns="jabber:component:accept" from="component.dilbert" id="38-0" to="conference.dilbert" type="get"><query xmlns="http://jabber.org/protocol/disco#info" /></iq>
Closing connection...
OnWriteXml

</stream:stream>
OnReadXml
</stream>
OnClose
Opening connection...
OnWriteXml

<stream:stream to='conference' xmlns='jabber:component:accept' xmlns:stream='http://etherx.jabber.org/streams'>
OnReadXml
<stream:stream xmlns:stream="http://etherx.jabber.org/streams" from="conference" >
OnWriteXml
<handshake xmlns="jabber:component:accept">e2f142ff6ea2d4ad8c63b3a0aa0e08d34ce33c82</handshake>
OnReadXml
<stream:error xmlns:stream="http://etherx.jabber.org/streams"><conflict xmlns="urn:ietf:params:xml:ns:xmpp-streams" /></stream:error>
OnClose
Avatar
Alex #18
Member since Feb 2003 · 4288 posts · Location: Germany
Group memberships: Administrators, Members
Show profile · Link to this post
ya, thats very odd. The conflict should mean that the component is already logged in. It looks like the server doesnt log off the component correct. Could you look in the sessions if the component shows up after login, and if it doesnt show up after log off. Also interesting would be a netstat to see if the socket gets disconnected. I tried the latest release on windows from Jive and right now the latest nightly build.
What i also dont understand is that the from attrib that the server sends is different in the stream header and in the disco query. I posted a question about hat in the Jive forums and hope to get an answer soon.

Alex
Avatar
bartbert #19
Member since Sep 2005 · 22 posts
Group memberships: Members
Show profile · Link to this post
The Jive Messenger component sessions page shows the component after opening the connection, and then it goes away after closing the connection.

A netstat command shows the following after opening the connection:

  TCP    dilbert:1742           dilbert.home.marrs.com:10015  ESTABLISHED
  TCP    dilbert:10015          dilbert.home.marrs.com:1742  ESTABLISHED

Then it shows this after closing the connection:

  TCP    dilbert:10015          dilbert.home.marrs.com:1742  TIME_WAIT

Then after waiting a few more seconds, that goes away as well, but I still can't get it to connect.
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Page: previous  1  2 
Forum: agsXMPP RSS