powered by Jive Software

Client-Server unable to communicate

Just setup the latest version of Wildfire. The server is up and running, bound to a specific IP via the conf. I can access the control panel via that ip and the dns.

Problem comes when trying to get spark to communicate with the server. Spark just loads endlessly when signing up for a new account. I get username/password invalid when trying to sign into an account I created via the web interface.

I get the following output in the error log.

  1. Begin error.log ###

2006.05.18 18:39:21 [org.jivesoftware.wildfire.spi.ConnectionManagerImpl.startSe

rverListener(ConnectionManagerImpl.java:102)] Could not setup a server socket

java.net.BindException: Address already in use

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.PlainSocketImpl.bind(Unknown Source)

at java.net.ServerSocket.bind(Unknown Source)

at java.net.ServerSocket.(XMPPServer.java:142)

at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

at sun.reflect.NativeConstructorAccessorImpl.newInstance(Unknown Source)

at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(Unknown Sou

rce)

at java.lang.reflect.Constructor.newInstance(Unknown Source)

at java.lang.Class.newInstance0(Unknown Source)

at java.lang.Class.newInstance(Unknown Source)

at org.jivesoftware.wildfire.starter.ServerStarter.start(ServerStarter.j

ava:88)

at org.jivesoftware.wildfire.starter.ServerStarter.main(ServerStarter.ja

va:49)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at com.exe4j.runtime.LauncherEngine.launch(Unknown Source)

at com.install4j.runtime.Launcher.main(Unknown Source)

  1. End error.log ###

Any help would be greatly appreciated.

It looks like something is already bound to the ports the server wants to use. Here’'s what you do:

  1. Stop Wildfire

  2. See what processes are listening to port 5222 and 5223.

On linux, do this to find out:

netstat -tnlp[/code]

On windows, go download TCPView from http://www.sysinternals.com/.