Join / Log in
IBM Integration Bus v10.0.0.21 was released on 25th June 2020. This is the twenty-first fixpack released for IBM Integration Bus. We provide regular fix packs, approximately once per quarter, a cadence which we intend to continue throughout the year.
This fixpack is primarily a maintenance release but does contain 2 enhancements to help with troubleshooting.
Output current environment variables and java system properties
During the support process we often come across instances where an Integration node running in one environment behaves differently from one running in another environment. This can be explained by a difference in the broker configuration but there are times where the difference is caused by a difference in the environment.
There are a number of environment variables and java system properties that affect behaviour and the value of these variables at the time that the Integration Node was started will be persisted until the Integration Node stops. This means that for example if you were to run the env command on a Unix system to display the current state of the environment this might differ from the values actually being used by an Integration node that had been started some time previously.
To help with comparing the environment the command mqsichangeproperties has been enhanced so that it can cause an integration server to output its current set of values for both environment variables and Java system properties. The command can be invoked with the following syntax:
mqsichangeproperties myNode -e myServer -o ComIbmInternalSupportManager/Java/JVM -n dump -v env
The output is written to $MQSI_WORKPATH/common/errors and files have the extension .envdump
The output is alphabetically sorted to make it easy to view differences in a standard diff editor. A portion of example output is shown below:
FlowThread Reporter output to CSV file
The FlowThread Reporter was introduced in fixpack 10.0.0.12 and provides a way to capture a snapshot of what processing is currently happening for every MessageFlow thread in an Integration Server. The output from this command is quite verbose and is displayed on the command console. To help make this information more usable the FlowThread Reporter has been enhanced to write a subset of information to CSV files to make it easier to interpret data.
The command can be invoked using the following syntax:
mqsireportproperties myNode -e myServer -o FlowThreadReporter/CSVTime -r
An example of the output is displayed below:
Figure 1. Flowthread reporter CSV output
Additionally the FlowThread Reporter can now be invoked using the “direct deploy” style of mqsireportproperties invocation. This version of the command is particularly useful when there is an in flight deploy that is blocking the processing of a Flowthread Reporter request. In these instances the culprit is usually a message flow thread which is stuck in a synchronous wait on a back end system, such as an HTTPRequest Node with a long timeout. Previously it would not have been possible to diagnose which node was responsible using the FlowThread Reporter. The direct deploy version of the command can now be used and the the FlowThread Reporter will not have to wait for the pending configuration message to complete.
The direct deploy invocation can be made using the following syntax:
mqsireportproperties myNode -e myServer -x
The fix list contains more details about issues resolved by this maintenance release.