IT34750: JMSINPUT NODE MAPMESSAGE FAILS XML VALIDATION WHEN MAP OR STREAMNAME CONTAINS INVALID CHARACTERS FOR AN XML TAG

APAR status

• Closed as program error.

Error description

• When a JMSInput node receives a JMS MapMessage it converts the
  names and values from the map into an XML bitstream and writes
  to the message tree using the XML parser.
  
  If a name of a name/value pair in  the MapMessage contains
  characters that are not compliant with the  XML specification
  for an XML tag, the XML parser fails with a  message similar to
  this:
  
  An XML parsing error 'Expected an attribute name ' occurred on
  line 1 column 50 when parsing
  element 'map'. Internal error codes are '174' and ''.
  

Local fix

• NA
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise V11 using a JMSInput
  node to receive JMS MapMessage or JMS StreamMessage
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When a JMSInput node receives a JMS MapMessage it converts the
   names and values from the map into an XML bitstream and writes
  to the message tree using the XML parser.
  
  If a name of a name/value pair in  the MapMessage contains
  characters that are not compliant with the  XML specification
  for an XML tag, the XML parser fails with a  message similar to
  this:
  
  An XML parsing error 'Expected an attribute name ' occurred on
  line 1 column 50 when parsing element 'map'. Internal error
  codes are '174' and ''.
  

Problem conclusion

• When a JMSInput node receives a JMS MapMessage which contains
  characters that would be invalid in an XML tag, it escapes the
  names as follows:
  
  The XML tag of the name element is formed by truncating the JMS
  message name element up to the location of the first invalid
  character.
  
  The original name from JMS name element is preserved in an
  attribute of the XML tag.
  
  The closing XML tag matches the opening tag , without the tag
  attribute.
  
  For example:
  
  In a JMS MapMessage where a name value pair is
  
              <ORDER_ITEM[5]><WIDGET>
  
  This would be converted to XML and written to the Message Tree
  as:
  
               <ORDER_ITEM
  ibm_original_name="ORDER_ITEM[5]">WIDGET</ORDER_ITEM>
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.11
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

  APP CONNECT ENT

• Fixed component ID

  5724J0550

Applicable component levels