Replies: 2 comments 4 replies
-
Which JAXP implementation are those VMs using? You should be able to find the If I remember correctly, at least one DOM implementation (Axiom DOM?) uses the same class to implement all the possible |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the reply. WORKING VM: NOT WORKING VM: As you may find I can not find the jaxp implementation (DocumentBuilderFactoryImpl) in not working vm ? what could be the reason for this different behavior when both VMs have same openjdk package is installed: (I see: https://bugs.openjdk.org/browse/JDK-8303531 as related to this) |
Beta Was this translation helpful? Give feedback.
-
|
@garydgregory, do you have any ideas on what is going on here?
@kumarbava, maybe there is a |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the reply and your time. No file named "jaxp.properties" under /usr/ path in both servers. Both are running same app (actually its the same rpm is installed from a repo location on all servers) . Verified also that jar files in the app class path are same on all servers. |
Beta Was this translation helpful? Give feedback.
-
|
Hi All, |
Beta Was this translation helpful? Give feedback.
-
|
Also of interest in this area, from the Oracle announcement on various mailing lists: JDK 23 Release Candidates | Restrictive JAXP Configuration Heads-up Everything is on track for the General Availability of Java 23 on September 17th [1] as the JDK 23 Release Candidate builds (RC2 - builds 37) are now available [2]. And before shifting your attention to JDK 24, make sure to check the Heads-Up below as it is related to an important JAXP update in JDK 23. The JVM Language Summit took place earlier this month in Santa Clara (California). During this unique conference, key updates around the Java platforms were presented and discussed. So, make sure to watch the JVMLS 2024 playlist [3] as videos are added regularly. And it's not really a surprise but Valhalla was a highly discussed topic. In his session [4], Brian Goetz (Java Language Architect) explained the proposed solution: value classes, null-restricted types, improved definite assignment analysis, and strict initialization. Around the same time-frame, Valhalla Early-Access builds implementing Value Classes and Objects were also made available [5], see the Release Notes [6] for the details. As usual, feedback should be reported to the proper mailing list [7]. [1] https://openjdk.org/projects/jdk/23/ Heads-up - JDK 23: Prepare for a More Restrictive JAXP ConfigurationThe Java platform supports XML processing with JAXP (Java APIs for XML Processing) that are based on a wide range of XML technologies and standards, which can make them challenging to secure. To mitigate risks, JAXP offers comprehensive security features [8], but the default settings of some security features are not strict, making them opt-in. To improve out-of-the-box security, future JDK releases will make XML processing more restrictive by default and JDKs 21 to 23 help developers prepare for these changes. JDK 21: JAXP Configuration FileJDK 21 added JDK 23: Restrictive JAXP Configuration File TemplateJDK 23 adds The following steps should be used to test an application with that template:
For details, please refer to JDK-8330542 [11]. [8] https://docs.oracle.com/en/java/javase/22/security/java-api-xml-processing-jaxp-security-guide.html#GUID-6E76FE41-A8C5-4F56-AB46-83A89B1E904A JDK 24 Early-Access BuildsThe JDK 24 early-access builds 12 are available [12], and are provided under the GNU General Public License v2, with the Classpath Exception. The Release Notes are available here [13]. Changes in recent JDK 24 builds that may be of interest:
Note: A more exhaustive list of changes can be found here [14]. [12] https://jdk.java.net/24/ Project Loom New Early-Access BuildsThe latest Loom early access builds (Builds 24-loom+3-33 -2024/7/27) are now available [15]. These builds, based on an incomplete version of JDK 24, improve the implementation of Java monitors (synchronized methods) to work better with virtual threads. These builds are intended for developers looking to "kick the tires" and provide feedback or bug reports. Feedback should be reported to the Loom mailing list [16] (subscription required). [15] https://jdk.java.net/loom/ JavaFX Early-Access BuildsThese are early access builds of the JavaFX 23 and 24 Runtime built from openjdk/jfx [17]. These builds enable JavaFX application developers to build and test their applications with JavaFX 23 and 24 on JDK 23 and 24 respectively. And although these builds are designed to work with JDK 23 EA, they are also known to work with JDK 21 and later versions. The latest early access builds of JavaFX 23 (Builds 27) are available [18], under the GNU General Public License, version 2, with the Classpath Exception. And similarly, the latest early access builds of JavaFX 24 (Builds 4) are available here [19]. [17] https://github.com/openjdk/jfx Topics of Interest
|
Beta Was this translation helpful? Give feedback.
-
Could some one help me to understand the issue here.
As the documentation says on Concise Syntax : https://logging.apache.org/log4j/2.x/manual/configuration.html#configuration-with-xml
my log4j xml configuration has below snippet,
however, logging does not work as expected (Pattern is missing in the actual logs)
Error thrown is:
ERROR StatusConsoleListener Error processing element Pattern (Pattern): CLASS_NOT_FOUNDI have changed the xml to below, then logging works as expected including pattern.
My application using log4j version: 2.21.1 (log4j-api, log4j-core)
Why does it complain to me that Pattern CLASS_NOT_FOUND ?
Worth to mention other things also in my application setup:
Beta Was this translation helpful? Give feedback.
All reactions