2.13 debug compile.log issue

[RT]

I tested out 2.13 in my project and got the following error after trying to debug "GWT Development Mode with Jetty" in Eclipse 2025-09 (4.37.0)

Running java org.eclipse.justj.openjdk.hotspot.jre.full.win32.x86_64_21.0.5.v20241023-1957\jre

Running CodeServer with parameters: [-noprecompile, -port, 9876, -sourceLevel, 17, -bindAddress, 127.0.0.1, -launcherDir, C:\myproject\war, -logLevel, INFO, -style, OBFUSCATED, -strict, com.myclass, com.myclass]
Super Dev Mode starting up
   workDir: C:\Users\me\AppData\Local\Temp\gwt-codeserver-15019746707938385524
[main] INFO org.eclipse.jetty.util.log - Logging initialized @2022ms to org.eclipse.jetty.util.log.Slf4jLog
   Loading Java files in com.myclass.
   Module setup completed in 3179 ms
java.nio.file.FileSystemException: C:\Users\me\AppData\Local\Temp\gwt-codeserver-15019746707938385524\com.myclass\compile-1: failed to delete one or more files; see suppressed exceptions for details
at com.google.gwt.thirdparty.guava.common.io.MoreFiles.throwDeleteFailed(MoreFiles.java:803)
at com.google.gwt.thirdparty.guava.common.io.MoreFiles.deleteRecursively(MoreFiles.java:554)
at com.google.gwt.dev.codeserver.OutboxDir.create(OutboxDir.java:91)
at com.google.gwt.dev.codeserver.CodeServer.makeOutboxTable(CodeServer.java:182)
at com.google.gwt.dev.codeserver.CodeServer.start(CodeServer.java:151)
at com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:104)
at com.google.gwt.dev.codeserver.CodeServer.main(CodeServer.java:55)
at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:103)
at java.base/java.lang.reflect.Method.invoke(Method.java:580)
at com.google.gwt.dev.shell.SuperDevListener.runCodeServer(SuperDevListener.java:118)
at com.google.gwt.dev.shell.SuperDevListener.start(SuperDevListener.java:97)
at com.google.gwt.dev.DevMode.ensureCodeServerListener(DevMode.java:705)
at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:778)
at com.google.gwt.dev.DevMode.doStartup(DevMode.java:599)
at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:880)
at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:698)
at com.google.gwt.dev.DevMode.main(DevMode.java:476)
Suppressed: java.nio.file.FileSystemException: C:\Users\me\AppData\Local\Temp\gwt-codeserver-15019746707938385524\com.myclass\compile-1\compile.log: The process cannot access the file because it is being used by another process
at java.base/sun.nio.fs.WindowsException.translateToIOException(WindowsException.java:92)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:103)
at java.base/sun.nio.fs.WindowsException.rethrowAsIOException(WindowsException.java:108)
at java.base/sun.nio.fs.WindowsFileSystemProvider.implDelete(WindowsFileSystemProvider.java:273)
at java.base/sun.nio.fs.AbstractFileSystemProvider.delete(AbstractFileSystemProvider.java:104)
at java.base/java.nio.file.Files.delete(Files.java:1152)
at com.google.gwt.thirdparty.guava.common.io.MoreFiles.deleteRecursivelyInsecure(MoreFiles.java:678)
at com.google.gwt.thirdparty.guava.common.io.MoreFiles.deleteDirectoryContentsInsecure(MoreFiles.java:698)
at com.google.gwt.thirdparty.guava.common.io.MoreFiles.deleteRecursivelyInsecure(MoreFiles.java:671)
at com.google.gwt.thirdparty.guava.common.io.MoreFiles.deleteRecursively(MoreFiles.java:543)
... 15 more

Looks like guava MoreFiles is having issues with the log file created.

I tried running Eclipse as admin and doing a clean/rebuild but the error remains. 

Changing back to 2.12.2 allows the debug session to run even with the log issue:
Super Dev Mode starting up
   workDir: C:\Users\me\AppData\Local\Temp\gwt-codeserver-5121754604815682518.tmp
