Java Error (Linux)

Technical Support & Bugs
1

I’m running Debian Squeeze with the latest version of VASSAL (3.1.13).

Whenever I run the shell script to start VASSAL I get the following error:

VASSAL: IO error
java.net.SocketException: Invalid argument
	at java.net.PlainSocketImpl.socketBind(Native Method)
	at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
	at java.net.ServerSocket.bind(ServerSocket.java:336)
	at java.net.ServerSocket.<init>(ServerSocket.java:202)
	at VASSAL.launch.ModuleManager.main(ModuleManager.java:157)

I’m using the OpenJDK JRE, version 6b17-1.7-1. I have tried it with Sun’s Java and gotten the same error.

Any advice to fix this?

2

Thus spake “Carborane”:

3.1.14 is the latest version of VASSAL. We recommend upgrading.

The error is happening on a line where we’re trying to open a socket on
the loopback interface. One reason this could fail is if your local
firewall is preventing connections to loopback. I suppose there could
also be some issue with IPv6, if you’re using that. Check both things
and let us know.

–
J.

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

3

Upgraded to 3.1.14, same issue. I don’t have a local firewall and I do not use IPv6, what else could be the source of the problem?

4

Thus spake “Carborane”:

Are you certain you have no iptables rules blocking connections to your
loopback device? What output do you get from ‘sudo iptables -L’?

–
J.

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

5

sudo iptables -L gives:

[code]Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination
[/code]

6

Thus spake “Carborane”:

What happens is if you try ‘ping 127.0.0.1’? ‘ping localhost’?

–
J.

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

7

Huh. I tried version 3.0 and it works flawlessly.

And then I gave 3.1.14 another go… and that also works perfectly. I’m not sure what changed but I no longer have any errors. I guess an update somewhere fixed whatever problem I was having.

8

I’m getting a very similar error message on launching VASSAL (v. 3.1.14).

VASSAL: IO error java.net.SocketException: Invalid argument at java.net.PlainSocketImpl.socketBind(Native Method) at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:365) at java.net.ServerSocket.bind(ServerSocket.java:319) at java.net.ServerSocket.<init>(ServerSocket.java:185) at VASSAL.launch.ModuleManager.main(ModuleManager.java:157)

I’ve looked at iptables and I’ve got the exact same output. I’ve also pinged 127.0.0.1 and it worked so the loopback device is fine. Any other suggestions. At the point of failure VASSAL has created the directory VASSAL in the home dir and also created the key and lock files in this dir (both are empty). I’m using the sun java (v 6.20-dlj-1).

9

I found a solution for this problem - not a very satisfactory solution, but a solution none-the-less. The open java JRE works fine with no issues nor error messages. It looks like something funny with just the Sun JRE.

10

Thus spake “jman11”:

What’s unsatisfactory about that solution? I’m not surprised to find that
OpenJDK works better than Sun’s.

–
J.

Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)