Error opening JavaGestureServer1.0.0b.jar

7 views
Skip to first unread message

icube

unread,
Apr 12, 2009, 11:55:43 PM4/12/09
to sparsh-ui
Hi,

I've got this following message when i executes
JavaGestureServer1.0.0b.jar from the command line.

[GestureServer] Failed to open a server socket.
java.net.BindException: Address already in use: JVM_Bind
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.<init>(Unknown Source)
at java.net.ServerSocket.<init>(Unknown Source)
at sparshui.server.GestureServer.openSocket(GestureServer.java:
77)
at sparshui.server.GestureServer.<init>(GestureServer.java:35)
at sparshui.server.GestureServer.main(GestureServer.java:27)
[GestureServer] Accepting Connections
Exception in thread "main" java.lang.NullPointerException
at sparshui.server.GestureServer.acceptConnections
(GestureServer.java:90
)
at sparshui.server.GestureServer.run(GestureServer.java:43)
at sparshui.server.GestureServer.main(GestureServer.java:27)

what might be wrong?
Message has been deleted

Jay

unread,
Apr 13, 2009, 12:09:44 AM4/13/09
to sparsh-ui
This generally happens when you attempt to start the gesture server
more than once, or it can also happen if you already are using the
port that the gesture server uses. The gesture server uses port 5945
by default, and can be changed if you have the source code by
modifying sparshui.common.NetworkConfiguration.java. We should let
you specify the port on the command line in the next release.

If you've got a service running on port 5945, you'll need to stop it
to run the Gesture Server. Make sure that you're not already running
an instance of the gesture server. Finally, if for some reason the
Gesture Server crashes (let us know if it does!), it can hold on to
that port for a while following the exit. Just give it about a minute
and a half to reset.

Jay
Reply all
Reply to author
Forward
0 new messages