Camel netty TCP enpoint is causing duplicate messages.

Solution Unverified - Updated -

Environment

  • Red Hat JBoss Fuse
    • 6.1.0

Issue

  • Camel netty TCP enpoint is causing duplicate messages.
  • Attached is the reproducer(camel-spring-netty-test.zip) of the issue which should generate duplicate message on high load.
  • Below is the netty TCP cndpoint configuration:
netty:tcp://localhost:7891?textline=false&autoAppendDelimiter=false&delimiter=NULL&keepAlive=true&synchronous=false&orderedThreadPoolExecutor=false&decoderMaxLineLength=5000&disconnect=true&decoders=#delimiter-based-frame-decoder,#string-decoder&encoder=#string-encoder

Resolution

  • User should create a new unsharable ChannelHandler per channel inside custom delimiter based frame decoder.
  • User can find the JIRA which might be the possible cause of this issue at https://issues.jboss.org/browse/ENTESB-2612.
  • There is attached example(ENTESB-2612.zip) with unsharable ChannelHandler. User can try with this test-case.

Attachments

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.

Comments