IBM Support

JR52082: LEADING ZEROS IN PURE NUMBER STRING ARE REMOVED AFTER WEB SERVICE INTEGRATION

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If the  root parameter in the request message contains a string
    type that is a pure number that is longer than nine digits and
    starts with zeros, such as 001234567890, after web service
    integration occurs the leading zeros are removed. For example,
    the request contains one string element only:
    <element name="op">
      <complexType>
        <sequence>
          <element name="example" type="xsd:string" />
        </sequence>
      </complexType>
    </element>
    If the value that you entered is 001234567890, the generated
    SOAP request message looks like 1234567890.
    Other symptoms of this may include errors such as:
    java.lang.NumberFormatException: Not a valid char
    constructor input:
    when certain string values that correlate to number formats
    like hex.
    For example, a string of "1D" may produce the above error.
    

Local fix

  • n/a
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  IBM Business Process Manager (BPM)          *
    *                  Advanced                                    *
    *                  IBM BPM Standard                            *
    *                  IBM BPM Express                             *
    ****************************************************************
    * PROBLEM DESCRIPTION: If the  root parameter in the request   *
    *                      message contains a string               *
    *                      type that is a pure number that is      *
    *                      longer than nine digits and             *
    *                      starts with zeros, such as              *
    *                      001234567890, after web service         *
    *                      integration occurs the leading zeros    *
    *                      are removed. For example,               *
    *                      the request contains one string         *
    *                      element only:                           *
    *                      <element name="op">                     *
    *                      <complexType>                           *
    *                      <sequence>                              *
    *                      <element name="example"                 *
    *                      type="xsd:string" />                    *
    *                      </sequence>                             *
    *                      </complexType>                          *
    *                      </element>                              *
    *                      If the value that you entered is        *
    *                      001234567890, the generated             *
    *                      SOAP request message looks like         *
    *                      1234567890                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When web service integration code tries to generate the SOAP
    request, the simple type for root element is not been
    transferred to the serializer. Therefore, the serializer must
    guess the type of the simple type. While serializing the
    parameter value, if the value is longer than nine digits, the
    value is processed as a decimal type instead of a string type.
    With the value format changed, the leading zeros are removed.
    

Problem conclusion

  • A fix is available for IBM BPM V8.5.5.0 to properly pass a
    parameter &#162;&#226;&#130;&#172;&#226;&#132;&#162;s type to the request message serializer.
    
    On Fix Central (http://www.ibm.com/support/fixcentral), search
    for JR52082:
    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 JR52082, 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

    JR52082

  • Reported component name

    BPM STANDARD

  • Reported component ID

    5725C9500

  • Reported release

    855

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-12-18

  • Closed date

    2015-01-15

  • Last modified date

    2015-03-03

  • 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 STANDARD

  • Fixed component ID

    5725C9500

Applicable component levels

  • R800 PSY

       UP

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

Document Information

Modified date:
03 March 2015