Vassal won't start - socket error after Java update

GrumpyOldMan · September 7, 2018, 1:59am

Hi

I updated to Java 18181 and now Vassal won’t start. I searched the forum and saw that it could be AV or firewall stopping socket connection so I (nervously) turned off all my security gear but it still wouldn’t run.

Error Log:-

2018-09-07 11:47:54,543 [0-main] INFO VASSAL.launch.StartUp - Starting
2018-09-07 11:47:54,546 [0-main] INFO VASSAL.launch.StartUp - OS Windows 7 6.1
2018-09-07 11:47:54,546 [0-main] INFO VASSAL.launch.StartUp - Java version 1.8.0_181
2018-09-07 11:47:54,546 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17
2018-09-07 11:47:54,624 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager
2018-09-07 11:47:59,365 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on port 54207
2018-09-07 11:47:59,365 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - java.net.SocketException: Permission denied: connect
2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.connect0(Native Method)
2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2018-09-07 11:47:59,402 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.PlainSocketImpl.connect(Unknown Source)
2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.SocksSocketImpl.connect(Unknown Source)
2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.connect(Unknown Source)
2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at java.net.Socket.(Unknown Source)
2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

2018-09-07 11:47:59,403 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream - at VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2018-09-07 11:47:59,404 [0-main] WARN VASSAL.tools.logging.LoggedOutputStream -

Any help would be appreciated.

Thanks

GrumpyOldMan

GrumpyOldMan · September 7, 2018, 10:51pm

Hello All

It seems my problem was an overzealous firewall that still blocked Java even when the firewall was set to sleep. Gave it a stern talking to, sent it to the Spanish Inquisition and everything works now.

Cheers

GrumpyOldMan

jonahh · September 25, 2018, 8:41am

Thanks. I have a similar issue. I will try your solution and see if it works