Issues raised for tomcat servered HTTP Dubbo service

[jun liu]

Hi, all

Here is the Github issue: https://github.com/apache/incubator-dubbo/issues/3236

I developed one HTTP service using Dubbo. I tried to start two provider 
processes on the same machine with the same port. The second provider process 
failed because of port conflict which is an expected behaviour. What confused 
me is that the conflict error did not interrupt the exporting process of Dubbo, 
the HTTP service URL was successfully registered to the Registry, no doubt any 
Consumer that find and try to consume this URL would fail. So we should find 
the reason why we are not interrupted by tomcat socket binding error:
 
      try {
            tomcat.start();
        } catch (LifecycleException e) {
            throw new IllegalStateException("Failed to start tomcat server at " 
+ url.getAddress(), e);
        } catch (Exception ee) {
            throw new IllegalStateException(e);
        }


Jun