PR 822 can handle base netty timeout very well. But CachedConnection should have it's own timeout handle
This is not the same. Most of the connection problems are caused by the base netty connection that not deal bery well. @Łukasz Dywicki have fixed response timeout problem。 Like I pointed out on the https://github.com/apache/plc4x/issues/801 issue, there are other netty connection issues that cause unpredictable errors Łukasz Dywicki <[email protected]> 于2023年3月17日周五 19:25写道： > Hey Chris, > We do have one, fairly basic Plc4xNettyWrapperTest which covers timeout > handling. The PR I made https://github.com/apache/plc4x/pull/822 was > spotted by this test and showed that we had behavior change. > > One thing which I still haven't found answer to is how to bind lifecycle > of timeout manager with connection and how to let end user pass external > timeout manager into driver (so he can centrally track degraded > operations). > > Best, > Łukasz > > On 17.03.2023 08:09, Christofer Dutz wrote: > > Hi all, > > > > I would like to address the timeout handling in our Java driver core > next. > > Unfortunately, I am a bit unsure how to address that. > > Usually, I would whip up a Unit-Test that causes the error and then to > fix it. > > > > However, I don’t quite know how to produce the problem that people are > describing. > > > > Would anyone here be able to assist me with at least that? I’m happy to > do the fixing. > > I just feel uncomfortable just swapping some code out with random other > code. > > > > > > Chris > > > > >
