Hello Joakim,
I am trying to build Jetty project to run the unit test. However, I am getting error message like
"Tests in error:
ALPNNegotiationTest.testAbruptCloseDuringHandshake:129 » AbstractMethod org.ec...
ALPNNegotiationTest.testClientAdvertisingHTTPServerSpeaksHTTP:191 » AbstractMethod
ALPNNegotiationTest.testClientAdvertisingMultipleProtocolsServerSpeaksHTTPWhenNegotiated:243 » AbstractMethod
ALPNNegotiationTest.testClientNotSupportingALPNServerSpeaksDefaultProtocol:294 » AbstractMethod
ALPNNegotiationTest.testGentleCloseDuringHandshake:70 » AbstractMethod org.ecl..."
I was wondering if the problem is with my SSL set up on my entire server or if it's something else I'm doing wrong?
Here is the test code where the error happens:
SslContextFactory sslContextFactory = newSslContextFactory();
sslContextFactory.start();
SSLEngine sslEngine = sslContextFactory.newSSLEngine(address);
sslEngine.setUseClientMode(true);
ALPN.put(sslEngine, new ALPN.ClientProvider()
{
@Override
public void unsupported()
{
}
@Override
public List<String> protocols()
{
return Arrays.asList("h2");
}
@Override
public void selected(String s)
{
}
});
sslEngine.beginHandshake();
Thanks
From: jetty-dev-bounces@xxxxxxxxxxx <jetty-dev-bounces@xxxxxxxxxxx> on behalf of Joakim Erdfelt <joakim@xxxxxxxxxxx>
Sent: Thursday, October 22, 2015 2:48 PM
To: Jetty @ Eclipse developer discussion list
Subject: Re: [jetty-dev] Class project
First, if you are using the git repository, use one of the stable tags to build from, not the master branch or anything that could be considered "in flux"
Use Maven 3.3.3 (or better)
Your JVM is fine, no change needed.
Our test cases can be very network heavy (for obvious reasons), so if you don't have your file handles or (other ulimits) setup properly you might hit other errors. I can't offer advice on what to set the ulimits up as, as it varys per individual. But
know that if you do have test failures, the details should quickly reveal if its a ulimit issue or not.