Hi,

Generally speaking a Session should have nothing to with information model loading, thus the error is odd. Or well historically there was an idea that maybe one could do that from the Client side, but that doesn’t basically exist nowadays. You could add individual nodes however and some APIs are related to that, which possibly could have been used accidentally here.

Thus, please look at the com.prosysopc.ua.samples.server.SampleConsoleServer.loadInformationModels() in the sampleconsoleserver example. It contains (commented) examples of loading nodesets. Copied as-is the method contents:

// // Register generated classes
// server.registerModel(DiServerInformationModel.MODEL);
// server.registerModel(AdiServerInformationModel.MODEL);
//
// // Load the standard information models
// try {
// // You can reference these bundled models either directly
// server.getAddressSpace().loadModel(DiServerInformationModel.class.getResource(“Opc.Ua.Di.NodeSet2.xml”).toURI());
//
// // or via the codegenerated helper getLocationURI() method
// server.getAddressSpace().loadModel(AdiServerInformationModel.getLocationURI());
//
// // You can also register and load model in one call
// server.registerAndLoadModel(PlcServerInformationModel.MODEL,
// PlcServerInformationModel.getLocationURI());
// } catch (Exception e) {
// throw new RuntimeException(e);
// }

If that doesn’t help, can you tell how you are loading the model?

P.S.
Technically if the resources outputs of Codegen are on the classpath, SDK can automatically discover and do the registerModel automatically (models must be loaded manually).

I have a theory.
Normally there shouldn’t be anything that could cause “java.lang.NullPointerException: Cannot invoke “com.prosysopc.ua.server.ServerUserIdentity.getType()” because the return value of “com.prosysopc.ua.server.Session.getUserIdentity()”, since nothing related to model loading should be Session-related.

However (and I did test this as well now), IF you have taken com.prosysopc.ua.samples.server.MyNodeManagerListener in the sampleconsoleserver as-is and added that to the NodeManagerUaNode to which you are trying to load the model, our sample code

+

will cause the error. This should potentially be labeled as our bug, since that doesn’t happen for adding a node, since that internally is checked that is the ServiceContext.isInternal() in which case the listener is not called (and there is a separate protected method (createNodeForNodeSet2) one could override in the NodeManagerUaNode. But there isn’t anything similar to References, so seems we do call that listener method. And the internal context session is null (intentionally).

Thus, you should be able to make this work by changing the ‘checkUserAccess’ (or do similar on your code) to do something like

Since the listener methods are only intended for the AddReferences and AddNodes service-calls originating from a client, the server-side loading isn’t “user-specific” or something session-access rights would be checked.

Please let us know if this was the case or not, but I think there is high likelihood that this was the issue. Probably our samples should change a bit to account for this possibility in the future (and/or not call the references methods from nodesetloading).