apex-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vlad Rozov <v.ro...@datatorrent.com>
Subject Re: Window id got stuck
Date Mon, 08 May 2017 15:28:19 GMT
The exception below means that a downstream operator abruptly 
disconnected. It is not an indication of a problem by itself. Please 
check downstream operator container log for exceptions and error messages.

Thank you,

Vlad

On 5/8/17 07:12, Pramod Immaneni wrote:
> Hi Chiranjeevi,
>
> I am assuming the operator that is upstream and feeding data to this 
> one is progressing properly. What is this operator doing? Is it doing 
> any blocking operations, for example, communicating with some external 
> systems in a blocking fashion? Do you see any other exceptions before 
> the above one you mentioned?
>
> Thanks
>
> On Mon, May 8, 2017 at 3:41 AM, chiranjeevi vasupilli 
> <chiru.vcj@gmail.com <mailto:chiru.vcj@gmail.com>> wrote:
>
>     Hi Team,
>
>     In my use case , one of the operator window id got stuck and after
>     timeout it is getting killed.
>     In the logs we can see
>     [ProcessWideEventLoop] ERROR netlet.AbstractLengthPrependerClient
>     handleException - Disconnecting
>     Subscriber{id=tcp://hostname:57968/323.rsnOutput.1} because of an
>     exception.
>     java.io.IOException: Connection reset by peer
>     at sun.nio.ch.FileDispatcherImpl.read0(Native Method).
>
>     Before container getting , we see the above exception in the logs.
>
>     Please suggest , reasons for window id getting stuck and how to
>     debug it further.
>
>     Thanks
>     Chiranjeevi V
>
>


Mime
View raw message