Question & Answer
Question
We would like to enable verbose garbage collection in the IBM InfoSphere Master Data Mangement Standard Edition to collect additional diagnostic information about the JVM runtime. How do we enable that?
Cause
Enabling verboseGC output is often required when diagnosing issues with the Java Virtual Machine. Verbose garbage collection is enabled at the JVM container/wrapper level using JVM tuning parameters. Before v-11, MDS ran within a Tanuki Software java wrapper whereas from v-11 onwards, it runs within WebSphere Application Server. The following section describes how to enable verboseGC output in either version.
Answer
Before version-11, the method to enable garbage collection was as follows:
1. Go to $MAD_HOMEDIR/inst/mpinet_<InstanceName>/conf directory and open wrapper.conf file for editing.
2. Add the following parameter in the wrapper.conf configuration file where x is the number of next available additional parameter e.g. x is 8 is 7 other additional parameters are already configured:
wrapper.java.additional.x=-verbose:GC
3. Restart the engine.
Version-11 onwards, the process is:
1. Log into the Administrative Console, expand Servers, expand Server Types, and then click WebSphere application servers.
2. Click on the server where the MDM eba is deployed, for example, server1 or MDM-s-01.
3. On the Configuration tab, under Server Infrastructure, expand Java and Process Management, and click Process Definition.
4. Under the Additional Properties section, click Java Virtual Machine.
5. Check the Verbose Garbage Collection check box.
6. Apply and Save the changes.
7. Restart the Application Server for the changes to take effect.
The verboseGC output will be written to the following file by default: native_stderr.log.
Product Synonym
MDS;Master Data Service;MDM;MDMSE;Master Data Management;IBM Infosphere Master Data Service;MDM Standard Edition;MDM Hybrid Edition
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21681969