IBM Support

JR52537: INBOUND WEB SERVICE GENERATE INCORRECT WSDL AND SOAP MESSAGE FOR COMPLEX TYPE LIST PARAMETERS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When you place your inbound web service  inside a toolkit and
    one parameter is defined as a complex type list, the inbound
    web service generated WSDL contains an array type definition
    in a non-existent namespace and the runtime-generated SOAP
    message does not accomplish the WSDL definition. As a result,
    the web service client reports an error when loading the wrong
    WSDL or parsing the SOAP response message.
    
       This can lead to the following hung threads
    [4/14/16 8:01:33:763 CEST] 000000a5 ThreadMonitor W   WSVR0605W:
     Thread
    "WebContainer : 0" (000001b2) has been active for 726141
    milliseconds and may be hung.  There is/are 1 thread(s) in
    total in the server that may be hung.
            at
    java.util.HashMap.findNonNullKeyEntry(HashMap.java:605)
    
    
    "WebContainer : 37" J9VMThread:0x0000000049652700,
    j9thread_t:0x000001004F719B40,
    java/lang/Thread:0x000000071FA2E298,
    state:R, prio=5
     (java/lang/Thread getId:0x24E2, isDaemon:true)
     (native thread ID:0x43D001D, native priority:0x5, native
    policy:UNKNOWN, vmstate:CW, vm thread flags:0x00000001)
    CPU usage total: 21.683002000 secs, user: 21.648816000 secs,
    system:
    0.034186000 secs
    Heap bytes allocated since last GC cycle=0 (0x0)
    Java callstack:
      at java/util/HashMap.findNonNullKeyEntry(HashMap.java:605
    (Compiled Code))
      at java/util/HashMap.getEntry(HashMap.java:589(Compiled Code))
      at java/util/HashMap.get(HashMap.java:575(Compiled Code))
      at com/lombardisoftware/core/xml/XMLTypeDescriptor.
    getFieldDescriptorByElementQName(XMLTypeDescriptor.java:495
    (Compiled Code))
      at com/lombardisoftware/core/xml/AbstractXMLSerializer.
    deserializeComplexType(AbstractXMLSerializer.java:1871(Compiled
    Code))
      at com/lombardisoftware/core/xml/AbstractXMLSerializer.
    deserializeObject(AbstractXMLSerializer.java:1335(Compiled
    Code))
      at com/lombardisoftware/core/xml/AbstractXMLSerializer.
    deserialize(AbstractXMLSerializer.java:1089)
      at com/lombardisoftware/sca/databinding/AxiomToTWObject.
    fromOMElement(AxiomToTWObject.java:111)
    

Local fix

  • No local fix
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM Business Process Manager (BPM)          *
    *                  Advanced                                    *
    *                  IBM BPM Express                             *
    *                  IBM BPM Standard                            *
    ****************************************************************
    * PROBLEM DESCRIPTION: When you place your inbound web         *
    *                      service  inside a toolkit and one       *
    *                      parameter is defined as a complex       *
    *                      type list, the inbound web service      *
    *                      generated WSDL contains an array type   *
    *                      definition in a non-existent            *
    *                      namespace and the runtime-generated     *
    *                      SOAP message does not accomplish the    *
    *                      WSDL definition. As a result, the web   *
    *                      service client reports an error when    *
    *                      loading the wrong WSDL or parsing the   *
    *                      SOAP response message.                  *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When you put the inbound web service inside a toolkit, the
    WSDL might use the namespace of the toolkit instead of the
    process application namespace. As a result, the array list
    items are created with the wrong namespace and wrong WSDL and
    a wrong SOAP message are generated.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.5.0 that ensures the
    correct namespace is used no matter where the web service is
    placed.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52537:
    
    1.Select IBM Business Process Manager with your edition from
    the product selector, the installed version to the fix pack
    level, and your platform, and then click Continue.
    2.Select APAR or SPR, enter JR52537, and click Continue.
    
    When you download fix packages, ensure that you also download
    the readme file for each fix. Review each readme file for
    additional installation instructions and information about the
    fix.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR52537

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-02-12

  • Closed date

    2015-04-07

  • Last modified date

    2016-12-30

  • 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

    BPM ADVANCED

  • Fixed component ID

    5725C9400

Applicable component levels

  • R800 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSFTN5","label":"IBM Business Process Manager Advanced"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 December 2016