I’ve been struggling with this problem for a while now and I don’t get what’s happening.
We have several Integration Servers 9.5 Core Fix 7, and they stop for apparently no reason with a JVM Shutdown Hook. They’ve all been started with either “nohup ./server.sh &” or “./startup.sh”, so it shouldn’t be caused by user logoff. We checked that no one called shutdown.sh or kill in the command history.
I don’t understand exactly how the new OSGi based architecture works, but it looks like the tanuki wrapper stops the IS and then dies itself. We then have to restart the IS manually. I can reproduce the behavior by deleting the wrapper.anchor file or by killing the wrapper process for example. From what I see in wrapper.log, these stops aren’t triggered through Command Central, because when I stop an IS with Command Central there’s a line “Anchor file deleted” in wrapper.log, and we see no such line.
Anyone has already been confronted to this situation? What could cause this behavior apart from a manual action?
If someone has good knowledge of the mechanics of the new OSGi based architecture for IS, I’d be very grateful if they could share their insights!