When I started working on scala I had a tough time understanding how exception handling works in scala. I had some background in java and javascript and I had exclusively worked with imperative codebases till that time.
When I look back I think my understanding about exception handling in scala came in stages: In the first stage I figured out what are the different ways of exception handling in scala. After this stage I knew what are different ways but I had a difficult time using those appropriately. During this time I started asking questions: Why do we need more than…
Recently I faced below error in my play application. My play application was trying to hit a server over https.
{"errors":[{"code":"General SSLEngine problem","message":"java.net.ConnectException: General SSLEngine problem\n\tat org.asynchttpclient.netty.channel.NettyConnectListener.onFailure(NettyConnectListener.java:162)\n\tat org.asynchttpclient.netty.channel.NettyConnectListener$1.onFailureThis exception occurred because the keystore used by play application did not have server’s certificate loaded. The server’s certificate in keystore tells the client (here my play application) to trust the https connection. Since server’s certificate was missing in keystore used by client, the above exception occurred. This problem can be fixed by adding server’s certificate in the keystore used by your play application. By default play application uses keystore ${java.home}/lib/security/cacerts …
Ashwini Anand
Software Engineer.
