Vassal will not start up

Technical Support & Bugs
1
  • Model: 3.2.15
  • Operating System: Windows 7 Home Premium 64-bit
  • CPU Intel Core i7 CPU 980 @ 3.33GHz (12 CPUs), ~3.3GHz
  • Memory 6144MB RAM
  • Video Card AMD Radeon HD 6900 Series
  • Vassal version. 3.2.15
  • Java version. 1.8.0_31-b13 Java HotSpot™ Client VM
  • Vassal module name and version Vassal40k6thbasic_ext
  • All I have to do is double click vassal or right click and tell vassal to open and it doesn’t work.
    I have gone though the trouble shooting guide.
2

Here is the Error log I keep getting. I did make sure that I was using an up to date version of java 64bit for my system.

2015-02-14 15:40:50,052 [0-main] INFO VASSAL.launch.StartUp - Starting
2015-02-14 15:40:50,070 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2015-02-14 15:40:50,070 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_31
2015-02-14 15:40:50,070 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.15
2015-02-14 15:40:50,274 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2015-02-14 15:40:51,358 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 53674
2015-02-14 15:40:51,359 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,383 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Invalid argument: connect
2015-02-14 15:40:51,383 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,383 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2015-02-14 15:40:51,383 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,383 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2015-02-14 15:40:51,383 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,383 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2015-02-14 15:40:51,384 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,384 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2015-02-14 15:40:51,384 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,384 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,385 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2015-02-14 15:40:51,386 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,386 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2015-02-14 15:40:51,386 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -
2015-02-14 15:40:51,386 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2015-02-14 15:40:51,386 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

3

Thus spake Delakar:

2015-02-14 15:40:51,358 [0-main] WARN
VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on
port 53674

Something’s blocking VASSAL from connecting over your loopback device.
Are you running a local firewall?

–
J.