Davy If you could give the PR a try and see if it helps I'd be happy to help get it reviewed and in for 1.4 if timing works out.
Thanks On Mon, Sep 18, 2017 at 4:39 PM, Bryan Bende <[email protected]> wrote: > Davy, > > I just pushed a second commit to the PR that will log the port from > the local address of the socket being used by the sender, which I > think is what you mean by the client port. > > If you turn on debug for PutTCP you will see something like... > > o.apache.nifi.processors.standard.PutTCP > PutTCP[id=95463da0-015e-1000-8723-0a2baf6c832f] Connected to local > port 57280 > > I only performed the logging after successful connection because I'm > not sure the ramifications of trying to obtain the local SocketAddress > while finishConnect is still returning false, so I guess the logging > wouldn't really help in the case where the exception was thrown. > > https://github.com/apache/nifi/pull/2159 > > -Bryan > > > On Mon, Sep 18, 2017 at 2:18 PM, ddewaele <[email protected]> wrote: >> Thx a lot for the quick response..... Looking forward to the PR and the >> release :) >> >> Would this for example still make the 1.4.0 release ? >> >> It would also be very interesting to log client ports in debug mode .... >> don't know how easy that is with nio. >> >> There is Keep Alive Timeout = 2min specified on the Moxa, so it means that >> the socket on the client (NiFi) is still responding to "keep alive" packets. >> (makes sense I guess, as we would need to configure some kind of read >> timeout on the moxa to kill off the client). >> >> I guess the fact that we don't see anything in the stack is because the >> socket got established in non blocking mode so it is in ESTABLISHED mode but >> nobody is around to do any processing on it. >> >> >> >> >> >> >> >> >> -- >> Sent from: http://apache-nifi-users-list.2361937.n4.nabble.com/
