IT12260: IBM MQ EXPLORER STARTS AND REPORTS THE ERROR "MQ EXPLORER NOT INITIALIZED" WHEN ADDING QUEUE MANAGERS

APAR status

• Closed as program error.

Error description

• The MQ Explorer starts, but any attempt to add queue managers or
  import settings will return a "MQ Explorer not initialized"
  error message.
  
  The MQ Explorer log shows:
  
  An unexpected java.lang.StringIndexOutOfBoundsException is
  reported:
  java.lang.ExceptionInInitializerError
      at
  java.lang.J9VMInternals.ensureError(J9VMInternals.java:134)
      at
  java.lang.J9VMInternals.recordInitializationFailure(J9VMInternal
  s.java:123)
      at
  com.ibm.mq.headers.internal.FieldGroup.<init>(FieldGroup.java:47
  )
      ...
  Caused by: java.lang.StringIndexOutOfBoundsException
      at java.lang.String.charAt(String.java:557)
      at
  com.ibm.mq.jmqi.system.internal.JmqiIniFile.processCurrentLine(J
  mqiIniFile.java:371)
  

Local fix

• In the MQ configuration file "mqclient.ini", ensure that any
  value for a name-value configuration pair within a stanza does
  not end in a single backslash character.  If it does, remove the
  trailing backslash, and restart the IBM MQ Explorer.
  
  For example, the following value for the
  ChannelDefinitionDirectory, defined under a CHANNELS stanza,
  denotes a directory and ends in a backslash character:
  
  ChannelDefinitionDirectory=C:\CCDT_DIR\
  
  In this example, remove the trailing backslash to resolve the
  problem:
  
  ChannelDefinitionDirectory=C:\CCDT_DIR
  
  
  Alternatively, add a space character after the backslash
  character.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the:
  
    - IBM MQ classes for JMS
    - IBM MQ classes for Java
    - IBM MQ Explorer
  
  who have configured a mqclient.ini or mqs.ini file which
  contains a value that ends with a backslash character, and there
  are no further characters after the backslash.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When an application uses the IBM MQ classes for JMS, classes for
  Java or the IBM MQ Explorer is started, accessible mqclient.ini
  and mqs.ini configuration files are parsed.  These files are
  text files that can be used to configure some client-side
  behaviour.
  
  While parsing the file, if the parser routine detected a
  backslash character within a configuration value it attempted to
  check the following character to determine if it was used to
  escape a hash/pound symbol, semicolon or another backslash
  character.  However, due to a defect in the calculation of the
  length of the value detected, a
  "java.lang.StringIndexOutOfBoundsException" was thrown when the
  backslash character was the last character on that line of the
  file.
  

Problem conclusion

• The IBM MQ classes for JMS, classes for Java and Explorer have
  been updated to ensure that, when a configuration value that
  ends with a backslash character is detected within the
  mqclient.ini or mqs.ini file, the length of the value is
  calculated correctly.  This ensures there are no further
  attempts to read character from that entry within the file in
  the case where the backslash was the final character on the
  line.  This therefore avoids the
  java.lang.StringIndexOutOfBoundsException being thrown.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.5
  
  The latest available maintenance can be obtained from
  'WebSphere MQ Recommended Fixes'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
  
  If the maintenance level is not yet available information on
  its planned availability can be found in 'WebSphere MQ
  Planned Maintenance Release Dates'
  http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
  ---------------------------------------------------------------
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WMQ BASE MULTIP

• Fixed component ID

  5724H7251

Applicable component levels

• R800 PSY

     UP