logo标签列表

Wiremock单元测试在本地失败 - java.net.BindException:地址已被使用：JVM_Bind

javaeclipsejunitjenkinswiremock
3

我在项目中使用了Wiremock进行测试，在Jenkins构建时测试通过，但在本地机器上执行时失败，并出现以下错误（Eclipse控制台）：

14:06:17,692  INFO [org.mortbay.log] - Logging to org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via org.mortbay.log.Slf4jLog
14:06:17,751  INFO [org.mortbay.log] - jetty-6.1.26
14:06:17,767  WARN [org.mortbay.log] - failed DelayableSocketConnector@0.0.0.0:62344: java.net.BindException: Address already in use: JVM_Bind
14:06:17,767  WARN [org.mortbay.log] - failed Server@549b6220: java.net.BindException: Address already in use: JVM_Bind
14:06:17,775  INFO [org.mortbay.log] - jetty-6.1.26
14:06:17,776  WARN [org.mortbay.log] - failed DelayableSocketConnector@0.0.0.0:62344: java.net.BindException: Address already in use: JVM_Bind
14:06:17,776  WARN [org.mortbay.log] - failed Server@1c1474ea: java.net.BindException: Address already in use: JVM_Bind
14:06:17,777  INFO [org.mortbay.log] - jetty-6.1.26
14:06:17,778  WARN [org.mortbay.log] - failed DelayableSocketConnector@0.0.0.0:62344: java.net.BindException: Address already in use: JVM_Bind
14:06:17,778  WARN [org.mortbay.log] - failed Server@34c7e8a7: java.net.BindException: Address already in use: JVM_Bind

(Maven)

Tests run: 3, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 0.408 sec <<< FAILURE!
Time elapsed: 0.377 sec  <<< ERROR!
java.lang.RuntimeException: java.net.BindException: Address already in use: JVM_Bind
    at com.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:188)
    at com.github.tomakehurst.wiremock.junit.WireMockClassRule$1.evaluate(WireMockClassRule.java:75)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:76)
    at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
    at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
    at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
    at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
    at org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
    at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
    at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
    at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:35)
    at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:115)
    at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:97)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103)
    at com.sun.proxy.$Proxy0.invoke(Unknown Source)
    at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:150)
    at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:91)
    at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69)
Caused by: java.net.BindException: Address already in use: JVM_Bind
    at java.net.PlainSocketImpl.socketBind(Native Method)
    at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:383)
    at java.net.ServerSocket.bind(ServerSocket.java:328)
    at java.net.ServerSocket.<init>(ServerSocket.java:194)
    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.github.tomakehurst.wiremock.WireMockServer.start(WireMockServer.java:186)
    ... 21 more

我调试代码以检查测试中的错误，但是我无法进行下一步，因为 WireMockClassRule 的创建失败（请参见下面的代码）。

private static int VVS_PORT_MOCK;
static {
    try {
        VVS_PORT_MOCK = (new ServerSocket(0)).getLocalPort();
    } catch (IOException e) {
        //
    }
}

@Rule
public static WireMockClassRule wireMockRule = new WireMockClassRule(VVS_PORT_MOCK);

问题似乎在于端口的动态分配，因为如果我硬编码一个端口值：
 private static int VVS_PORT_MOCK = 8989; //using this it works

所有测试都没有问题（但由于这是单元测试，我试图避免硬编码，因为我想确保测试在任何地方都能通过）。
（我使用netstat检查了分配的端口是否被使用过，但那里没有问题）
我认为这可能与我缺少的某些本地配置有关，但我现在很迷茫。
有什么想法可能会发生什么？
此外，请告诉我是否需要进一步的信息来解决这些问题。
谢谢！
1个回答
5

当你运行方法“getLocalPort()”时，ServerSocket会保留端口。而在代码实例化WireMockClassRule时，端口已经被绑定，导致你所遇到的异常。

你可以将提供的代码块更改为以下内容：

ServerSocket ss = null;
try {
    ss = new ServerSocket(0);
    PORT = ss.getLocalPort();
} catch (IOException e) {
    LOG.error("Socket Exception while opening socket:", e);
} finally {
    try {
        ss.close();
    } catch (IOException e) {
        LOG.error("Socket Exception while closing socket:", e);
    }
}

如果可以使用，请告诉我。

1
这个实际上完美地运行。而且它可以跨平台运行。奇怪的是，这个错误只在Windows上运行时发生。在Unix上它正常工作。但是这个修复使得它在所有环境中都能正确运行。谢谢！ - undefined
网页内容由stack overflow 提供, 点击上面的
可以查看英文原文，
原文链接