Temporary JAR files are generated at each execution that are not cleaned up

[PaulRambags]

Expected Behavior

I expect the Pipeline 2 to remove temporary files, so that the disk does not fill up.

Actual Behavior

After each execution, a lot of JAR files are generated by the Pipeline and stored in the local temp folder of the account under which the Pipeline runs. These JAR files are not automatically removed.

Steps to Reproduce

Just run a DTBook conversion.

Example

After running a conversion, this is generated in C:\Users\svc_pipeline_BRA-02\AppData\Local\Temp and not cleaned up:

03/31/2026  05:43 PM           242,314 436596930604043260.jar
03/31/2026  05:43 PM           105,684 1087029211393743444.jar
03/31/2026  05:43 PM            68,366 1308178097227417449.jar
03/31/2026  05:43 PM            50,149 5370970069387448807.jar
03/31/2026  05:43 PM            90,023 11379718617341601711.jar
03/31/2026  05:43 PM            89,758 17144929397392228072.jar
03/31/2026  05:43 PM            14,526 13554973474827009003.jar
03/31/2026  05:43 PM           333,325 3629363213289445798.jar
03/31/2026  05:43 PM           232,354 3641089316668078777.jar
03/31/2026  05:43 PM           105,446 4384966229723322714.jar
03/31/2026  05:43 PM        14,386,028 4105267211133483903.jar
03/31/2026  05:43 PM           586,812 8849001711817100829.jar
03/31/2026  05:43 PM            87,077 2637035852515673223.jar
03/31/2026  05:43 PM            36,174 9584099341828478424.jar
03/31/2026  05:43 PM            26,605 14041320465023997886.jar
03/31/2026  05:43 PM           278,286 2155588633839367391.jar
03/31/2026  05:43 PM         3,176,148 16267409550637731596.jar
03/31/2026  05:43 PM           572,551 6799748561315487270.jar
03/31/2026  05:43 PM         1,229,289 6390764439829330687.jar
03/31/2026  05:43 PM           708,436 551054942531084525.jar
03/31/2026  05:43 PM           529,249 7748382732679801650.jar
03/31/2026  05:43 PM         3,728,517 7917786992759329176.jar
03/31/2026  05:43 PM           337,027 11618307112792805651.jar
03/31/2026  05:43 PM           259,053 16329266060435948588.jar
03/31/2026  05:43 PM            81,508 13730796927269907476.jar
03/31/2026  05:43 PM           238,043 3992754199873641823.jar
03/31/2026  05:43 PM         1,434,558 7793901235068107053.jar
03/31/2026  05:43 PM           317,192 5104806674601387002.jar

Some of the contents of these JAR files:

1. org\daisyzedval\
2. org\tritonus\share\
3. org\ccil\cowan\tagsoup\
4. org\tritonus
5. org\w3c\css\sac\
6. net\sf\saxon\dom\

Environment

• Operating system: Windows Server 2022 Standard version 21H2, 64-bit
• DAISY Pipeline 2 version: 1.15.2
• Interface: command line interface, and web UI
• JVM: OpenJDK Runtime Environment Temurin-17.0.14+7 (build 17.0.14+7)

[bertfrees]

@PaulRambags I asked you this before in an email, and you confirmed that the JAR files are generated for each conversion, and that the Pipeline process is not stopped in between. But I don't understand. This simply does not match what is in the code. The JARs should be created once, when the Pipeline is launched (or when the API is used for the first time, this depends on the version). Also, the files should normally be deleted when the Java process exists.

I am doing some improvements to temporary file management in various places in the code now, because there are issues. But the issues you mention I can not see.

Could you test it again with version 1.15.4?