From d4f5689dc761529888c917b81f5e3d3d9ec2f13b Mon Sep 17 00:00:00 2001 From: Marcin Grzejszczak Date: Mon, 2 Jan 2017 11:30:27 +0100 Subject: [PATCH] Documented potential issues with blocked ports with Stub Runner fixes #369 --- spring-cloud-contract-stub-runner/README.adoc | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/spring-cloud-contract-stub-runner/README.adoc b/spring-cloud-contract-stub-runner/README.adoc index 611a3c2290..ea9b185676 100644 --- a/spring-cloud-contract-stub-runner/README.adoc +++ b/spring-cloud-contract-stub-runner/README.adoc @@ -8,6 +8,14 @@ For messaging, special stub routes are defined. ==== Running stubs +===== Limitations + +IMPORTANT: There might be a problem with StubRunner shutting down ports between tests. You might + have a situation in which you get port conflicts. As long as you use the same context across tests + everything works fine. But when the context are different (e.g. different stubs or different profiles) + then you have to either use `@DirtiesContext` to shut down the stub servers, or else run them on + different ports per test. + ===== Running using main app You can set the following options to the main class: