-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Exceptions appearing in log #77
Comments
Are these exception significant? |
For the last one (java.lang.UnsatisfiedLinkError: no tcnative-1 ) see the following. That's something in your tomcat instance and would likely apply to any app. |
I think I have figured out the other warnings in the logs. Although I was shutting down some of the threads the context shutdown listener wasn't waiting for the threads to close. This caused the errors. There were also another couple of threads that weren't being stopped. I've committed to my fork https://github.com/revolsys/cpf and am deploying to the delivery environment. When we are ready to migrate then I'll update the bcgov/cpf repository via a pull request |
I'll review https://tomcat.apache.org/native-doc/ |
@pauldaustin do you have APR enabled in your environment? |
@dkelsey No I haven't enabled it as I just have development systems |
I had a chat with Leo and he stated that we are not using APR. |
In <!--APR library loader. Documentation at /docs/apr.html -->
<!--
<Listener className="org.apache.catalina.core.AprLifecycleListener" SSLEngine="on" />
--> After restarting there are no APR warnings. |
Now I see a different warning in
I've searched a little and found solutions that say update @ll911 do you have any suggestions? Note: @pauldaustin If I find other exceptions/warning... I feel I should create a separate ticket. I'm happy to do that for this too. Your thoughts? |
Chatting with Leo he pointed out it is the BGEO CPF Plugin.... so... I'll fix that. |
In exploring the state of CPF in our Delivery environment and OpenJDK11, I observed that the DLV instance, which is on OpenJDK11, had exceptions recorded in the startup logs.
Recording these here.
AND
AND
The text was updated successfully, but these errors were encountered: