IT45609: WHEN CONVERTING A JMS HEADER VALUE THAT HAS AN UNSUPPORTED TYOE EXCESSIVE INFORMATION IS LOGGED TO STDERR

APAR status

• Closed as program error.

Error description

• When using the JMSInput Node to process a message that has a JMS
  Header value that is not a supported type the following
  exception will be logged to stderr:
  
  <com.ibm.broker.plugin.MbRecoverableException
  class:com.ibm.broker.plugin.MbElement method:setValue
  source:BIPmsgs key:4373 >
  at com.ibm.broker.plugin.MbElement.setValue(MbElement.java:1660)
  
  at com.ibm.broker.plugin.MbElement.(MbElement.java:319)
  at com.ibm.broker.plugin.MbElement.createElementAsLastChild(MbE
  lement.java:1092)
  at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsTo
  Mb.createDataTypeValueElements(JMSClientMessageFormatterJmsToMb
  .java:1973)
  at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsTo
  Mb.getMessagePropertiesFromJMS(JMSClientMessageFormatterJmsToMb
  .java:1208)
  at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsTo
  Mb.jmsHeaderAndPropertiesToTreeDirect(JMSClientMessageFormatter
  JmsToMb.java:190)
  at com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsTo
  Mb.jmsHeaderAndPropertiesToTree(JMSClientMessageFormatterJmsToM
  b.java:161)
  at com.ibm.broker.jmsclientnodes.JMSClientInputNode.parseInput(
  JMSClientInputNode.java:1291)
  at com.ibm.broker.jmsclientnodes.JMSClientInputNode.run(JMSClie
  ntInputNode.java:545)
  
  Processing of the message otherwise proceeds as normal with the
  unsupported message header missing from the message, however for
  high message volumes this can result in an excessive use of disk
  space as the stderr file does not wrap.
  
  The exception should instead be logged to trace instead of
  output to stderr.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of IBM App Connect Enterprise version 12 or above
  using the JMSInput Node
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When using the JMSInput Node to process a message that has a JMS
  Header value that is not a supported type the following
  exception will be logged to stderr:
  
  <com.ibm.broker.plugin.MbRecoverableException
  class:com.ibm.broker.plugin.MbElement method:setValue
  source:BIPmsgs key:4373 > at
  com.ibm.broker.plugin.MbElement.setValue(MbElement.java:1660)
  at com.ibm.broker.plugin.MbElement.(MbElement.java:319)
  at
  com.ibm.broker.plugin.MbElement.createElementAsLastChild(MbEleme
  nt.java:1092)
  at
  com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsToMb.c
  reateDataTypeValueElements(JMSClientMessageFormatterJmsToMb.java
  :1973)
  at
  com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsToMb.g
  etMessagePropertiesFromJMS(JMSClientMessageFormatterJmsToMb.java
  :1208)
  at
  com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsToMb.j
  msHeaderAndPropertiesToTreeDirect(JMSClientMessageFormatter
  JmsToMb.java:190)
  at
  com.ibm.broker.jmsclientnodes.JMSClientMessageFormatterJmsToMb.j
  msHeaderAndPropertiesToTree(JMSClientMessageFormatterJmsToMb.jav
  a:161)
  at
  com.ibm.broker.jmsclientnodes.JMSClientInputNode.parseInput(JMSC
  lientInputNode.java:1291)
  at
  com.ibm.broker.jmsclientnodes.JMSClientInputNode.run(JMSClientIn
  putNode.java:545)
  
  Processing of the message otherwise proceeds as normal with the
  unsupported message header missing from the message, however for
  high message volumes this can result in an excessive use of disk
  space as the stderr file does not wrap.
  

Problem conclusion

• The exception is now logged to service trace instead of stderr
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v12.0      12.0.12.3
  
  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

  5724J0560

Applicable component levels