issues with socket
>>>>>>> handling. But had not seen it on Java 11 though may be possible. Is
>>>>>>> there a full stack trace?
>>>>>>>
>>>>>>> On Sat, May 29, 2021 at 12:00 PM Robert R. Bruno
>>>>>
2021 at 12:00 PM Robert R. Bruno
>>>>>> wrote:
>>>>>>
>>>>>>> We upgraded to java 11 when we upgrade to 1.13.2 we were on java 8
>>>>>>> with 1.9.2.
>>>>>>>
>>>>>>> On Sat, May 29, 2021, 14:
13.2 we were on java 8
>>>>>> with 1.9.2.
>>>>>>
>>>>>> On Sat, May 29, 2021, 14:21 Joe Witt wrote:
>>>>>>
>>>>>>> What JVM are you using?
>>>>>>>
>>>>>>> Thanks
>>>>>
; wrote:
>>>>>>
>>>>>>> Not related to Nifi, but I faced the same type of issue for
>>>>>>> endpoints behind a proxy which takes more than 30 seconds to answer.
>>>>>>> Fixed
>>>>>>> by replacing
>>>>> gardellajuanpa...@gmail.com> wrote:
>>>>>
>>>>>> Not related to Nifi, but I faced the same type of issue for endpoints
>>>>>> behind a proxy which takes more than 30 seconds to answer. Fixed by
>>>>>> r
d not investigate further,
>>>>> just
>>>>> simply replaced one library by another and the error was fixed.
>>>>>
>>>>>
>>>>> Juan
>>>>>
>>>>> On Sat, 29 May 2021 at 15:08, Robert R. Bruno
>&
t;> Juan
>>>>
>>>> On Sat, 29 May 2021 at 15:08, Robert R. Bruno
>>>> wrote:
>>>>
>>>>> I wanted to see if anyone has any ideas on this one. Since upgrading
>>>>> to 1.13.2 from 1.9.2 we are starting to see broken pipe
>>
>>>
>>> Juan
>>>
>>> On Sat, 29 May 2021 at 15:08, Robert R. Bruno wrote:
>>>
>>>> I wanted to see if anyone has any ideas on this one. Since upgrading
>>>> to 1.13.2 from 1.9.2 we are starting to see broken pipe (write
ixed.
>>
>>
>> Juan
>>
>> On Sat, 29 May 2021 at 15:08, Robert R. Bruno wrote:
>>
>>> I wanted to see if anyone has any ideas on this one. Since upgrading to
>>> 1.13.2 from 1.9.2 we are starting to see broken pipe (write failed) errors
>>
ng to
>> 1.13.2 from 1.9.2 we are starting to see broken pipe (write failed) errors
>> from a few invokeHttp processers.
>>
>> It is happening to processors talking to different endpoints, so I am
>> suspecting it is on the nifi side. We are now using load balanced queues
May 2021 at 15:08, Robert R. Bruno wrote:
> I wanted to see if anyone has any ideas on this one. Since upgrading to
> 1.13.2 from 1.9.2 we are starting to see broken pipe (write failed) errors
> from a few invokeHttp processers.
>
> It is happening to processors talking to different
I wanted to see if anyone has any ideas on this one. Since upgrading to
1.13.2 from 1.9.2 we are starting to see broken pipe (write failed) errors
from a few invokeHttp processers.
It is happening to processors talking to different endpoints, so I am
suspecting it is on the nifi side. We
12 matches
Mail list logo
