Use different version of Jetty

[Jigar Patel]

We have developed a highly available and scalable app using DW 0.6.2.
We migrated to DW 0.7.1 about 3 months ago.
Ever since the upgrade we are noticing higher error rate for the client for the RESTFul transaction processing.
It is not easily reproducible. It only occurs at high load and the frequency has gone up since migration to DW 0.7.1.

Is it possible to use different version (not updated version) of Jetty to test it out one the hypothesis of jetty server change.
We want to try out to see if it can be fixed or elevated by using the updated version of libraries without much of a code change.
Again, it is hard to know what is causing the issue at the end.

If you are wondering then we are getting following exceptions on Jersey client (Apache client) . Some of the errors are expected under the load but the frequency has gone up.

org.apache.http.NoHttpResponseException: The target server failed to respond

java.lang.IllegalStateException: Connection pool shut down

java.net.SocketException: Socket closed

java.net.ConnectException: Connection refused

[Artem Prigoda]

Hi, Jigar

I don't think it's possible. We have a compile dependency for Jetty for a
reason. You can try to exclude the dependencies in Maven, but I doubt that
it will work.

Have you tried to check changes in Jetty configuration between 0.6 and 0.7.1?
Especially the parameter idleTimeout? If you use Apache Client with a
connection pool, the pool can contain stale connections already closed by
Jetty. If the client uses a stale connections, an I/O error happens.

By default Apache Client works around it by testing that a connection is stale,
but it's sometimes disabled for performance reason.
Check the client configuration and if errors happen after periods of
inactivity.

Artem