So i got nashorn to fire up with the simplest possible configuration
possible on jdk17 with tomcat11.
I then compared the working environment to to environment that i have the
issue on. I basically rigged up tomcat to use log4j2 for logging across the
board. That required a smallish change to the s
On Sun, Nov 24, 2024 at 4:53 PM Amit Pande
wrote:
>
> Though it's super late, thought of sharing using JMX to get the application
> deployment status.
>
> https://github.com/amitlpande/java-utils/blob/master/ApplicationeploymentCheckerValve.java
> https://github.com/amitlpande/java-utils/blob/mas
Though it's super late, thought of sharing using JMX to get the application
deployment status.
https://github.com/amitlpande/java-utils/blob/master/ApplicationeploymentCheckerValve.java
https://github.com/amitlpande/java-utils/blob/master/server.xml
Appreciate reviews/comments.
Thanks,
Amit
--
Hi Chris,
> Are there no logs or anything like that?
Our service stops quickly.
Nothing in logs though we redirect all tomcat logs into logs of our application.
> When Java encounters an error, it usually produces an hs_pid file which may
> be in an unusual location given the unusual CWDs of sy
