Solved
Issue running tmp patch for CS466318
Getting failures applying this patch to my test environment on RHEL 9. Fails with following message:
DEBUG 14-04-2026 13:21:37 - [java] java.lang.RuntimeException: Unable to write to byte cache
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.util.DiskCache.writeByteArray(DiskCache.java:191)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.javac.CompiledClass.<init>(CompiledClass.java:118)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.createCompiledClass(JdtCompiler.java:344)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.javac.JdtCompiler$CompilerImpl.process(JdtCompiler.java:306)
DEBUG 14-04-2026 13:21:37 - [java] at org.eclipse.jdt.internal.compiler.Compiler.processCompiledUnits(Compiler.java:575)
DEBUG 14-04-2026 13:21:37 - [java] at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:475)
DEBUG 14-04-2026 13:21:37 - [java] at org.eclipse.jdt.internal.compiler.Compiler.compile(Compiler.java:426)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.javac.JdtCompiler.doCompile(JdtCompiler.java:1020)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.javac.CompilationStateBuilder$CompileMoreLater.compile(CompilationStateBuilder.java:322)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.javac.CompilationStateBuilder.doBuildFrom(CompilationStateBuilder.java:532)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.javac.CompilationStateBuilder.buildFrom(CompilationStateBuilder.java:464)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.cfg.ModuleDef.getCompilationState(ModuleDef.java:423)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Precompile.precompile(Precompile.java:210)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Precompile.precompile(Precompile.java:190)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Precompile.precompile(Precompile.java:131)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Compiler.compile(Compiler.java:192)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Compiler.compile(Compiler.java:143)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Compiler.compile(Compiler.java:132)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Compiler$1.run(Compiler.java:110)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.CompileTaskRunner.doRun(CompileTaskRunner.java:55)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.CompileTaskRunner.runWithAppropriateLogger(CompileTaskRunner.java:50)
DEBUG 14-04-2026 13:21:37 - [java] at com.google.gwt.dev.Compiler.main(Compiler.java:113)
DEBUG 14-04-2026 13:21:37 - [java] Caused by: java.io.IOException: No space left on device
DEBUG 14-04-2026 13:21:37 - [java] at java.base/java.io.RandomAccessFile.write0(Native Method)
I’ve seen this before first place I looked was my /tmp and /var/tmp folders. I do have noexec on those mounts. I used the variables IATEMPDIR and java command line tmp switches. I can see it using my specified new temp area with oodles of space and open rights. But, I also see folders and execution in /tmp still. I was able to remount with exec option but did not seem to make a difference. Message “No space left on device” still appeared.
Other special details is that I am running with wtSafeArea so I used the special switches indicated in help docs below (TIP: Only specify 1 option):
Usage:
java -jar <patch_jar_filename> [--help]
[--describe]
[--antDebug]]
[--antVerbose]]
[--antOpts <ant_memory_value>]
[--install <product_root>]
[--forceinstall <product_root>]
[--javaHome <java_home>]
[--makeJar <product_root>]
[--recompileRbinfo <product_root>]
[--jsfrags <product_root>]
[--xconfManager <product_root>]
[--safeAreaInstall <product_root>]
[--completeSafeAreaInstall <product_root>]
Options (Only one option can be specified at a time):
-h,--help Displays usage information.
-b,--describe Displays a brief description of the patch.
-d,--antDebug Set ant debug to true.
-v,--antVerbose Set ant verbose to true.
-m,--antOpts Allows user to set the memory options for ANT_OPTS
variable used by ANT. An array of values must be specified
in quotes. For Eg: "-Xms128m -Xmx256m".
-i,--install Installs the patch content and runs configuration actions
that are appropriate for this patch. Must pass in the
product root directory as an argument.
-f,--forceinstall Installs the patch content and runs configuration actions
even though the patch may have previously been installed.
Not applicable for all product patches. Must pass in the
product root directory as an argument.
-j,--javaHome Allows user to set JAVA_HOME.
-k,--makeJar Allows user to execute MakeJar.
-c,--recompileRbinfo Allows user to recompile rbInfo files.
-s,--jsfrags Allows user to deploy Jsfrags.
-x,--xconfManager Allows user to forcibly execute xconfmanager.
-a,--safeAreaInstall Safe area mode install extracts the files in patch which
are also site-modified into <install-
dir>/wtSafeArea/ptcCurrent directory. This allows user
time to merge the files modified by the patch with their
site modified files before running the complete safe area
install.
-g,--completeSafeAreaInstall Complete safe area mode install runs the standard patch
install as well as copies the files merged by user in
<install-dir>/wtSafeArea/siteMod to <install-dir>
I did not see any files in the ptcCurrent area created so proceeded ahead with completeSafeAreaInstall. I also did not see space filled up. I put a watch on the folder and sure enough, it filled up /tmp area but immediately cleaned itself up after failure. Sneaky.
