camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "edge wang (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5225) camel-netty can't distinguish between Sharable and Unsharable codecs
Date Fri, 27 Apr 2012 17:10:50 GMT


edge wang commented on CAMEL-5225:

Here is the correct testcase and the patch to pass the testing. The patch simply creates a
new decoder(by hard coding that matches the testcase) each time when getpipeline is called,
when you run the testcase against patched 2.9.1 version of cammel-netty, you get it passed,
but not for 2.9.2 and 2.10.
> camel-netty can't distinguish between Sharable and Unsharable codecs
> --------------------------------------------------------------------
>                 Key: CAMEL-5225
>                 URL:
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-netty
>    Affects Versions: 2.9.2
>         Environment: ALL
>            Reporter: edge wang
>            Assignee: Claus Ibsen
>              Labels: netty
>             Fix For: 2.10.0
>         Attachments:,,
> Camel-netty uses general configuration model for referenced encoders/decoders for channel
pipelines, see DefaultServerPipelineFactory. That is, create encoder/decoder objects at configuration
parsing time and store them in a list, then use them when a pipeline is established. However,
this will make encoder/decoder objects shared among different pipelines, that may cause data
conflicts, when the encoder/decoder is not Sharable(has object status/not annotated as @Sharable),
e.g. a LengthFieldBasedFrameDecoder.
> Although we can avoid the problem by totally writing a new serverpipelinefactory for
our apps, several problem still remains, please see detailed description and testcase for
this bug at:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message