AWS Blu Age L3 workshop - Tomcat server needs restart often to solve issues

I am performing the AWS Blu Age L3 Workshop. In the Appstream instance, once in a while the Blu Age batch jobs stop running properly. In the Eclipse console, minimal number of messages appear, and the DISPLAYs from the application and utilities are not appearing. But, all the steps show the message: Program return code is 0. A snippet from Console log: 2024-05-23_13-58-29-777 | [STEP] STEP040 - Started 2024-05-23 11:58:29.807 INFO 2728 --- [ Thread-18] c.n.b.g.rt.db.stats.DatabaseStatistics : DATABASE STATISTIC DISABLED 2024-05-23_13-58-29-808 | Program return code is 0 2024-05-23_13-58-29-808 | [STEP] STEP040 - Ended 2024-05-23_13-58-29-808 | [JOB] CREASTMT - Ended

Even though the above log indicates all the steps completed with return code of 0, in reality the job has not executed any steps and none of the output files are created.

Workaround: If I stop the Tomcat server and start it again, and then submit the same job, it works fine - all the application program / utility messages appear in the Console and output files are generated. The above problem keeps occurring once in a while and only a Tomcat server restart is resolving the issue. This problem happens for online JICS application also. In case of online, executing a transaction will show a blank screen and no error messages in Console. After restarting the Tomcat server, the same transaction works fine.

Question: Are there other log files and additional debugging mechanisms available (other than the Tomcat server Console) that can be used to debug the problem when running a AWS Blu Age batch job? As I mentioned above, the Console log just says the program gave a return code of 0.