After stopping the ESB service locator (tesb-stop-locator), the tesb.log is flooded with exceptions even though no services or routes have the locator feature enabled. How do you stop these warnings, similar to the following, from filling up the Runtime log?
2019-01-11T14:03:59,419 | INFO | pool-35-thread-1-SendThread(xxxxxx:2181) | .zookeeper.ClientCnxn$SendThread 975 | 200 - org.apache.hadoop.zookeeper - 3.4.6 | Opening socket connection to server 0:0:0:0:0:0:0:1/0:0:0:0:0:0:0:1:2181. Will not attempt to authenticate using SASL (unknown error) 2019-01-11T14:04:00,429 | WARN | pool-35-thread-1-SendThread(xxxxxx:2181) | .zookeeper.ClientCnxn$SendThread 1102 | 200 - org.apache.hadoop.zookeeper - 3.4.6 | Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect java.net.ConnectException: Connection refused: no further information at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[?:?] at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717) [?:?] at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) [200:org.apache.hadoop.zookeeper:3.4.6] at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081) [200:org.apache.hadoop.zookeeper:3.4.6]
When the event logging or monitoring is started (tesb:start-el-default or tesb:start-em-default) that internally starts the tesb-locator-monitor bundle which is continuously polling/connecting to the locator, even after the locator was stopped.
If you stop the locator, then also stop the locator monitor, as shown below:
Then restart the Runtime.