You are experiencing reduced Java performance, or Java performance degrades after debugging a message flow

Follow this guidance to resolve the problem of reduced Java performance after debugging a message flow.

Procedure

  • Scenario: The Java™ code in the JavaCompute, the Java user-defined node, or the XSLTransform node does not run as quickly as expected, or performance in these nodes degrades after debugging a message flow.
    This performance degradation might particularly affect the deployment of XML schemas. Other Java based nodes might also experience degraded performance; for example, adapter nodes (SAP, PeopleSoft, JD Edwards, Siebel), SOAP nodes, CORBA nodes, IMS nodes, CICS® nodes and JMS nodes.
  • Explanation: The integration node disables the Java JIT (just-in-time) compiler on the Java virtual machine (JVM) that is created when the integration server is started if you are debugging a message flow. A disabled Java JIT compiler provides a greater choice of debugging options, however any optimizations typically performed during JIT compilation are prevented, which might result in degraded performance.
  • Solution: If you are not debugging a message flow:
    1. Set the JVM debug port to zero using this command:
      mqsichangeproperties integration_node_name -e integration_server_name 
-o ComIbmJVMManager -n jvmDebugPort -v 0
      For example:
      mqsichangeproperties TEST -e default 
-o ComIbmJVMManager -n jvmDebugPort -v 0
    2. Disable flow debugging.