Hi, We use the embedded jetty proposed by CXF in our project's integration tests. Those are in the form of Junit tests and wired by Spring (and launched by maven surefire plugin) Tested JAX-WS web services are deployed on the embedded jetty and accessed through a JAX-WS client also provided by CXF.
Now that our maven project has several modules that uses that feature, we randomly get "read timed out" errors during our tests (the stack trace is given at the end of this post). The thing is that this is really random and looks to happen only when several modules are launched in a row. The tests in the first module run well and when it switches to the next modules, we sometimes get the timeouts in those next modules. We tried different things to workaround this issue but without success so far: - Increasing client and server timeout values - Setting "org.apache.cxf.transports.http_jetty.DontClosePort" to true following this post: http://camel.465427.n5.nabble.com/Issue-using-camel-cxf-in-an-unit-test-td5718310.html <http://camel.465427.n5.nabble.com/Issue-using-camel-cxf-in-an-unit-test-td5718310.html> => Didn't work, but surefire forks a jvm for each module in our case and that workaround seems to be related to tests running in the same JVM - Assigning random http ports to jetty => Didn't work even when the port is different from one module to another, we still randomly get timeouts... - Activating DEBUG logs on "org.eclipse.jetty" and "org.apache.cxf", but we've seen nothing relevant (logs look similar until the timeout comparing a run that goes well and another that times out) We are running out of ideas while our continuous builds keep failing randomly... :-( Any idea or help about that issue would be gladly appreciated. Version of CXF used: 2.3.9 Thanks in advance, Vincent -- View this message in context: http://cxf.547215.n5.nabble.com/Embedded-jetty-Could-not-send-Message-Read-timed-out-tp5730168.html Sent from the cxf-user mailing list archive at Nabble.com.
