Currently, the status lines come from parsing the config.xml file when it's deployed, which is usually accurate, but doesn't necessarily reflect the true "listening on port" status if there's an error starting the server. More accurate would be to implement a Liberty feature that tracks the endpoint MBeans and updates the status lines there.
This would be most safely done in cooperation with the server process itself. Perhaps it would be best to establish a message queue in the Domino side and then have individual servers push into that. That way, if the Liberty server dies, it won't leave a status line hanging open.
Currently, the status lines come from parsing the config.xml file when it's deployed, which is usually accurate, but doesn't necessarily reflect the true "listening on port" status if there's an error starting the server. More accurate would be to implement a Liberty feature that tracks the endpoint MBeans and updates the status lines there.
This would be most safely done in cooperation with the server process itself. Perhaps it would be best to establish a message queue in the Domino side and then have individual servers push into that. That way, if the Liberty server dies, it won't leave a status line hanging open.