Vassal shutsdown after about 60 secs

Technical Support & Bugs
1

Just come back to using Vassal after a few month absence

I was using 3.2.13 and it was working fine
But now it shuts down after about 60 secs whether a module is selected or not.
No error report is given

Tried Updating to 3.2.15 but this is behaving the same, I have tried updating Jave…no change

OS windows 8.1

2

Model Sony Vaio SVE171C11M
OS 8.1
CPU Intel i7 3632QM @ 2.2GHz
Memory 8GB
Video AMD Radeon HD7500M/7600 series
Java - latest

3

2015-01-22 21:01:16,123 [0-main] INFO VASSAL.launch.StartUp - Starting
2015-01-22 21:01:16,123 [0-main] INFO VASSAL.launch.StartUp - OS Windows 8 6.2
2015-01-22 21:01:16,123 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_31
2015-01-22 21:01:16,123 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.15
2015-01-22 21:01:16,216 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager

4

The following event log generated when attempting to open module ( The Devil’s Cauldron)

2015-01-22 22:02:43,813 [0-main] INFO VASSAL.launch.StartUp - Starting
2015-01-22 22:02:43,813 [0-main] INFO VASSAL.launch.StartUp - OS Windows 8 6.2
2015-01-22 22:02:43,813 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_31
2015-01-22 22:02:43,813 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.15
2015-01-22 22:02:43,907 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2015-01-22 22:02:52,878 [0-SwingWorker-pool-12347030-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module file C:\Users\Andy\Downloads\The_devils_cauldron_v643.vmod
2015-01-22 22:02:53,378 [0-SwingWorker-pool-12347030-thread-1] INFO VASSAL.launch.TilingHandler - No images to tile.
2015-01-22 22:02:53,378 [0-SwingWorker-pool-12347030-thread-1] INFO VASSAL.launch.AbstractLaunchAction - Loading module The Devils Cauldron v6
2015-01-22 22:02:53,378 [0-SwingWorker-pool-12347030-thread-1] INFO VASSAL.tools.io.ProcessLauncher - launching C:\Program Files (x86)\Java\jre1.8.0_31\bin\java -Xms256M -Xmx512M -DVASSAL.id=1 -DVASSAL.port=52163 -Duser.home=C:\Users\Andy -Duser.dir=C:\Program Files\VASSAL-3.2.15 -cp lib\Vengine.jar VASSAL.launch.Player --load – C:\Users\Andy\Downloads\The_devils_cauldron_v643.vmod
2015-01-22 22:02:54,175 [1-main] INFO VASSAL.launch.StartUp - Starting
2015-01-22 22:02:54,190 [1-main] INFO VASSAL.launch.StartUp - OS Windows 8 6.2
2015-01-22 22:02:54,190 [1-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_31
2015-01-22 22:02:54,190 [1-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.15
2015-01-22 22:02:54,190 [1-main] INFO VASSAL.launch.Launcher - Player

5

Tried to run the program again this morning and attempted to dig a bit deeper VASSAL: Problem with socket on port 50828 seems to be the issue, ive included a full error log below for a basis vassel open request, no modules selected.

2015-01-23 11:23:02,231 [0-main] INFO VASSAL.launch.StartUp - Starting
2015-01-23 11:23:02,235 [0-main] INFO VASSAL.launch.StartUp - OS Windows Vista 6.0
2015-01-23 11:23:02,236 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_31
2015-01-23 11:23:02,236 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.15
2015-01-23 11:23:02,402 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2015-01-23 11:23:23,688 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 50828
2015-01-23 11:23:23,688 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,689 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.ConnectException: Connection timed out: connect
2015-01-23 11:23:23,689 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,690 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2015-01-23 11:23:23,690 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,690 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2015-01-23 11:23:23,690 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,691 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2015-01-23 11:23:23,691 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,691 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2015-01-23 11:23:23,691 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,691 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2015-01-23 11:23:23,692 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,692 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2015-01-23 11:23:23,692 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,692 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2015-01-23 11:23:23,692 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,693 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2015-01-23 11:23:23,693 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,693 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2015-01-23 11:23:23,693 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,693 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2015-01-23 11:23:23,693 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,694 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2015-01-23 11:23:23,694 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-01-23 11:23:23,694 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2015-01-23 11:23:23,694 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

6

I have just tried disconnecting from the internet and turning off firewall …problem still apparent.

Tried running several times and checking the log file… still appears to be socket issues but different numbers are appearing each time I run the program ie 51156, 51171, 51181 and 51187.

7

Java version “1.8.0_31”
Java™ SE Runtime Environment (build 1.8.0_31-b13)
Java HotSpot™ Client VM (build 25.31-b07, mixed mode)

8

Thus spake steelpanther:

I have just tried disconnecting from the internet and turning off
firewall …problem still apparent.

Tried running several times and checking the log file… still appears
to be socket issues but different numbers are appearing each time I run
the program ie 51156, 51171, 51181 and 51187.

We randomize the port we use, which is the explanation for seeing a
different port on each run.

It looks like the Module Manager is unable to connect to the socket over
which the Module Manager talks to itself. That could happen because
the OS is blocking it or because you have a stale or corrupt key file.
It’s safe to delete C:\Users<username>\AppData\Roaming\VASSAL\key when
VASSAL isn’t running. That would be the first thing I’d try.

–
J.

9

I have already tried a clean install
made sure all roaming, regedit references to vassal were removed after an uninstall

10

Issue now resolved …had to completely reinstall laptop good job I had all the disks

Must have been some sort of registry clash …But needed Vassal

11

Thus spake steelpanther:

Issue now resolved …had to completely reinstall laptop good job I had
all the disks

Must have been some sort of registry clash …But needed Vassal

Glad to hear that you got it working. Nothing but VASSAL reads VASSAL’s
registry keys, so it’s unlikely to have been those. Java itself has a
history of being flaky on Windows—I’m not surprised that a completely
fresh install fixed the problem for you.

–
J.