In a recent build PKI server (which is based on Tomcat) was stuck during startup due to an incorrect library path.

Steps to reproduce:

1. Set up a RHEL 10 Beta machine
2. Install tomcat-9.0.87-2.el10
3. Install dogtag-pki-11.5.4-2.el10
4. Create a Tomcat instance with PKI libraries: pki-server create
5. Deploy PKI's ROOT webapp: pki-server webapp-deploy --descriptor /usr/share/pki/server/conf/Catalina/localhost/ROOT.xml ROOT
6. Run Tomcat on the foreground: pki-server run --debug
7. Use a separate terminal to run the client: wget http://$HOSTNAME:8080

Actual result: The client is stuck waiting for response from Tomcat.

$ wget http://pki1.example.com:8080
{}2024-08-22 14:52:54{}  http://pki1.example.com:8080/
Resolving pki1.example.com (pki1.example.com)... 10.0.199.209
Connecting to pki1.example.com (pki1.example.com)|10.0.199.209|:8080... connected.
HTTP request sent, awaiting response... 

Expected result: The client should get a response from Tomcat (which could be any HTTP error code).

Additional info: According to rhn-support-csutherl Tomcat is trying to scan the entire file system so it's taking a long time to start so it won't respond to clients. This issue doesn't happen if there's no webapp deployed. The issue happens both with Java 17 and 21.