IBM Support

Using MDM Kafka based notification with IBM JDK v8 SR4

Troubleshooting


Problem

Issues running out of the box Kafka v0.10.2.1 bundled with MDM and IBM JDK v 8.0 SR4

Symptom

(i) Minor issue : IBM JDK gc logging setting is not compatible
(ii) Major issue : Zookeeper and Kafka server crashes

Cause

Thirdparty: Issue with IBM JDK v8 SR4

Resolving The Problem

(i) User needs to provide verbose logging option in their corresponding Kafka package
Open the following file in any editor : KAFKA_HOME\bin\kafka-run-class.sh
search for "GC options"
update value of KAFKA_GC_LOG_OPTS like below and save the file
KAFKA_GC_LOG_OPTS="-Xverbosegclog:$LOG_DIR/$GC_LOG_FILE_NAME -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps "

(ii) User needs to disable JIT using one command(Xnojit) but this can trigger slow performance.
Open the following file in any editor : KAFKA_HOME\bin\kafka-run-class.sh
search for "GC options"
update value of KAFKA_GC_LOG_OPTS like below and save the file.
KAFKA_GC_LOG_OPTS="-Xverbosegclog:$LOG_DIR/$GC_LOG_FILE_NAME -Xnojit -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+PrintGCTimeStamps "

The fix to issue (ii) for JIT has been released with IBM JDK v 8.0 SR5

[{"Product":{"code":"SSWSR9","label":"IBM InfoSphere Master Data Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"--","Platform":[{"code":"PF016","label":"Linux"}],"Version":"11.6.0.3","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
27 April 2022

UID

swg22008222

Page Feedback