A newer version of this document is available. Customers should click here to go to the newest version.
Checking Message Transmission
For each application message, another extra message is sent which includes:
Data type signature hash code (for GLOBAL:MSG:DATATYPE:MISMATCH)
Checksum of the data (for GLOBAL:MSG:DATA_TRANSMISSION_CORRUPTED)
Stack backtrace for the place where the message was sent (for both of these errors and also for GLOBAL:MSG:PENDING)
Only disabling of all of these three errors avoids the overhead for the extra messages.
Buffered messages which are not received lead to a resource leak. They are detected each time a communicator is freed or (if a communicator does not get freed) when the application terminates.
The information provided includes a call stack of where the message was sent as well as the current call stack where the error is detected.
Did you find the information on this page useful?