SocketTimeoutException

[Johan Goosen]

Hi all,

In need of some help with a socket timeout exception that keeps showing in the logs. As far as I can tell there is no impact, but this exception is filling up the logs as it repeats every few seconds.

VERSIONS: 

Java amqp-client-5.11.0

RabbitMQ 3.8.22 

Erlang 24.0.5

We are making use of SSL protocol so the UseSllProtocol is set on the ConnectionFactory. 

I've tried setting the SoTimeout on the socket, but it has made no difference. 

Looking at the exception it seems to originate internally inside AMQConnection Main loop thread: 

javax.net.ssl|FINE|57|AMQP Connection 10.128.186.230:5671|2021-11-12 14:47:47.175 SAST|SSLSocketInputRecord.java:214|READ: TLSv1.2 application_data, length = 32

javax.net.ssl|FINE|57|AMQP Connection 10.128.186.230:5671|2021-11-12 14:47:47.175 SAST|SSLSocketInputRecord.java:486|Raw read (

  0000: F8 77 12 49 C4 38 42 15   14 5F A9 F7 EB 50 48 1B  .w.I.8B.._...PH.

  0010: C9 4C 62 52 56 0C F8 1C   37 5D 43 EA E5 AF 77 2A  .LbRV...7]C...w*

)

javax.net.ssl|FINE|57|AMQP Connection 10.128.186.230:5671|2021-11-12 14:47:47.175 SAST|SSLSocketInputRecord.java:247|READ: TLSv1.2 application_data, length = 32

javax.net.ssl|FINE|57|AMQP Connection 10.128.186.230:5671|2021-11-12 14:47:47.175 SAST|SSLCipher.java:1622|Plaintext after DECRYPTION (

  0000: 08 00 00 00 00 00 00 CE                            ........

)

javax.net.ssl|WARNING|57|AMQP Connection 10.128.186.230:5671|2021-11-12 14:48:02.192 SAST|SSLSocketImpl.java:1336|handling exception (

"throwable" : {

  java.net.SocketTimeoutException: Read timed out

  at java.net.SocketInputStream.socketRead0(Native Method)

  at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)

  at java.net.SocketInputStream.read(SocketInputStream.java:171)

  at java.net.SocketInputStream.read(SocketInputStream.java:141)

  at sun.security.ssl.SSLSocketInputRecord.read(SSLSocketInputRecord.java:476)

  at sun.security.ssl.SSLSocketInputRecord.readHeader(SSLSocketInputRecord.java:470)

  at sun.security.ssl.SSLSocketInputRecord.bytesInCompletePacket(SSLSocketInputRecord.java:70)

  at sun.security.ssl.SSLSocketImpl.readApplicationRecord(SSLSocketImpl.java:1151)

  at sun.security.ssl.SSLSocketImpl.access$300(SSLSocketImpl.java:72)

  at sun.security.ssl.SSLSocketImpl$AppInputStream.read(SSLSocketImpl.java:838)

  at java.io.BufferedInputStream.fill(BufferedInputStream.java:246)

  at java.io.BufferedInputStream.read(BufferedInputStream.java:265)

  at java.io.DataInputStream.readUnsignedByte(DataInputStream.java:288)

  at com.rabbitmq.client.impl.Frame.readFrom(Frame.java:91)

  at com.rabbitmq.client.impl.SocketFrameHandler.readFrame(SocketFrameHandler.java:184)

  at com.rabbitmq.client.impl.AMQConnection$MainLoop.run(AMQConnection.java:665)

  at java.lang.Thread.run(Thread.java:748)}

Does anyone have any idea what could be the reason for this exception and what else I can try or investigate? 

Thank you

Johan

[Arnaud Cogoluègnes]

Can you be more specific on your broker configuration? The server logs would be useful as well.

It would be great if you could provide a project and steps to reproduce, using a tool like tls-gen [1] to generate the certificates and keys.

[1] https://github.com/michaelklishin/tls-gen

[Johan Goosen]

Thanks, I will try and get more information. All I know is we initially had Rabbit deployed to Kubernetes and had no issues. This issue started since we moved the broker to Amazon/AWS.