# VASSAL had an internal error

**URL:** <https://forum.vassalengine.org/t/vassal-had-an-internal-error/10017>\
**Category:** Technical Support & Bugs\
**Created:** [September 18, 2019, 12:33am UTC](https://forum.vassalengine.org/t/vassal-had-an-internal-error/10017 "2019-09-18T00:33:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AmbassadorALV](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/a/90ced4/32.png) [@AmbassadorALV](https://forum.vassalengine.org/u/AmbassadorALV)\
**Post date:** [September 18, 2019, 12:33am UTC](https://forum.vassalengine.org/t/vassal-had-an-internal-error/10017/1 "2019-09-18T00:33:08Z")

</div>

> [@](#):
>
> VASSAL was unable to submit your bug report. Please post the file /home/albert/.VASSAL/errorLog and a description of what you were doing when the bug occurred in the Technical Support & Bugs section of the VASSAL Forum.

I was waiting for the Mayday module, version 2.1, to finish loading.  
Unable to attach the log file - forum interface says “The extension is not allowed”. (What extension? 😕 )

First few lines of the log:

2019-09-17 20:18:48,822 [0-main] INFO VASSAL.launch.StartUp - Starting  
2019-09-17 20:18:48,832 [0-main] INFO VASSAL.launch.StartUp - OS Linux 4.15.0-64-generic  
2019-09-17 20:18:48,834 [0-main] INFO VASSAL.launch.StartUp - Java version 11.0.4  
2019-09-17 20:18:48,834 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17  
2019-09-17 20:18:51,400 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager  
2019-09-17 20:19:32,547 [0-SwingWorker-pool-231311211-thread-3] INFO VASSAL.launch.AbstractLaunchAction - Loading module file /home/albert/Documents/Wargames/VassalMod/Mayday\_2.1.vmod  
2019-09-17 20:19:33,514 [0-SwingWorker-pool-231311211-thread-3] INFO VASSAL.tools.io.ProcessLauncher - launching /usr/lib/jvm/java-11-openjdk-amd64/bin/java -classpath /home/albert/VASSAL-3.2.17/lib/Vengine.jar -Xmx307M -DVASSAL.id=2 -Duser.home=/home/albert -DVASSAL.port=43801 VASSAL.tools.image.tilecache.ZipFileImageTiler /home/albert/Documents/Wargames/VassalMod/Mayday\_2.1.vmod /home/albert/.VASSAL/tiles/25941236f011107751e9ed625107a022e310dc8a 256 256  
2019-09-17 20:19:39,574 [2-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Starting  
2019-09-17 20:19:39,955 [0-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream - WARNING: An illegal reflective access operation has occurred  
WARNING: Illegal reflective access by VASSAL.tools.image.ImageIOImageLoader (file:/home/albert/VASSAL-3.2.17/lib/Vengine.jar) to field sun.java2d.cmm.ProfileDeferralMgr.deferring  
WARNING: Please consider reporting this to the maintainers of VASSAL.tools.image.ImageIOImageLoader  
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations  
WARNING: All illegal access operations will be denied in a future release

---

<div class="post-metadata">

**Author:** ![JoelCFC25](https://forum.vassalengine.org/user_avatar/forum.vassalengine.org/joelcfc25/32/2687_2.png) [@JoelCFC25](https://forum.vassalengine.org/u/JoelCFC25)\
**Post date:** [September 18, 2019, 1:08am UTC](https://forum.vassalengine.org/t/vassal-had-an-internal-error/10017/2 "2019-09-18T01:08:16Z")

</div>

See this thread: [https://forum.vassalengine.org/t/vassal-doesnt-seem-to-work-with-java-9-version/9654/1](https://forum.vassalengine.org/t/vassal-doesnt-seem-to-work-with-java-9-version/9654/1)

At the moment there are only test builds with support for Java 11, no official release yet.

---

<div class="post-metadata">

**Author:** ![delerini](https://forum.vassalengine.org/letter_avatar_proxy/v4/letter/d/b5e925/32.png) [@delerini](https://forum.vassalengine.org/u/delerini)\
**Post date:** [September 21, 2019, 4:01pm UTC](https://forum.vassalengine.org/t/vassal-had-an-internal-error/10017/3 "2019-09-21T16:01:19Z")

</div>

> [@AmbassadorALV](#):
>
> > [@](#):
> >
> > VASSAL was unable to submit your bug report. Please post the file /home/albert/.VASSAL/errorLog and a description of what you were doing when the bug occurred in the Technical Support & Bugs section of the VASSAL Forum.
> 
> I was waiting for the Mayday module, version 2.1, to finish loading.  
> Unable to attach the log file - forum interface says “The extension is not allowed”. (What extension? 😕 )
> 
> First few lines of the log:
> 
> 2019-09-17 20:18:48,822 [0-main] INFO VASSAL.launch.StartUp - Starting  
> 2019-09-17 20:18:48,832 [0-main] INFO VASSAL.launch.StartUp - OS Linux 4.15.0-64-generic  
> 2019-09-17 20:18:48,834 [0-main] INFO VASSAL.launch.StartUp - Java version 11.0.4  
> 2019-09-17 20:18:48,834 [0-main] INFO VASSAL.launch.StartUp - VASSAL version 3.2.17  
> 2019-09-17 20:18:51,400 [0-AWT-EventQueue-0] INFO VASSAL.launch.ModuleManager - Manager  
> 2019-09-17 20:19:32,547 [0-SwingWorker-pool-231311211-thread-3] INFO VASSAL.launch.AbstractLaunchAction - Loading module file /home/albert/Documents/Wargames/VassalMod/Mayday\_2.1.vmod  
> 2019-09-17 20:19:33,514 [0-SwingWorker-pool-231311211-thread-3] INFO VASSAL.tools.io.ProcessLauncher - launching /usr/lib/jvm/java-11-openjdk-amd64/bin/java -classpath /home/albert/VASSAL-3.2.17/lib/Vengine.jar -Xmx307M -DVASSAL.id=2 -Duser.home=/home/albert -DVASSAL.port=43801 VASSAL.tools.image.tilecache.ZipFileImageTiler /home/albert/Documents/Wargames/VassalMod/Mayday\_2.1.vmod /home/albert/.VASSAL/tiles/25941236f011107751e9ed625107a022e310dc8a 256 256  
> 2019-09-17 20:19:39,574 [2-main] INFO VASSAL.tools.image.tilecache.ZipFileImageTiler - Starting [myloweslife](https://myloweslife.onl/)  
> 2019-09-17 20:19:39,955 [0-ProcessLauncher-2] WARN VASSAL.tools.logging.LoggedOutputStream - WARNING: An illegal reflective access operation has occurred  
> WARNING: Illegal reflective access by VASSAL.tools.image.ImageIOImageLoader (file:/home/albert/VASSAL-3.2.17/lib/Vengine.jar) to field sun.java2d.cmm.ProfileDeferralMgr.deferring  
> WARNING: Please consider reporting this to the maintainers of VASSAL.tools.image.ImageIOImageLoader  
> WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations  
> WARNING: All illegal access operations will be denied in a future release

It’s the fault of our current hosting provider. Lunarpages has been nothing but awful every time I’ve had to deal with them. We were almost ready to move to our new site (hosted on our own machine, elsewhere); the current problem I think will hasten the move, I think.