IT38342: PROXY SERVLET RETURNS SOAP FAULT MESSAGE IF NON-ASCII DATA IS SENT

APAR status

• Closed as program error.

Error description

• If using the Proxy Servlet, if you send a message containing
  non-ASCII data, you may get a 500 return with a SOAP fault with
  the following details:
  <faultstring>An internal error has occurred: 3 2222 in
  processPost</faultstring>
  <text>A communications failure occurred during message
  processing (MQPUT) in broker MyBroker</text>
  
  A trace of the servlet will show:
  java.nio.charset.UnmappableCharacterException: Input length = 1
  
  The servlet is attempting to write the message to MQ to share
  with the flow, but the setting do not tolerate non-ASCII data.
  

Local fix

• Send only ASCII messages.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of the proxy servlet in IBM App Connect Enterprise v11
  and v12 who need the POST/PUT/PATCH methods with non-ASCII data.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  If the proxy servlet receives a PUT, PATCH, or POST request
  whose body is not ASCII encoded then an error will be logged
  stating MQJE001: Completion Code '3', Reason '2222' and a SOAP
  Fault message with HTTP status code 500 will be returned.
  
  A service trace of the proxy servlet will show that the MQJE001
  error is due to an UnmappableCharacterException:
  
  20210820175117.571  40 WBIMBServlet processPost Sending data to
  DFE length=537
  20210820175117.571  40 { WBIMBServlet putInputMessage
  20210820175117.571  40   { MQClientContext getBrokerInputQueue
  20210820175117.571  40   } MQClientContext getBrokerInputQueue
  20210820175117.571  40   { WBIMBServlet putMQMessageToQueue
  20210820175117.571  40     WBIMBServlet putMQMessageToQueue
  Exception uncaught
  ioe.toString()=java.nio.charset.UnmappableCharacterException:
  Input length = 1
  20210820175117.571  40     WBIMBServlet putMQMessageToQueue
  Throwing bogus MQ Exception
  20210820175117.572  40     WBIMBServlet processPost Exception
  uncaught mqe.toString()=com.ibm.mq.MQException: MQJE001:
  Completion Code '3', Reason '2222'.
  20210820175117.572  40     WBIMBServlet processPost Something
  went wrong with the MQPUT - generating SOAP Fault message
  statusCode=500
  

Problem conclusion

• The proxy servlet now correctly handles non-ASCII characters and
  all other binary data.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.15
  v12.0      12.0.2.0
  
  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