Hello Nick,
I'm not able to reproduce all your problems.
I've generated a certificate following the Jetty's instructions and I
use this code :
**********************************************************************************************
component.getContext().getParameters().add(new Parameter("type",
"2"));
component.getContext().getParameters().add(new
Parameter("keystorePath", keystoreFile.toURI().toASCIIString()));
component.getContext().getParameters().add(new
Parameter("keystorePassword", "password"));
component.getContext().getParameters().add(new
Parameter("keyPassword", "password"));
component.getServers().add(Protocol.HTTPS, 8182);
component.getDefaultHost().attach("", app);
component.start();
**********************************************************************************************
I switch the "type" parameter in order to use NIO (1) or BIO (2). Am I
wrong?
When using BIO :
- if I provide wrong passwords, the server crashes when starting.
- if I provide right passwords, Jetty send a weird file with odd
characters for every request.
When using NIO :
- if I provide wrong passwords, the server loops when starting,
because of NullPointerExceptions that seem to be badly managed.
- if I provide right passwords, the server hangs, but I don't know if
it is the consequence of my request, of if the server is stille starting.
Best regards.
Thierry Boileau
Nick a écrit :
Jerome, I only get this problem with the NIO connector, the other one seems ok.
I think this is a problem with the stability of jetty 6.1 NIO SSL connector.
