Vassal starts then stops

Technical Support & Bugs
1
  • HP
  • Win7
  • CPU Intel I7
  • Memory : 8GB
  • Video Card : integrated
  • Vassal version 3.2.15
  • Java version. 8u51

After a recent general upgrade of Java, McAfee, and Vassal, Vassal will not work. Prior to this it was solid

Vassal starts then after 10 seconds or terminates.
I have turned off the firewall and McAfee family protection as a test, still no luck
While Vassal is open I can see the version, look at the log files, check server status. However I cannot import or delete modules.

Mark

2

From the error log, problem with socket port 58720. Does this give a hint to anyone ?

2015-07-28 20:49:39,742 [0-main] INFO VASSAL.launch.StartUp - Starting
2015-07-28 20:49:39,758 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2015-07-28 20:49:39,758 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_51
2015-07-28 20:49:39,758 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.15
2015-07-28 20:49:39,851 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2015-07-28 20:50:01,254 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 58720
2015-07-28 20:50:01,254 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2015-07-28 20:50:01,254 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.ConnectException: Connection timed out: connect
2015-07-28 20:50:01,254 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - 2015-07-28 20

3

Thus spake mcaskey11925:

From the error log, problem with socket port 58720. Does this give a
hint to anyone ?

2015-07-28 20:49:39,742 [0-main] INFO VASSAL.launch.StartUp - Starting
2015-07-28 20:49:39,758 [0-main] INFO VASSAL.launch.StartUp - OS
Windows 7 6.1
2015-07-28 20:49:39,758 [0-main] INFO VASSAL.launch.StartUp - Java
version 1.8.0_51
2015-07-28 20:49:39,758 [0-main] INFO VASSAL.launch.StartUp - VASSAL
version 3.2.15
2015-07-28 20:49:39,851 [0-AWT-EventQueue-0] INFO
VASSAL.launch.ModuleManager - Manager
2015-07-28 20:50:01,254 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on
port 58720
2015-07-28 20:50:01,254 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - 2015-07-28 20:50:01,254
[0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
java.net.ConnectException: Connection timed out: connect
2015-07-28 20:50:01,254 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - 2015-07-28 20

You’re having a problem with the socket over which the Module Manager
talks to itself and to Player instances in which modules are opened.

You might already have something running on that port, or there could
be something (e.g, antivirus program, local firewall) blocking the
port for you.

J.

4

Turns out that it was McAfee Family Protection software that was doing something nefarious, even with all the filters supposedly turned off. Removing it fixed the problem.