I think adding the handling is the first thing to do, if this freaks out
someone who knows what they are doing, what will it do to someone new to
the project?
Also, maybe the drivers will need a quirks mode?
On April 12, 2019 at 09:26:25, Christofer Dutz (christofer.d...@c-ware.de)
wrote:
Hi
Hi Otto,
when inspecting the TCP traffic, for example Siemens LOGO devices tend to just
hang up without sending a TCP ack if they get something they don't like.
It's not TCP compliant, but it's the way they roll :-(
So I know when trying to access a LOGO device with the S7 protocol, I had to
I would think you’d want to handle it, and then investigate the reason for
it in this instance
On April 12, 2019 at 08:51:05, Christofer Dutz (christofer.d...@c-ware.de)
wrote:
Hi Otto,
I think the English translation would be something like:
"Connection reset by remote" or "Connection reset
Hi Otto,
I think the English translation would be something like:
"Connection reset by remote" or "Connection reset by peer"
Not sure if this helps understand what's going on ... I always thought it was
related to
the PLC hanging up without following the correct procedure for doing that. Sort
Oh .. I must apologize to you Julian,
Sitting in yet another meeting and viewing emails on my phone isn't that ideal.
What I saw reminded me to normal log output, but after Otto's comment I had
another look ... You are absolutely right ... We should fix that.
Unfortunately I'm a little lost
Maybe all the streams aren’t getting closed correctly?
On April 12, 2019 at 07:52:04, Otto Fowler (ottobackwa...@gmail.com) wrote:
An exceptionCaught() event was fired, and it reached at the tail of the
pipeline. It usually means the last handler in the pipeline did not handle
the exception.
The netty handlers don’t implement exceptionCaught so the default is to
spew to logs. I don’t speak german so I don’t know what the exception
message is.
Maybe the handlers should implement the method.
On April 12, 2019 at 04:56:40, Julian Feinauer (j.feina...@pragmaticminds.de)
wrote:
An
But that's not the way you handle logging.
Logging frameworks are built to allow analysis and turn on and off this parts
interesting to me as a user. The way you define what you want is by configuring
the logging.
Staying by your car example:
Probably you didn't leave the volume of the stereo
Hi Chris,
well.. thats like the handling procedure if you have an unknown noise in your
car... turn the radio louder __
In this case, I wanted to delete the curse not mute the logs... as It sounds
for me this is a issue to be addressed.
Julian
Am 12.04.19, 11:01 schrieb "Christofer Dutz" :
You could increase the log-level ... should reduce the amount of logging
drastically.
Chris
Am 12.04.19, 10:56 schrieb "Julian Feinauer" :
Hi all,
as many of you may know, we use PLC4X pretty heavily in Prod.
We recently checked our logs and found a lot of entries from PLC4X
Hi all,
as many of you may know, we use PLC4X pretty heavily in Prod.
We recently checked our logs and found a lot of entries from PLC4X which are
thrown although everything is working.
This is something I want to fix (if theres no issue then be silent).
We use the S7 driver, but I think this is
11 matches
Mail list logo
