Vassal not launching

Technical Support & Bugs
1

When I run Vassal, I simply get the “busy” mouse icon (with the spinning circle) for a couple seconds,then nothing. The game never launches and I don’t get an error.

Here is the requested system information:

Model: Custom (CyberPower)
OS: WIndows 7-64 bit
CPU: Intel Core i7 3.20GHz
Memory: 12GB
Video: GeForce GTX 560
VASSAL: 3.1.20 and 3.2.0 (tried both)
Java: 7u9

I’ve tried uninstalling and reinstalling the Vassal clients multiple times with no success.

Has anyone else had this problem? Any idea how to fix it?

Thanks!
Sp00ny

2

Thus spake sp00ny:

Has anyone else had this problem? Any idea how to fix it?

What’s in ~/.VASSAL/errorLog?

–
J.

3

I don’t see an errorLog file. The only files in the root Vassal directory are VASSAL.exe and unist.exe.
-Sp00ny

4

Thus spake sp00ny:

I don’t see an errorLog file. The only files in the root Vassal
directory are VASSAL.exe and unist.exe.

I’m not referring to the directory where VASSAL is installed. I’m
referring to ~/.VASSAL. This is a directory named “.VASSAL” in your
home directory.

–
J.

5

Ahh, gotcha. Here is the contents of the errorLog file:

20 Oct 2012 21:45:25.413 0 – Starting
20 Oct 2012 21:45:25.414 0 – OS Windows 7
20 Oct 2012 21:45:25.414 0 – Java version 1.7.0_09
20 Oct 2012 21:45:25.414 0 – VASSAL version 3.1.20
20 Oct 2012 21:45:25.448 0 – Manager
20 Oct 2012 21:45:25.714 0 VASSAL: Problem with socket on port 54935
20 Oct 2012 21:45:25.714 0

