Socket Error - Please Help

i have scoured the net and forums finding only one similar post, but the OP has no idea how it started working. i’ve tried everything mentioned there.

here’s my system info…

  • HP Pavilion dv9000

  • Operating System: Windows XP - Media Center Edition Version 2002 - SP3

  • CPU: Intel Core 2 - T5500 @ 1.66GHz

  • Memory: 2GB

  • Video Card: NVIDIA GeForce Go 7600

  • Vassal version: 3.1.15

  • Java version. 1.6.0_24

  • Vassal module name and version: got this error with every module i tried --Arkham_Horror_FFG.vmod‎ v1.6.9 – ShadowsOverCamelotv4.vmod – apples_v2.0_basic+kids+custom.mod

  • I just downloaded VASSALs latest version, updated java, and installed the program. I ran VASSAL, went to file|open module, and selected my game. i’ve attempted to run 3 modules now and gotten a “Socket Error” every time. the window actually pops up twice. first it says :

Socket Error
The socket over which the Module Manager communicates has had a fault. Please restart VASSAL.

details → java.util.concurrent.ExecutionException: java.io.EOFException
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.AbstractLaunchAction$LaunchTask.done(AbstractLaunchAction.java:539)
at VASSAL.launch.Player$LaunchAction$1.done(Player.java:162)
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$000(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.awt.EventQueue$1.run(Unknown Source)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$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.io.EOFException
at java.io.DataInputStream.readInt(Unknown Source)
at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:438)
at VASSAL.launch.AbstractLaunchAction$LaunchTask.doInBackground(AbstractLaunchAction.java:227)
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$Worker.runTask(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)

Followed by by the same “Socket Error” message with different log details →

java.net.SocketException: socket closed
at java.net.PlainSocketImpl.socketAccept(Native Method)
at java.net.PlainSocketImpl.accept(Unknown Source)
at java.net.ServerSocket.implAccept(Unknown Source)
at java.net.ServerSocket.accept(Unknown Source)
at VASSAL.launch.CommandServer.run(CommandServer.java:62)
at java.lang.Thread.run(Unknown Source)

In my attempts to remedy this i’ve re-reinstalled java, reinstalled VASSAL (to different drive), completely shut down my firewall (comodo), restarted windows, and cursed like a sailor with tourettes.

any other suggestions, please? i really wanna play some games.

any other suggestions, please? i really wanna play some games.

VASSAL is trying to communicate over your computer’s loopback interface (127.0.0.1). You should check whether that works. E.g., try pinging it.

Greetings, guys!

Sorry to bump into this thread, but i’m happening to suffer the same issue.

Tried every approach to fix it, but without luck:

  • Reinstalling VASSAL - OK
  • Disabling Firewall/Antivirus - OK
  • Ping 127.0.0.1 - OK

Even tried out the workarround explained here:

http://www.vassalengine.org/forum/viewtopic.php?f=3&t=3876&start=30

Everything without luck.

So, any other guess?

Thanks.

If this is necessary, here there are my system’s basic specs:

Model: N/A (Custom PC)
OS: Windows 7 (64 bits)
CPU: AMD Phenom II x4 945, 3.02 Ghz
Memory: 4GB
Video: ATI Radeon HD 5750
VASSAL: 3.1.15
Java: 1.6.0_24
Module: N/A (i get the error with any Mod, even the tour)

And here it is a copy of Vassal’s error log:

I’ve started getting these same errors after previously being able to use Vassal. And I’ve about run out of things to try for a solution.

Socket Error
The socket over which the Module Manager communicates has had a fault. Please restart VASSAL.

Socket Error
The socket over which the Module Manager communicates has had a fault. Please restart VASSAL.

Turning off Firewalls & Anti-virus does not help.

Far as I can tell, it might have to do with installing extra PC protection in the form of a DNS modification, detailed here; Blocking Unwanted Parasites with a Hosts File

I do not think OpenDNS is the issue, or at least it does not seem to block things in this manner.

Tech Support Guy System Info Utility version 1.0.0.1
OS Version: Microsoft Windows XP Home Edition, Service Pack 3, 32 bit
Processor: mobile AMD Athlon™ XP-M 1900+, x86 Family 6 Model 10 Stepping 0
Processor Count: 1
RAM: 2047 Mb
Graphics Card: NVIDIA GeForce FX 5500, 256 Mb
Hard Drives: C: Total - 114463 MB, Free - 33370 MB;
Motherboard: ECS, M863, 1.0, 00000000
Antivirus: Norton Internet Security, Updated: Yes, On-Demand Scanner: Enabled

Java; Version 6 Update 25 (build 1.6.0_25-b06) 2011

Any help would be appreciated… :confused:

It took me a bit to figure out where XP put the Vassal folder with the log - And I did not realize it overwrites each time;

Vassal version; 3.1.15
Module in question; HGB version0214d

Error Log;

Thus spake SmilodonUP:

I’ve started getting these same errors after previously being able to
use Vassal. And I’ve about run out of things to try for a solution.

Socket Error
The socket over which the Module Manager communicates has had a fault.
Please restart VASSAL.

Does this happen every time you load a module? Immediately? After
you use the module for a while?


J.