[messages] [Technical Support & Bugs] Vassal-3.2.10 wont start

vorman87 mwhitehead87 at hotmail.co.uk
Wed Feb 12 23:56:31 CET 2014


J.

yeah a little confusing I agree. :)

Below however is the error report from when I last tried to run Vassal
3.2.11-svn9002:

2014-02-11 17:58:03,949 [0-main] INFO  VASSAL.launch.StartUp - Starting
2014-02-11 17:58:03,953 [0-main] INFO  VASSAL.launch.StartUp - OS
Windows 7 6.1
2014-02-11 17:58:03,953 [0-main] INFO  VASSAL.launch.StartUp - Java
version 1.7.0_51
2014-02-11 17:58:03,953 [0-main] INFO  VASSAL.launch.StartUp - VASSAL
version 3.2.11-svn9002
2014-02-11 17:58:03,997 [0-AWT-EventQueue-0] INFO 
VASSAL.launch.ModuleManager - Manager
2014-02-11 17:58:04,218 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream - VASSAL: Problem with socket on
port 49222
2014-02-11 17:58:04,219 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,219
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream -
java.net.SocketException: Invalid argument: connect
2014-02-11 17:58:04,219 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,219
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.DualStackPlainSocketImpl.connect0(Native Method)
2014-02-11 17:58:04,219 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,219
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
2014-02-11 17:58:04,219 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,221
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,221
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,221
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.AbstractPlainSocketImpl.connect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,221
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.PlainSocketImpl.connect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,221
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.SocksSocketImpl.connect(Unknown Source)
2014-02-11 17:58:04,221 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,221
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.Socket.connect(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,222
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.Socket.connect(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,222
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.Socket.<init>(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,222
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
java.net.Socket.<init>(Unknown Source)
2014-02-11 17:58:04,222 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  2014-02-11 17:58:04,222
[0-main] WARN  VASSAL.tools.logging.LoggedOutputStream - 	at
VASSAL.launch.ModuleManager.main(ModuleManager.java:216)
2014-02-11 17:58:04,222 [0-main] WARN 
VASSAL.tools.logging.LoggedOutputStream -  


Let me know if you need anything else, system specs etc

Thanks for your help so far though.


Matt

_______________________________________________
Read this topic online here:
http://www.vassalengine.org/forum/viewtopic.php?p=43923#p43923


More information about the messages mailing list