DDLV4MessageFB exeption if the message is to long!

[PKlein]

Hello,

we have a problem when we receive an OpconXml telegram which is larger than the defined buffer.

Then we get an exeption of the DDLV4MessageFB out of the NxIpDdl 1.2.11.0 (liberay version 1.2.9.0)

Sometimes the MES error messages or feedback have different lengths. This leads to exceptions occurring within production. This leads to a significant risk in production! This error is a very critical error, so please take care of it as soon as possible.

Why didn't I open a ticket: To inform other colleagues who may have the same problem/error.

You are also welcome to contact me directly. Example telegrams are available.

[sutrus]

I don't really understand, but why don't you resize the Buffer?
For each telegram tab Common change the Buffer size.

[PKlein]

Some times is it not possible to know the correct buffer size of the event. because they send us some time very long informations:

And Yes, we have a  definition that the trace should be 80 or no 255 digits. Or what? How cares?

In the end, we can discuss a lot about the right sizes and a lot has already been said about that.

But....

If we have the event text at the objects? Why not use? Better an exception and know body knows what happens?

[PKlein · Accepted solution]

After detailed investigation, it is not entirely clear that it is due to the buffer size.

I need some support! Thanks!

[PKlein · Accepted solution]

The Problem is not the DDLV4MessageFB! It is an internal Bug!