IBM integrations

Known issues

At the time of release, there is known issue that you should be aware of when running the probe.

This section covers the following known issue:

Shutting down the probe
There is a known issue of potentially corrupting the recovery file if you use Control-C or PA to shut down the probe. The current workaround is to use the shutdown_probe command to shut down the probe.
Probe does not respond to log files stored on shared drive or mounted disk when appended on another server
The probe does not work if the log file is stored in on a shared directory and is then modified by another server (one on which the probe is not running).
Probe cannot be run with commands that parse an empty parameter on Windows
There is a known Windows limitation whereby a command cannot be parsed if it contains an empty parameter.
Probe cannot be run with -recoveryfile '' in command line on Windows
On Windows, if you set the -recoveryfile option to '' when running the probe, the recovery file function is not disabled.
Master probe re-sends events sent by the slave probe
When running in peer-to-peer failover mode, the master probe re-sends the events sent by the slave probe when it was down, based on its recovery file pointer.
Probe cannot start on RHEL 7.7 or 8.0
There is a known issue with this probe whereby the probe cannot start on RHEL 7.7 or 8.0.
Camel message not applicable
log4j WARN message written to the log file.

Parent topic: Generic Log File Java