You can actually monitor your listeners with some external tools.
Consider visiting Atom web server monitoring for more information
I submitted an idea just for this: Send alerts for JMS and Web Service Listener failures
We've had cases where we happen to be looking at the Atom Management screen and see the red flag for one or a couple listeners.
We have many, many listeners so monitoring each would be ineffective. Does monitoring
http://<host>:<port>/_admin/statushttp://<host><port> return status if some web service (or JMS) listeners have errors? If so, that would be helpful.
Voted for this idea.
What kind of errors are you seeing? Web service listeners are largely passive, there's not much that can "fail" (other than the atom web server failing to start correctly, but that would take down all listeners).
We've had a few cases where individual (or multiple, not all) listeners were not active on at least one of the nodes. Recently, we had a case where the listeners nodes were restarting and a handful of listeners failed to come online, due to NullPointerException thrown from com.boomi.connector.server.ConnectorServerManager.stopConnectorServer().
To resolve, we had to restart the node. Generally, we've never seen any benefit to restarting the listener from Atom Management. If the listener is offline, the only way to get it running is to restart the node.
That sounds like either a bug, or a bad config. Have you followed up with Boomi support?
Srinivas Chandrakanth Vangari
Atom web server monitoring will be helpful to monitor the atom web server status but in our case, it's happening only to few of our web service listener processes and I just see a "null pointer exception" in the error message.
Digging into this a bit, the failures in the web service listeners may be related to some weaknesses with how extensions are applied in the Atom. These weaknesses are on track to be addressed in some near term, upcoming releases.
That said, there are obviously still situations where other listener types can run into problems (e.g. jms listeners losing contact with the jms server).
Sorry if it's too small... screenshot of a screenshot.
Yep, that's the error i looked into.
Retrieving data ...