20 Oct 2012 21:45:25.715 0 java.net.SocketException: Invalid argument: connect
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.DualStackPlainSocketImpl.connect0(Native Method)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.PlainSocketImpl.connect(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.SocksSocketImpl.connect(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.Socket.connect(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.Socket.connect(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.Socket.(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at java.net.Socket.(Unknown Source)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.715 0 at VASSAL.launch.ModuleManager.main(ModuleManager.java:204)
20 Oct 2012 21:45:25.715 0

20 Oct 2012 21:45:25.777 0 java.lang.ExceptionInInitializerError
at com.sun.jna.Structure.(Structure.java:110)
at VASSAL.tools.MemoryUtils.getPhysicalMemory(MemoryUtils.java:78)
at VASSAL.launch.AbstractLaunchAction.(AbstractLaunchAction.java:97)
at VASSAL.launch.ModuleManagerWindow.(ModuleManagerWindow.java:280)
at VASSAL.launch.ModuleManagerWindow.(ModuleManagerWindow.java:168)
at VASSAL.launch.ModuleManager.launch(ModuleManager.java:398)
at VASSAL.launch.ModuleManager$2.run(ModuleManager.java:293)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$200(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.lang.IllegalStateException: Shutdown in progress
at java.lang.ApplicationShutdownHooks.add(Unknown Source)
at java.lang.Runtime.addShutdownHook(Unknown Source)
at com.sun.jna.Native.loadNativeLibraryFromJar(Native.java:724)
at com.sun.jna.Native.loadNativeLibrary(Native.java:678)
at com.sun.jna.Native.(Native.java:106)
… 21 more

20 Oct 2012 21:45:25.779 0 java.util.concurrent.ExecutionException: java.net.SocketException: Invalid argument: connect
at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
at java.util.concurrent.FutureTask.get(Unknown Source)
at org.jdesktop.swingworker.SwingWorker.get(Unknown Source)
at VASSAL.launch.UpdateCheckRequest.done(UpdateCheckRequest.java:38)
at org.jdesktop.swingworker.SwingWorker$5.run(Unknown Source)
at org.jdesktop.swingworker.SwingWorker$DoSubmitAccumulativeRunnable.run(Unknown Source)
at org.jdesktop.swingworker.AccumulativeRunnable.run(Unknown Source)
at org.jdesktop.swingworker.SwingWorker$DoSubmitAccumulativeRunnable.actionPerformed(Unknown Source)
at javax.swing.Timer.fireActionPerformed(Unknown Source)
at javax.swing.Timer$DoPostEvent.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
at java.awt.EventQueue.access$200(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.awt.EventQueue$3.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
Caused by: java.net.SocketException: Invalid argument: connect
at java.net.DualStackPlainSocketImpl.connect0(Native Method)
at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
at java.net.PlainSocketImpl.connect(Unknown Source)
at java.net.SocksSocketImpl.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at java.net.Socket.connect(Unknown Source)
at sun.net.NetworkClient.doConnect(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.openServer(Unknown Source)
at sun.net.www.http.HttpClient.(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.http.HttpClient.New(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.plainConnect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.connect(Unknown Source)
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at java.net.URL.openStream(Unknown Source)
at VASSAL.tools.version.VersionUtils.getVersion(VersionUtils.java:36)
at VASSAL.tools.version.VersionUtils.getRelease(VersionUtils.java:24)
at VASSAL.tools.version.VersionUtils.update(VersionUtils.java:76)
at VASSAL.tools.version.AbstractUpdateCheckRequest.doInBackground(AbstractUpdateCheckRequest.java:35)
at VASSAL.tools.version.AbstractUpdateCheckRequest.doInBackground(AbstractUpdateCheckRequest.java:30)
at org.jdesktop.swingworker.SwingWorker$1.call(Unknown Source)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at org.jdesktop.swingworker.SwingWorker.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

6

I opened the port from the errorLog (54935) in my router and am not getting a different error:

20 Oct 2012 23:54:55.134 0 – Starting
20 Oct 2012 23:54:55.135 0 – OS Windows 7
20 Oct 2012 23:54:55.135 0 – Java version 1.7.0_09
20 Oct 2012 23:54:55.135 0 – VASSAL version 3.1.20
20 Oct 2012 23:54:55.168 0 – Manager
20 Oct 2012 23:54:55.412 0 VASSAL: Problem with socket on port 51811
20 Oct 2012 23:54:55.412 0

20 Oct 2012 23:54:55.413 0 java.net.SocketException: Invalid argument: connect
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.DualStackPlainSocketImpl.connect0(Native Method)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.PlainSocketImpl.connect(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.SocksSocketImpl.connect(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.Socket.connect(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.Socket.connect(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.Socket.(Unknown Source)
20 Oct 2012 23:54:55.413 0

20 Oct 2012 23:54:55.413 0 at java.net.Socket.(Unknown Source)
20 Oct 2012 23:54:55.414 0

20 Oct 2012 23:54:55.414 0 at VASSAL.launch.ModuleManager.main(ModuleManager.java:204)
20 Oct 2012 23:54:55.414 0

7

Also, I tried opening all ports and adding this PC to a DMZ but had the same results.

8

Thus spake sp00ny:

Ahh, gotcha. Here is the contents of the errorLog file:

20 Oct 2012 21:45:25.413 0 – Starting
20 Oct 2012 21:45:25.414 0 – OS Windows 7
20 Oct 2012 21:45:25.414 0 – Java version 1.7.0_09
20 Oct 2012 21:45:25.414 0 – VASSAL version 3.1.20
20 Oct 2012 21:45:25.448 0 – Manager
20 Oct 2012 21:45:25.714 0 VASSAL: Problem with socket on port 54935
20 Oct 2012 21:45:25.714 0

The Module manager is failing to connect to the socket it opens on
the loopback device. Is your firewall blocking connections to 127.0.0.1?

J.

9

Thus spake sp00ny:

I opened the port from the errorLog (54935) in my router and am not
getting a different error:

The problem has nothing to do with your router. The interface on which
the port is being opened is a strictly local interface.

–
J.

10

I have the Kaspersky firewall running and I don’t believe it is blocking connections to 127.0.0.1. In any event, I disabled Kaspersky entirely for testing purposes, and made sure the Windows firewall was disabled as well, and am still getting a similar error:

21 Oct 2012 19:32:11.722 0 – Starting
21 Oct 2012 19:32:11.723 0 – OS Windows 7
21 Oct 2012 19:32:11.723 0 – Java version 1.7.0_09
21 Oct 2012 19:32:11.723 0 – VASSAL version 3.1.20
21 Oct 2012 19:32:11.759 0 – Manager
21 Oct 2012 19:32:12.121 0 VASSAL: Problem with socket on port 56043
21 Oct 2012 19:32:12.121 0

11

Thus spake sp00ny:

“uckelman” wrote:

Thus spake sp00ny:
The Module manager is failing to connect to the socket it opens on
the loopback device. Is your firewall blocking connections to
127.0.0.1?

J.

I have the Kaspersky firewall running and I don’t believe it is blocking
connections to 127.0.0.1. In any event, I disabled Kaspersky entirely
for testing purposes, and made sure the Windows firewall was disabled as
well, and am still getting a similar error:

21 Oct 2012 19:32:11.722 0 – Starting
21 Oct 2012 19:32:11.723 0 – OS Windows 7
21 Oct 2012 19:32:11.723 0 – Java version 1.7.0_09
21 Oct 2012 19:32:11.723 0 – VASSAL version 3.1.20
21 Oct 2012 19:32:11.759 0 – Manager
21 Oct 2012 19:32:12.121 0 VASSAL: Problem with socket on port 56043
21 Oct 2012 19:32:12.121 0

I don’t have anything more to add at this point, sorry. VASSAL picks a
high-numbered port on 127.0.0.1 in order to coordinate starting the
Module Manager. Something is preventing connections to the ports that
VASSAL is choosing, so getting this to work will involve finding out
what.

–
J.