# Elasticsearch WARN message after upgrade 8.19.2 to 8.19.3 **URL:** \ **Category:** Elasticsearch\ **Created:** [August 30, 2025, 3:09am UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460 "2025-08-30T03:09:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![kalai](https://avatars.discourse-cdn.com/v4/letter/k/e495f1/32.png) [@kalai](https://discuss.elastic.co/u/kalai)\ **Post date:** [August 30, 2025, 3:09am UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460/1 "2025-08-30T03:09:51Z")
After upgrade the Elasticsearch version 8.19.2 to 8.19.3 the below message is rollover Not entitled: component [(unknown)], module [ALL-UNNAMED], class [class com.dynatrace.agent.casp.thirdparty.io.UrlUtils], operation [$java\_net\_URL$] org.elasticsearch.entitlement.runtime.api.NotEntitledException: component [(unknown)], module [ALL-UNNAMED], class [class com.dynatrace.agent.casp.thirdparty.io.UrlUtils], operation [$java\_net\_URL$] at org.elasticsearch.entitlement.runtime.policy.PolicyCheckerImpl.notEntitled(PolicyCheckerImpl.java:466) ~[elasticsearch-entitlement-8.19.3.jar:?] at org.elasticsearch.entitlement.runtime.policy.PolicyCheckerImpl.neverEntitled(PolicyCheckerImpl.java:132) ~[elasticsearch-entitlement-8.19.3.jar:?] at org.elasticsearch.entitlement.runtime.policy.PolicyCheckerImpl.checkChangeJVMGlobalState(PolicyCheckerImpl.java:162) ~[elasticsearch-entitlement-8.19.3.jar:?] at org.elasticsearch.entitlement.runtime.policy.PolicyCheckerImpl.checkChangeNetworkHandling(PolicyCheckerImpl.java:187) ~[elasticsearch-entitlement-8.19.3.jar:?] at org.elasticsearch.entitlement.runtime.policy.ElasticsearchEntitlementChecker.check$java\_net\_URL$(ElasticsearchEntitlementChecker.java:485) ~[elasticsearch-entitlement-8.19.3.jar:?] at java.net.URL.(URL.java) ~[?:?] at com.dynatrace.agent.casp.thirdparty.io.UrlUtils.createRestrictedURL(UrlUtils.java:348) ~[?:1.313.54.20250607-101638] at com.dynatrace.agent.casp.thirdparty.codesource.CodeSourceLocationFactory.codeSourceLocationToUri(CodeSourceLocationFactory.java:164) ~[?:1.313.54.20250607-101638] at com.dynatrace.agent.casp.thirdparty.codesource.CodeSourceLocationFactory.fromClass(CodeSourceLocationFactory.java:124) ~[?:1.313.54.20250607-101638] at com.dynatrace.agent.casp.thirdparty.collectors.CodeSourceCollector.getFrom(CodeSourceCollector.java:57) ~[?:1.313.54.20250607-101638] at com.dynatrace.agent.casp.thirdparty.SoftwareComponentInformationCreator.createFrom(SoftwareComponentInformationCreator.java:122) ~[?:1.313.54.20250607-101638] at com.dynatrace.agent.casp.thirdparty.SoftwareComponentExtractor.doExtract(SoftwareComponentExtractor.java:109) ~[?:1.313.54.20250607-101638] at com.dynatrace.agent.casp.thirdparty.SoftwareComponentExtractor.extract(SoftwareComponentExtractor.java:74) ~[?:1.313.54.20250607-101638] ---
**Author:** ![DavidTurner](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/davidturner/32/22453_2.png) [@DavidTurner](https://discuss.elastic.co/u/DavidTurner)\ **Post date:** [August 30, 2025, 7:53am UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460/2 "2025-08-30T07:53:01Z")
> [@kalai](#): > > com.dynatrace.agent The Dynatrace agent isn’t supported and we recommend not using it. See the warning in [these docs](https://www.elastic.co/docs/deploy-manage/deploy/self-managed/installing-elasticsearch#jvm-version) for more information: > **WARNING:** Don’t use third-party Java agents that attach to the JVM. Such agents can be harmful to Elasticsearch stability and performance. In some cases they may cause nodes to freeze, crash, or fail to start up, or to lose or corrupt your data. ---
**Author:** ![kalai](https://avatars.discourse-cdn.com/v4/letter/k/e495f1/32.png) [@kalai](https://discuss.elastic.co/u/kalai)\ **Post date:** [September 2, 2025, 9:21pm UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460/3 "2025-09-02T21:21:09Z")
Thanks David for your response. But I am not using any third party JVM, using inbuild Elasticsearch one only. Not sure the error message. Pls let me know how these error messages are showing if we use inbuilt one ---
**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\ **Post date:** [September 2, 2025, 9:29pm UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460/4 "2025-09-02T21:29:02Z")
> [@kalai](#): > > But I am not using any third party JVM, using inbuild Elasticsearch one only. The issue is not the JVM, from the logs you have a Dynatrace agent that it is attaching itself to the JVM running Elasticsearch. You need to validate it in your system and disable the agent from attaching to the Elasticsearch JVM. ---
**Author:** ![kalai](https://avatars.discourse-cdn.com/v4/letter/k/e495f1/32.png) [@kalai](https://discuss.elastic.co/u/kalai)\ **Post date:** [September 2, 2025, 9:35pm UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460/5 "2025-09-02T21:35:17Z")
Thanks [Leandro Pereira](https://discuss.elastic.co/u/leandrojmp). How can I disable the agent from attaching to the Elasticsearch JVM? ---
**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\ **Post date:** [September 2, 2025, 10:51pm UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460/6 "2025-09-02T22:51:04Z")
> [@kalai](#): > > How can I disable the agent from attaching to the Elasticsearch JVM? You need to ask your dynatrace representative or community. We would have no insight into that. ---
**Author:** ![kalai](https://avatars.discourse-cdn.com/v4/letter/k/e495f1/32.png) [@kalai](https://discuss.elastic.co/u/kalai)\ **Post date:** [September 3, 2025, 5:33pm UTC](https://discuss.elastic.co/t/elasticsearch-warn-message-after-upgrade-8-19-2-to-8-19-3/381460/7 "2025-09-03T17:33:01Z")
Thanks Stephenb