PI30726: BIP3158E ERROR WHEN STORING SOAP MESSAGE ON THE COLLECTOR NODE FOR IBM INTEGRATION BUS

APAR status

• Closed as program error.

Error description

• The collector node will serialise the SOAP message before
  storing it on the Collection queue. It will serialise the
  message based on the system default ccsid, which on z/OS for
  example, is usually 500 (ebcdic).
  
  With the message stored in ebcdic, when parsing the HTTP Input
  header bitstream using ascii ccsid 819, it cannot find a
  CRLF (0D0A) character because it does not recognise the ebcdic
  (0D25) CRLF character. As a result, it continues parsing the
  whole bitstream until it exceeds the limit and logs the BIP3158
  message as below:
  
  'BIP3158', 'An error was found whilst parsing HTTP header data.
  Bad http header data. Internal single line limit exceeded
  without CRLF found',
  'POST http://hostname:port/..........
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of WebSphere Message Broker V8.0 and IBM Integration
  Bus V9.0 on z/OS storing SOAP/HTTP messages with the Collector
  node.
  
  
  Platforms affected:
  z/OS
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  The following BIP3158 error is reported when storing SOAP / HTTP
  messages to the Collector node on z/OS:
  
  'BIP3158', 'An error was found whilst parsing HTTP header data.
  Bad http header data. Internal single line limit exceeded
  without CRLF found'
  
  When storing the message to the Collector node queue, the
  message tree is serialized using the default CCSID, which on
  z/OS defaults in most cases to 500 (EBCDIC). SOAP/HTTP messages
  should however be parsed using CCSID 819. When the SOAP message
  was serialized with CCSID 500, the CRLF character was coded as
  an EBCDIC CRLF, which was then not recognized when the message
  was read back from the queue in CCSID 819 (ASCII). The HTTP
  header is limited to 4096 characters and when the CRLF was not
  found because of the CCSID conversion error, the product
  reported that this limit had been exceeded.
  
  There are a number of resource name changes between WebSphere
  Message Broker and IBM Integration Bus Version 9.0. For details
  visit
  http://www-01.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.i
  bm.etools.mft.doc/bb23814_.htm
  

Problem conclusion

• The product will now use the correct CCSID for SOAP/HTTP
  messages when serializing the SOAP/HTTP message to be stored on
  the Collector node queue.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v8.0       8.0.0.7
  v9.0       9.0.0.4
  
  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

  IB Z/OS

• Fixed component ID

  5655IBB00

Applicable component levels

• R900 PSY

     UP