IT37469: Invalid config-property-type returned by IBM MQ RA results in 'Invalid archive: wmq.jmsra' warnings in WildFly/JBoss.

APAR status

• Closed as program error.

Error description

• When the MQ resource adapter is deployed into WildFly
  application server, a number of warning messages similar to the
  example shown below are written to the WildFly server log:
  
  Severity: WARNING
  Section: 20.7
  Description: Invalid config-property-type for ResourceAdapter.
  Code: Class: com.ibm.mq.connector.ResourceAdapterImpl Property:
  traceEnabled Type: boolean
  
  Despite the warnings, the MQ resource adapter behaves as
  expected.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  This issue affects users of the IBM MQ resource adapter.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  Section 20.7 in the Java connector architecture (JCA) 1.7
  specification states that the config-property-type element
  within a resource adapter's XML file must be set to one of the
  following Java objects:
  
  - java.lang.Boolean
  - java.lang.String
  - java.lang.Integer
  - java.lang.Double
  - java.lang.Byte
  - java.lang.Short
  - java.lang.Long
  - java.lang.Float
  - java.lang.Character
  
  Although the MQ resource adapter's XML file correctly defined
  properties using the Java objects shown above, the getter
  methods which corresponded to some of the properties incorrectly
  returned Java primitives (such as boolean and int) rather than
  objects. For example, the MQ resource adapter's XML file defined
  the traceEnabled property like this:
  
  <config-property>
    <config-property-name>traceEnabled</config-property-name>
    <config-property-type>java.lang.Boolean</config-property-type>
    <config-property-value>false</config-property-value>
  </config-property>
  
  However, the getter method for this property:
  
  getTraceEnabled()
  
  returned a boolean, instead of a java.lang.Boolean.
  
  As a result, when the MQ resource adapter was deployed into
  WildFly, warning messages were written to the WildFly server log
  indicating that the config-property-type element within the
  resource adapter's XML file was invalid, as shown in the example
  below:
  
  Severity: WARNING
  Section: 20.7
  Description: Invalid config-property-type for ResourceAdapter.
  Code: Class: com.ibm.mq.connector.ResourceAdapterImpl Property:
  traceEnabled Type: boolean
  
  
  Similar warnings were also generated for the following
  properties:
  
  Property: CCSID, Type: int
  Property: sslResetCount, Type: int
  Property: port, Type: int
  Property: statusRefreshInterval, Type: int
  Property: pollingInterval, Type: int
  Property: failIfQuiesce, Type: boolean
  Property: targetClientMatching, Type: boolean
  Property: rescanInterval, Type: int
  Property: sslFipsRequired, Type: boolean
  Property: cleanupInterval, Type: long
  Property: connectionConcurrency, Type: int
  Property: reconnectionRetryInterval, Type: int
  Property: startupRetryInterval, Type: int
  Property: supportMQExtensions, Type: boolean
  Property: maxConnections, Type: int
  Property: reconnectionRetryCount,, Type: int
  Property: traceEnabled, Type: boolean
  Property: traceLevel, Type: int
  Property: logWriterEnabled, Type: boolean
  Property: startupRetryCount, Type: int
  Property: sendCheckCount, Type: int
  Property: pubAckInterval, Type: int
  Property: unmappableReplacement, Type: byte
  Property: MaxSequentialDeliveryFailures, Type: int
  
  Note: The warning messages do not affect the functionality of
  the MQ resource adapter - despite the warnings, the MQ resource
  adapter works as expected.
  

Problem conclusion

• To resolve this issue, the MQ resource adapter has been updated
  so that the getter methods for the following properties:
  
  - CCSID
  - cleanupInterval
  - connectionConcurrency
  - failIfQuiesce
  - logWriterEnabled
  - maxConnections
  - MaxSequentialDeliveryFailures
  - pollingInterval
  - port
  - pubAckInterval
  - reconnectionRetryCount
  - reconnectionRetryInterval
  - rescanInterval
  - sendCheckCount
  - sslFipsRequired
  - sslResetCount
  - startupRetryCount
  - startupRetryInterval
  - statusRefreshInterval
  - supportMQExtensions
  - targetClientMatching
  - traceEnabled
  - traceLevel
  - unmappableReplacement
  
  now return Java objects, rather than primitives, as per the JCA
  1.7 specification.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v9.2 LTS   9.2.0.5
  v9.x CD    9.2.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

  MQ BASE V9.2

• Fixed component ID

  5724H7281

Applicable component levels