[JDEV] Yaja connection problem (was RE: please help me)

[Mike Prince]

Jabber has roughly three kinds of "things" it connects to: clients,
other jabber servers, and components.
 
Clients are usually the instant messengers you see on your desktop and
connect via port 5222.  Other jabber servers connect using 5269, and
components connect to whatever port you've told jabber to allow them on.
 
For each of these they use a different namespace.
 
>From the details you gave below, you mean to use the server namespace on
port 5222, which is doomed to fail.  Also, the secret is actually a
password known by the server that the component uses to validate itself.
Clients don't use secrets, and instead have another similar but
different validation mechanism.
 
Do you really mean to program a jabber component?  Or do you want to
write a client?
 
Thanks,
 
Mike
 
 -----Original Message-----
From: Suchitra Joshi [mailto:suchitra.joshi at objectorb.com] 
Sent: Monday, March 24, 2003 11:22 PM
To: mike at machino.org
Subject: please help me



Mike,
 
I'm are using the Yaza API. I have facing a problem. For testing I am
running EchoComponent, an example class.
 
I have set  
String sSecret = com.realtime.xmpp.XmppSession.JABBER_SERVER_NAMESPACE; 
String sHost = ( argv.length > 1 ? argv[1] : "serpens" );
String sPort = ( argv.length > 2 ? argv[2] : "5222" );
 in EchoComponent
 
I am getting the following error.
 
3.25.03 12:37.56.718 (Re)starting Connection
3.25.03 12:37.56.765 Opening Socket:
com.realtime.xmpp.streams.SocketStreamFactory serpens:5222
3.25.03 12:37.56.890 Socket Open
3.25.03 12:37.56.921 Starting Session: jabber:component:accept
3.25.03 12:37.57.875 XMPP Parser Selected:
org.apache.xerces.parsers.SAXParser at e8f
3.25.03 12:37.58.125 Sending Packet:
<handshake>ca44ce71d83f1fea7ec5c27dd7c230643256c677</handshake>
3.25.03 12:37.58.203 Incoming packet: <stream:error
xmlns:stream="http://etherx.jabber.org/streams">Invalid
Namespace</stream:error>
3.25.03 12:37.58.281 Packet in: <stream:error
xmlns:stream="http://etherx.jabber.org/streams">Invalid
Namespace</stream:error>
Ignoring packet: <stream:error
xmlns:stream="http://etherx.jabber.org/streams">Invalid
Namespace</stream:error>
Warning: missing namespace prefix ignored: 
3.25.03 12:37.58.296 Session Authenticated
Warning: missing namespace prefix ignored: stream
3.25.03 12:37.58.109 Session Started
3.25.03 12:37.58.312 Connection Error: java.net.SocketException: socket
closed (code=0)
3.25.03 12:37.58.312 Socket Closing
3.25.03 12:37.58.312 (Re)starting Connection
3.25.03 12:37.58.312 Stream Closed
3.25.03 12:37.58.328 Opening Socket:
com.realtime.xmpp.streams.SocketStreamFactory serpens:5222
3.25.03 12:37.58.328 Socket Open
3.25.03 12:37.58.375 Starting Session: jabber:component:accept
3.25.03 12:37.58.406 XMPP Parser Selected:
org.apache.xerces.parsers.SAXParser at 3026
3.25.03 12:37.58.421 Incoming packet: <stream:error
xmlns:stream="http://etherx.jabber.org/streams">Invalid
Namespace</stream:error>
3.25.03 12:37.58.421 Packet in: <stream:error
xmlns:stream="http://etherx.jabber.org/streams">Invalid
Namespace</stream:error>
Ignoring packet: <stream:error
xmlns:stream="http://etherx.jabber.org/streams">Invalid
Namespace</stream:error>
3.25.03 12:37.58.437 Sending Packet:
<handshake>8644c6898bf95476e65bf72474680e5e0a612360</handshake>
Warning: missing namespace prefix ignored: 
Warning: missing namespace prefix ignored: stream
3.25.03 12:37.58.437 Connection Error: java.net.SocketException: socket
closed (code=0)
java.io.IOException: Timed out waiting for XMPP handshake
 java.lang.Throwable(java.lang.String)
 java.lang.Exception(java.lang.String)
 java.io.IOException(java.lang.String)
 void
com.realtime.xmpp.dom.DomAcceptComponent.waitForAuthentication(long)
 void com.realtime.xmpp.dom.DomAcceptComponent.start()
 void com.realtime.xmpp.examples.EchoComponent.main(java.lang.String [])

Please respond ASAP.
 
Regards
Suchitra


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.jabber.org/jdev/attachments/20030325/14cb151e/attachment-0002.htm>