title: Integration tests with WireMock failing because no ALPN Processors are found
body: <p>I'm writing some integration tests for a Spring Boot application written in Kotlin. To stub some HTTP requests, I'm using WireMock via <code>spring-cloud-contract-wiremock</code> as dependency.</p>
  <p>Some anonymized sample code from an integration test:</p>
  <pre class="lang-java prettyprint-override"><code>@SpringBootTest
  @AutoConfigureMockMvc
  @AutoConfigureWireMock
  class MyIntegrationTest { 
  
      @Test
      fun `some test`() {
          mockEndpoint(&quot;url&quot;, 500, someResponseBodyInJson)
  
          mockMvc.perform(
              MockMvcRequestBuilders
                  .post(&quot;url&quot;)
                  .contentType(MediaType.APPLICATION_JSON.toString())
                  .content(someRequestBodyInJson)
          )
              .andExpect(MockMvcResultMatchers.status().isInternalServerError)
      }
  
      private fun mockEndpoint(url: String, responseCode: Int, responseBody: String) {
          stubFor(
              WireMock.post(url).willReturn(
                  WireMock.aResponse()
                      .withStatus(responseCode)
                      .withHeader(HttpHeaders.CONTENT_TYPE, MediaType.APPLICATION_JSON.toString())
                      .withBody(responseBody)
              )
          )
      }
  
  }
  </code></pre>
  <p>While running these tests on my local machine, everything is working fine. On the CI/CD environment it's failing though with the following error:</p>
  <pre><code>java.lang.IllegalStateException: No Server ALPNProcessors!
  at wiremock.org.eclipse.jetty.alpn.server.ALPNServerConnectionFactory.&lt;init&gt;(ALPNServerConnectionFactory.java:52)
  </code></pre>
  <p>I did some searching and figured out is has to do with Jetty missing some things on the class path. I added the following dependency <code>testImplementation(&quot;org.eclipse.jetty:jetty-alpn-server:11.0.7&quot;)</code>, but the tests are still failing. The <code>alpn-boot</code> extension should not be necessary as JDK 11 is being used.</p>
  <p>Anyone able to help me solve this? Do I need another dependency or am I looking in the wrong direction?</p>