I had a similar but different issue which I solved.  In doing so, I
found three conditions which cause three errors at this part of the
startup:

You must ensure that the --xmpp_component_name=[NAME] matches the
Openfire Server Settings/External Components/Allowed to Connect
subdomain, and that the Shared secret matches and has no whitespace

1) if you have --xmpp_component_name=foo and there is no "foo" allowed
to connect while the whitelist is selected, the error you will get is:

INFO: Starting client frontend on host: 127.0.0.1 port: 9876 couldn't
connect to XMPP server:org.xmpp.component.ComponentException: host-
unknown

2) If you try to put a more qualified domain name like foo.com in both
then you get:

INFO: Starting client frontend on host: 127.0.0.1 port: 9876
couldn't connect to XMPP server:org.xmpp.component.ComponentException:
org.xmlpull.v1.XmlPullParserException: expected start tag name and
not / (position: START_DOCUMENT seen </... @1:2)

And
3)  If there is an issue with the Shared Secret (such as whitespace in
the secret) you get:

INFO: Starting client frontend on host: 127.0.0.1 port: 9876
couldn't connect to XMPP server:org.xmpp.component.ComponentException:
not-authorized


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Wave 
Protocol" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/wave-protocol?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to