相关文章推荐
玉树临风的香菜  ·  About Azure Bastion ...·  4 天前    · 
豪气的大葱  ·  Azure AD Connect on ...·  昨天    · 
想旅行的鸵鸟  ·  oracle ...·  7 月前    · 
礼貌的凉面  ·  python 的 ...·  1 年前    · 

To return expected results, you can:

  • Reduce the number of search terms. Each term you use focuses the search further.
  • Check your spelling. A single misspelled or incorrectly typed term can change your result.
  • Try substituting synonyms for your original terms. For example, instead of searching for "java classes", try "java training"
  • Did you search for an IBM acquired or sold product ? If so, follow the appropriate link below to find the content you need.
  • A SAR was created for the RESTful client service provider. On
    the request, the header Accept-Encoding=gzip,deflate was passed
    from the client to z/OS Connect EE. z/OS Connect EE
    passed this to the REST endpoint, which responded correctly.
    z/OS Connect EE failed to handle the returned compressed data
    resulting in an HTTP response code 500 (internal server error)
    being returned. The following messages was issued:
    BAQR0429W: API {0} encountered an error while processing a
               request under URL {1}.
    The following IOException is recorded in the z/OS Connect EE
    server's FFDC directory:
     Exception = java.io.IOException
     Source = com.ibm.zosconnect.service.client.rest.internal.SarRes
     tClientServiceImpl
     probeid = 392
     Stack Dump = java.io.IOException: Unexpected character '?' on
     line 1, column 2
      at com.ibm.json.java.internal.Tokenizer.next
      at com.ibm.json.java.internal.Parser.parse
      at com.ibm.json.java.internal.Parser.parse
      at com.ibm.json.java.JSONObject.parse
      at com.ibm.json.java.JSONObject.parse
      at com.ibm.zosconnect.service.client.rest.internal.RestClientS
         erviceImpl.invoke
      at com.ibm.zosconnect.internal.ZosConnectServiceImpl.apiInvoke
      at com.ibm.zosconnect.internal.ServiceManagerImpl.invoke
      at com.ibm.zosconnect.internal.ApiManagerImpl.invokeApi
      at com.ibm.zosconnect.internal.web.ServiceProxyServlet$3.run
      at com.ibm.ws.webcontainer.async.ServiceWrapper.wrapAndRun
      at com.ibm.ws.webcontainer.async.ContextWrapper.run
      at com.ibm.ws.webcontainer.async.WrapperRunnableImpl.run
      at java.util.concurrent.ThreadPoolExecutor.runWorker
      at java.util.concurrent.ThreadPoolExecutor$Worker.run
      at java.lang.Thread.run(Thread.java:812)
    Additional search words: msgBAQR0429W msgBAQR0429 BAQR0429
    SarRestClientServiceImpl IOException IOE
    

    Local fix

  • Send the request with header:  Accept-Encoding:identify
    

    Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of z/OS Connect EE V3.0.           *
    ****************************************************************
    * PROBLEM DESCRIPTION: HTTP response code 500 and message      *
    *                      BAQR0429W are returned when an          *
    *                      Accept-Encoding:gzip,deflate header is  *
    *                      flowed.                                 *
    ****************************************************************
    z/OS Connect EE was passing on gzip compressed data with a valid
    header to the target program, but was not able to process the
    returned gzipped data.
    

    Problem conclusion

    Temporary fix

    Comments

  • z/OS Connect EE has been changed to not forward the following
    headers:
    ContentType, ContentEncoding, ContentLanguage, Accept,
    AcceptEncoding, AcceptLanguage
    The Accept header will be set to MediaType application/json in
    the flowed request.
    The fix for this APAR is expected to be delivered by the PTF for
    z/OS Connect EE V3.0.23.0 (PH13344).
    

    APAR Information

  • APAR number

    PH11409

  • Reported component name

    Z/OS CONNECT EE

  • Reported component ID

    5655CE300

  • Reported release

    000

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-04-24

  • Closed date

    2019-06-14

  • Last modified date

    2019-06-14

  • 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

    Z/OS CONNECT EE

  • Fixed component ID

    5655CE300

  • Applicable component levels

    [{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNPJM","label":"IBM z\/OS Connect"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"3.0","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
  •