Jerry,
On 6/13/23 12:25, Jerry Malcolm wrote:
Chris,
On 6/13/2023 11:03 AM, Christopher Schultz wrote:
Jerry,
On 6/13/23 11:51, Jerry Malcolm wrote:
Reg,
On 6/13/2023 2:57 AM, r.barc...@habmalnefrage.de wrote:
Hey Jerry,
Caused by: java.lang.SecurityException: Can not initialize
cryptographic
mechanism
at
java.base/javax.crypto.JceSecurity.<clinit>(JceSecurity.java:120)
... 86 mo
Caused by: java.lang.SecurityException: Can't read cryptographic
policy
directory: unlimited
Does this help?
https://stackoverflow.com/a/58183460/
Yours,
Reg
The stackoverflow link provides a lot of useful info about the error.
But unless something in the boot process deletes those files and
recreates them later, they are all there and correct. One boot works
fine. The next boot throws this error. The next boot is fine. Is
there a possibility that permissions get altered on this 'unlimited'
folder during boot? I can't think of many reasons it would say a
folder doesn't exist that clearly does exist.
How are you launching Tomcat on boot?
Are you able to add some instrumentation/logging to that?
-chris
In /etc/rc.local I have:
----------------------
sleep 120s
systemctl start tomcat9
That's an odd way to do things (in rc.local).
If you have systemctl, you are using systemd. If you are using systemd,
you isn't it auto-starting that service?
$ sudo systemctl enable tomcat9
That ought to do it, and the tomcat9 service should start on startup,
resolving any dependencies it needs.
Are you able to do an "ls [path to policy files] > /tmp/some_log_file"
in there to see the situation when the service is trying to start?
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
