Hi, Have you seen that a restart is needed when a new module is installed? I think this is a step back. What do you think?
Yes, hot loading was removed intentionally.
2 Likes
It was a difficult decision to make when we decided to remove hot loading for 8.3.0, but ultimately we decided that we needed to do that.
Hot loading causes all kinds of issues for the Java class loaders, and lead to the kinds of problems where you would need to restart running modules to clear up issues. By having the list of modules known at start up we avoid a lot of potential race conditions and instabilities.
11 Likes
We use the Sepasoft suite, which is 5 modules for us. Will I need to restart after each module update, or just once after updating all? Obviously hoping for the latter.
The latter. Update all then restart.
1 Like
Adding or removing modules is not something that is done on a daily basis, so it is not a problem for me
As @pturmel said, you can add, update, enable, disable, or uninstall as many as you’d like in one go, then restart when you’re ready. The gateway will display a banner which notifies you that some number of module changes are waiting on a Gateway restart, and you’ll be able to perform that restart directly from the banner.
In the following screenshot, I’ve disabled two modules. After a short period, a banner was displayed which informed me that two modules were waiting on a gateway restart. I was also able to hover over a part of the banner to see which modules were due to be affected.
3 Likes