[main] INFO org.eclipse.jetty.util.log - Logging initialized @2240ms to org.eclipse.jetty.util.log.Slf4jLog
   Loading Java files in com.myclass.
   Module setup completed in 4115 ms
   [WARN] unable to delete 'C:\Users\me\AppData\Local\Temp\gwt-codeserver-5121754604815682518.tmp\com.myclass\compile-1' (skipped)
   [ERROR] unable to create directory: C:\Users\me\AppData\Local\Temp\gwt-codeserver-5121754604815682518.tmp\com.myclass\compile-1
   Loading Java files in com.myclass.
   Module setup completed in 731 ms
[main] INFO org.eclipse.jetty.server.Server - jetty-9.4.44.v20210927; built: 2021-09-27T23:02:44.612Z; git: 8da83308eeca865e495e53ef315a249d63ba9332; jvm 21.0.5+11-LTS
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@29835b68{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.AbstractConnector - Started ServerConnector@1c45c654{HTTP/1.1, (http/1.1)}{127.0.0.1:9876}

[main] INFO org.eclipse.jetty.server.Server - Started @5882ms
The code server is ready at http://127.0.0.1:9876/

I'm guessing it's something to do with my specific build, so is there something I can do to either relocate the log file or disable it perhaps?  

[Colin Alworth]

I'm sorry for the inconvenience, it looks like you're encountering https://github.com/gwtproject/gwt/issues/10272. The bad news is that of all the GWT users running on Windows, you're one of only two (so far) able to reproduce this - but if possible, we'd love to gather a little more information on why that might be. The good news is that we have a tentative fix, linked from that ticket, with an SDK download for you to try and confirm that it solves it.

[RT]

Thanks for the quick reply!  I downloaded the java 21 version linked from that ticket and ran it and the error is not present.  I presume this is 2.13 based on the jetty version listed (jetty-9.4.58.v20250814)

Running CodeServer with parameters: [-noprecompile, -port, 9876, -sourceLevel, 17, -bindAddress, 127.0.0.1, -launcherDir, C:\myproject\war, -logLevel, INFO, -style, OBFUSCATED, -strict, com.myclass, com.myclass]
Super Dev Mode starting up

   workDir: C:\Users\me\AppData\Local\Temp\gwt-codeserver-1135198551249951907
[main] INFO org.eclipse.jetty.util.log - Logging initialized @1813ms to org.eclipse.jetty.util.log.Slf4jLog

   Loading Java files in com.myclass.

   Module setup completed in 19356 ms

   Loading Java files in com.myclass.

   Module setup completed in 632 ms
[main] INFO org.eclipse.jetty.server.Server - jetty-9.4.58.v20250814; built: 2025-08-14T02:28:49.637Z; git: 8f1440587e9e4ae7db3d74cf205643f3d707148d; jvm 21.0.5+11-LTS
[main] INFO org.eclipse.jetty.server.handler.ContextHandler - Started o.e.j.s.ServletContextHandler@18817f93{/,null,AVAILABLE}
[main] INFO org.eclipse.jetty.server.AbstractConnector - Started ServerConnector@3032b238{HTTP/1.1, (http/1.1)}{127.0.0.1:9876}
[main] INFO org.eclipse.jetty.server.Server - Started @20983ms

The code server is ready at http://127.0.0.1:9876/

Code server started in 20.30 s ms
[main] INFO org.eclipse.jetty.server.Server - jetty-9.4.58.v20250814; built: 2025-08-14T02:28:49.637Z; git: 8f1440587e9e4ae7db3d74cf205643f3d707148d; jvm 21.0.5+11-LTS

If you are interested in digging deeper let me know and I can reproduce the issue for you, just let me know what info you want.

[Craig Mitchell]

Was there an old code server running in the background that didn't shutdown correctly?  If you create a bat file with this in it (this script will kill any zombie code servers):

for /f "tokens=5" %%a in ('netstat -aon ^| findstr :9876.*LISTENING') do taskkill /f /pid %%a

When you run it, does fix the issue?