cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Mobile Application: How to interpret this SSLException

Hi,

We see a lot of SSLExceptions for our Android App.

Having a deeper look it seems that not specific users are affected but sometimes a user gets this error and all the other requests seem to be fine even the same request is fine the next time it is executed. This seems to be kinda weird behaviour for this kind of Exception. It looks more like a Timeout or something like that. Did somebody else experience errors like this?

regards,

Gerald

4 REPLIES 4

andreas_grabner
Dynatrace Leader
Dynatrace Leader

I agree. Looks like a strange error. I guess there are no more details you get on that exception? no stack trace?

Hi Andi,

I found an Exception:

javax.net.ssl.SSLException: Read error: ssl=0x786a6398: I/O error during system call, Connection reset by peer near/at com.android.org.conscrypt.NativeCrypto.SSL_read:-2

at com.android.org.conscrypt.NativeCrypto.SSL_read(Native Method)
at com.android.org.conscrypt.OpenSSLSocketImpl$SSLInputStream.read(OpenSSLSocketImpl.java:745)
at java.io.BufferedInputStream.read(BufferedInputStream.java:283)
at com.android.okhttp.internal.http.UnknownLengthHttpInputStream.read(UnknownLengthHttpInputStream.java:39)
at java.io.InputStream.read(InputStream.java:162)
at java.io.BufferedInputStream.fillbuf(BufferedInputStream.java:142)
at java.io.BufferedInputStream.read(BufferedInputStream.java:288)
at java.io.InputStream.read(InputStream.java:162)
at at.threebeg.mbanking.service.WebServiceProvider.WebServiceProvider.post(Unknown Source)
at at.threebeg.mbanking.service.WebServiceProvider.WebServiceProvider.query(Unknown Source)

There is a nice StackOverflow article on this

http://stackoverflow.com/questions/30538640/javax-net-ssl-sslexception-read-error-ssl-0x9524b800-i-o-error-during-system

So it seems that it really could be a timeout.

regards,

Gerald

Thanks for the update. Yeah - connection reset by peer definitely means that the connection was shut down by the other party. could be a timeout! or an overloaded backend