Hi,

Sorry for the trouble, there might be something we didn’t account for. While it probably doesn’t fix it, can you please try with 5.2.8, that includes the ’cause’ in that “Could not parse the Opc.Ua.NodeSet2.xml nodeset” IllegalStateException, which probably helps in figuring out what has happened.

Does that WARN about “Cannot initialize XML factories to ignore DTD processing ” still happen? My guess would be it does..

Can you do the following by using the same Java version (and environment), in just a main method (or where you would first use the SDK normally):
javax.xml.parsers.DocumentBuilderFactory.newInstance()
and then for the instance
javax.xml.parsers.DocumentBuilderFactory.setNamespaceAware(true) <– this probably throws in your case?
javax.xml.parsers.DocumentBuilderFactory.newDocumentBuilder()

Basically the WARN should be related to the steps https://cheatsheetseries.owasp.org/cheatsheets/XML_External_Entity_Prevention_Cheat_Sheet.html#Java failing. We do that to prevent some XML-related attacks, but the WARN should only happen with Java 6 (so basically shouldn’t with SDK 5.x since 8 is minimum, but the init code is same as in 4.x). However, for com.prosysopc.ua.UaNodeSet functionality we had to add DocumentBuilderFactory.setNamespaceAware(true) as part of the com.prosysopc.ua.stack.utils.XMLFactoryCache initializations. So if that somehow fails by itself the WARN would appear (and is confusing, we need to change that).

IF I remove that setNamespaceAware(true) and start SampleConsoleServer, I get a NPE regrading a switch-case on a String, which matches your stacktrace.

Since we didn’t get this error in any of our testing and we did test on all major platforms, do you run in some sort of a special setup? (continue in uajava-support@prosysopc.com if not possible to answer here)

I could theorize e.g. GraalVM or maybe OSGi etc. something that has possibly removed the NamespaceAware implementation from the runtime itself or hides it somehow so that it cannot be found. Or maybe if some libs are used that override the xml parsers inside the typical runtime and they wouldn’t have a NamespaceAware implementation. IF yes, maybe you have some configuration option to make it visible/find-able?

P.S.
Sorry, the formatting options are not that great. HTML pre and code tags can be used, but I heavily recommend writing the answer in a notepad first, since both have issues and can remove e.g. xml elements (and indentation doesn’t work).