carylu created TUBEMQ-316:
-----------------------------

             Summary: Where the port has aleady been used, the process throw 
the exception, but not exit;
                 Key: TUBEMQ-316
                 URL: https://issues.apache.org/jira/browse/TUBEMQ-316
             Project: Apache TubeMQ
          Issue Type: Bug
          Components: Broker, Master
            Reporter: carylu


When starting broker or master .If the port has aleady been used, the process 
throw the exception, but not exit. It should be exit when the port has already 
been used;

Here are the exceptions:

[WARN] 2020-08-14 13:10:06,900 [log] failed [email protected]:8081: 
java.net.BindException: Address already in use (Bind failed)
[WARN] 2020-08-14 13:10:06,900 [log] failed Server@17baae6e: 
java.net.BindException: Address already in use (Bind failed)
[WARN] 2020-08-14 13:10:06,901 [ZkOffsetStorage] Thread terminated with 
exception: main
java.net.BindException: Address already in use (Bind failed)
 at java.net.PlainSocketImpl.socketBind(Native Method)
 at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
 at java.net.ServerSocket.bind(ServerSocket.java:375)
 at java.net.ServerSocket.<init>(ServerSocket.java:237)
 at java.net.ServerSocket.<init>(ServerSocket.java:181)
 at 
org.mortbay.jetty.bio.SocketConnector.newServerSocket(SocketConnector.java:80)
 at org.mortbay.jetty.bio.SocketConnector.open(SocketConnector.java:73)
 at org.mortbay.jetty.AbstractConnector.doStart(AbstractConnector.java:283)
 at org.mortbay.jetty.bio.SocketConnector.doStart(SocketConnector.java:147)
 at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
 at org.mortbay.jetty.Server.doStart(Server.java:235)
 at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)
 at com.tencent.tubemq.server.broker.web.WebServer.start(WebServer.java:49)
 at com.tencent.tubemq.server.broker.TubeBroker.<init>(TubeBroker.java:136)
 at com.tencent.tubemq.server.tools.BrokerStartup.main(BrokerStartup.java:27)



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to