tions in other usage-patterns worse?
> >
> > I think if we work on stuff like this, we should sort of start
> implementing tests.
> >
> > Chris
> >
> > Von: Cesar Garcia
> > Datum: Freitag, 17. März 2023 um 18:03
&
work on stuff like this, we should sort of start implementing
tests.
Chris
Von: Cesar Garcia
Datum: Freitag, 17. März 2023 um 18:03
An: dev@plc4x.apache.org
Betreff: Re: Trying to fix the timeout issues ...
Hello everyone,
For the S7HA version I used a different path for the timeout implement
@plc4x.apache.org
Betreff: Re: Trying to fix the timeout issues ...
Hello everyone,
For the S7HA version I used a different path for the timeout implementation.
/ NIOChannel B
PLC4X -> EmbeddedChan
Hello everyone,
For the S7HA version I used a different path for the timeout implementation.
/ NIOChannel B
PLC4X -> EmbeddedChannel ->
\ NIOChannel A
Channels A and B have timeout monitoring (
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 ou
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 time
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
describin
