JR46037: If modules don't propagate HTTP headers, the test case response will not come back.

8.0.1.2: IBM Integration Designer V8.0.1 Fix Pack 2 for Windows
8.0.1.2: IBM Integration Designer V8.0.1 Fix Pack 2 for Linux
7.5.1.2: IBM Integration Designer V7.5.1 Fix Pack 2 for Linux
7.5.1.2: IBM Integration Designer V7.5.1 Fix Pack 2 for Windows

APAR status

• Closed as fixed if next.

Error description

• Testers using the test project servlet or component test
  explorer may run into this issue:If modules don't propagate HTTP
   headers, the test case response will not come back.
  
  
  If the HTTP header is not available from the HTTP binding when
  the response is being created, the comptest HTTP handler will
  throw an NPE. A 500 error will be displayed instead. Missing
  headers can result from user errors such as maps that don't map
  header contents. And it seems to be a problem when using JMS
  bindings. The HTTP binding is used when running test cases
  outside IID, such as using the CTE. The only function that will
  not work when this NPE is fixed is when a parameter is added to
  the URL that specifies whether to use a JUnit-compatible
  response format (which would only be when the user calls the
  test project servlet directly, so when not using IID or the
  CTE).
  

Local fix

• A work around is available for the maps that don't map the
  header: either map the header at the top level, or select /body
  as the mapping root.
  

Problem summary

• This fix will be included in the upcoming releases.
  

Problem conclusion

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

Applicable component levels

• R751 PSY

     UP

• R800 PSY

     UP

• R801 PSY

     UP