CODEWITHSUNDEEP
netty
Nenad
Nenad

Reputation: 257

Seeing ClosedChannelException after upgrade to Netty 3.2.7

I have a server that acts as a pass-through gateway between a large number of clients and an application server. The gateway uses netty and as far as its behavior is concerned, it simply passes any data received from either end to the other (i.e. from a client to the server and vice versa). The established link (made of two netty channels) between a client and the server is closed if either the client or the server closes its end of the connection... We have been using netty 3.2.4 and have recently upgraded to netty 3.2.7. Since the upgrade we started seeing java.nio.channels.ClosedChannelException while running some volume tests. We did not see any issues with the same kind of tests while we were on 3.2.4.

Does anybody have any idea what might be causing this? I have come across the note from tbocek : see the last post in this link that mentions similar issues. Please help.

Upvotes: 1

Views: 277

Answers (1)

Norman Maurer
Norman Maurer

Reputation: 23567

This was a regression that got fixed in 3.3.0.Final. So consider upgrading to 3.3.1.Final. If you use maven Ou need to change the groupId from org.jboss.netty to io.netty

Upvotes: 1

Related Questions