nifi-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bryan Bende <bbe...@gmail.com>
Subject Re: PutTCP connector not cleaning up dangling connections
Date Wed, 20 Sep 2017 16:41:36 GMT
Sounds good, interested to hear about it when you get a chance.

On Wed, Sep 20, 2017 at 12:32 PM, Davy De Waele <ddewaele@gmail.com> wrote:
> Having dinner now without laptop :) Have more updates. Isolated the problem
> in the puttcp class in the processor. Rest of the 1.4.0-snapshot seems fine.
>
> Will post more info after dinner.
>
> On Wed, 20 Sep 2017 at 18:27, Bryan Bende <bbende@gmail.com> wrote:
>>
>> Is the data good at other points in the flow before getting to PutTCP?
>>
>> If you are seeing those bytes in provenance, then they would have to
>> be in there before reaching PutTCP, because PutTCP doesn't modify the
>> content of the flow file.
>>
>> So I'm thinking something else in the flow before PutTCP is working
>> differently than before.
>>
>> On Wed, Sep 20, 2017 at 4:38 AM, ddewaele <ddewaele@gmail.com> wrote:
>> > Small update : No garbage / noise on 1.3.0 also so it must be in
>> > 1.4.0-SNAPSHOT.
>> >
>> > Noticed that the PutTCP processor has changed the way it processes
>> > incoming
>> > flowfiles. Might be related to that.
>> >
>> > Looked into the data provenance and noticed  3 bytes EF BF BD (in hex)
>> > when
>> > things go bad. (This seems to be the utf-8 encoding of the Unicode
>> > character
>> > U+FFFD REPLACEMENT CHARACTER.)
>> >
>> > So I'm guessing some kind of encoding / charset issue.
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> >
>> > --
>> > Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/

Mime
View raw message