IT19413: FDC files in WebSphere Application Server with probe ID 'XS001002' on z/OS

APAR status

• Closed as program error.

Error description

• A IBM MQ classes for JMS application is running within the
  WebSphere Application Server v9.0 environment where the IBM MQ
  Resource Adapter had been updated from a MQ v9.0 installation on
  z/OS, and FDC files are generated with the content:
  
  [2/21/17 14:04:49:429 GMT]     FFDC
  Exception:com.ibm.ws.wmqcsi.trace.WMQClientException
  SourceId:getMessage(String,Object[]) ProbeId:XS001002
  Reporter:java.util.HashMap@6e73432e
  com.ibm.ws.wmqcsi.trace.WMQClientException:
  
                                      FDCTitle
  
  Product          :- ProductName
  Date/Time        :- Tue Feb 21 14:04:49 GMT 2017
  System time      :- 1487685889407
  Operating System :- z/OS
  UserID           :- userid
  Java Vendor      :- IBM Corporation
  Java Version     :- 2.8
  
  Source Class     :- com.ibm.ws.wmqcsi.nls.NLSImpl
  Source Method    :- getMessage(String,Object[])
  ProbeID          :- XS001002
  Thread           :- name=P=878406:O=0:CT priority=5 group=main
  ccl=com.ibm.ws.bootstrap.ExtClassLoader@ff31e29a
  
                                        Data
                                        ----
  |   key  :-  MQJCA5001
  
  Stack trace to show the location of the FFST call:
  
  |   FFST Location  :-  java.lang.Exception
  |   	at
  com.ibm.msg.client.commonservices.trace.Trace.getCurrentPosition
  (Trace.java:2149)
  |   	at
  com.ibm.msg.client.commonservices.trace.Trace.createFFSTString(T
  race.java:2056)
  |   	at
  com.ibm.msg.client.commonservices.trace.Trace.ffstInternal(Trace
  .java:1938)
  |   	at
  com.ibm.msg.client.commonservices.trace.Trace.ffst(Trace.java:17
  39)
  |   	at
  com.ibm.msg.client.commonservices.j2se.NLSServices.getMessage(NL
  SServices.java:181)
  |   	at
  com.ibm.msg.client.commonservices.j2se.NLSServices.getMessage(NL
  SServices.java:202)
  |   	at com.ibm.ws.wmqcsi.log.LogImpl.log(LogImpl.java:93)
  |   	at
  com.ibm.msg.client.commonservices.Log.Log.logInternal(Log.java:5
  38)
  |   	at
  com.ibm.msg.client.commonservices.Log.Log.log(Log.java:484)
  |   	at
  com.ibm.mq.connector.ResourceAdapterImpl.<clinit>(ResourceAdapte
  rImpl.java:275)
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the IBM MQ classes for Java and IBM
  MQ classes for JMS when running on z/OS.
  
  This does not affect users of WebSphere Application Server v9.0
  on z/OS unless they have manually updated the IBM MQ Resource
  Adapter with one from an MQ v9.0 installation on z/OS.  The
  default IBM MQ Resource Adapter as supplied with WebSphere
  Application Server v9.0 does not have this problem.
  
  
  Platforms affected:
  z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The IBM MQ classes for JMS and IBM MQ classes for Java jar files
  were being built on z/OS containing an EBCDIC character encoded
  version of the message properties files (such as
  mqji.properties).
  
  The IBM MQ classes for Java/JMS expected to find these
  properties files encoded in ASCII, which was the case in
  previous versions up to and including MQ v8.0.  The result of
  this was that at runtime, the IBM MQ classes for Java/JMS would
  throw an "java.lang.Exception" which would result in an FDC when
  running inside the WebSphere Application Server environment.
  
  As part of a change to allow dynamic inclusion of the MQ product
  name in the message properties files at build time, the
  properties files were being incorrectly re-encoded in EBCDIC on
  z/OS, which caused the problem at runtime.
  

Problem conclusion

• The IBM MQ build scripts have been updated to specify that they
  are to use an ASCII character encoding when dynamically updating
  the product name within the message property files for z/OS.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.0 CD    9.0.3
  v9.0 LTS   9.0.0.1
  
  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

  IBM MQ BASE M/P

• Fixed component ID

  5724H7261

Applicable component levels

• R900 PSY

     UP