Hi,

Please clarify what you mean, but some assumptions: I’ll take this has nothing to do with OPC UA PubSub (you mentioned “publishing” but also “client”). Thus either you mean stop listening to incoming connections and/or a way to close the socket connection between a client and the server?

IF you instead meant PubSub, you should be able to do PubSubSystem.shutdown without shutting down the UaServer. Though it should be noted that we are aware of some issues regarding PubSub, in some cases you might need to currently make a new PubSubSystem, but the intention anyway would be to just be able to PubSubSystem.start it again.

As to closing a Session from within the server. In short it may be possible (but not tried that I can remember) currently by a lot of subtyping UaServer and related components, but there is no intended public-API to do so . In short you kinda do not do that in OPC UA. Though this has been asked at least once before we do have it somewhere in our very big TODO-list. The one possible use-case could be IF a user is removed completely it might be desired to close the session. But basically in all other cases the clients would just try to immediately open the connection again (and they would do so here as well).

For the stopping listening incoming connections, not really a way, but I’m not 100% sure what you mean. However, it is possible that you would be looking for UaServer.shutdown(int secondsTillShutdown, String shutdownReason, boolean closeServer) and using false for the last parameter. From the javadocs “… * @param closeServer determine whether the server is also closed at the same. Use ‘false’ if you
* intend to restart the server again, by calling {@link #start()}. It will leave the node
* managers intact, and they will not need to be re-initialized. Default is true. …”

If that didn’t help, I would need more clarifications on what you mean?