Log In
Register
Forum
Topic RSS
5:12, EET
November 7, 2019
Offline
I’m calling shutdown(), and then later trying to start the server back up with start().
My custom node manager’s init() is being called twice on that second start() call, once from NodeManagerTable.init(), and once from NodeManager.start(), via NodeManagerTable.start().
First, is this something that should work? If so, is this a bug, or do I need to do something differently?
Thanks
Doan
10:39, EET
April 3, 2012
Offline
Hi,
Basically, yes it should work, but I might note that feature/option is somewhat new in the lifetime of the SDK.
The documentation could use some improvements, but do you call super.init() in your override? That will set the initialized field to true. If it is false, the start() will call init() as well (start super will also set the started field as true).
The reason is that on the initial start, managers can be added after the initial UaServer.init() call. This is even what the samples do. There is not much you can do without the call first.
Subsequent starts would usually have the managers already so there would not be need for start to check init status, but given that it is the same code it is what happens.
1 Guest(s)
