CODEWITHSUNDEEP
nettyactivemq-artemis
IngeniouSeven
IngeniouSeven

Reputation: 43

What might be causing these warning exceptions in my Artemis service logs?

I'm seeing a lot of these warnings in my Artemis server logs and I'd like to understand what is triggering them? 

[io.netty.channel.DefaultChannelPipeline] An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception.: io.netty.channel.unix.Errors$NativeIoException: syscall:read(..) failed: Connection reset by peer

The only things I've tried is to understand the origin of the issue.

This is from within Artemis server code.

Upvotes: 0

Views: 472

Answers (1)

Justin Bertram
Justin Bertram

Reputation: 34988

The root issue is the "Connection reset by peer" which is explained in this Stack Overflow answer. ActiveMQ Artemis is simply logging that the connection was reset. There's nothing it can actually do about it.

I recommend you investigate the clients accessing the broker as well as the network between them all to ensure they are operating properly.

Upvotes: 1

Related Questions