Community
Participate
Working Groups
An SSL failure on the server side should inform the client of what's happened. But in fact, the client connection times out with no information as to why it failed. Simple example: configure the server's launch config with bad paths to its keystore and truststore. When an SSL connection comes in, it'll try to configure the SSLEngine; this will fail immediately, but the client will loop until it times out.
I expect the authors to step up for issues with SSL: * @author Teerawat Chaiyakijpichet (No Magic Asia Ltd.) * @author Caspar De Groot (No Magic Asia Ltd.)
Moving all open issues to 4.2. Open bugs can be ported to 4.1 maintenance after they've been fixed in master.
No activity or ping here for a year. Please reopen this bug if you feel a need.