JR46002: BHVC: INCONSISTENT HANDLING OF TIMEZONES FOR XSD:DATE TYPE IN BPM V8 WEBSERVICES, CAUSING A CHANGE IN THE DAY.

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • BPM 8.0.1  Web Service Integration component (in BPD) has
    incorrect treatment of timezones of xsd:Date.
    
    This is a change in behavior from BPM v7.5.1, as well as
    inconsistent with WPS/SCA and prior behavior.
    
    
    Assume the local timezone is a US time e.g. -0500 (new york).
    If an incoming date is un-timezoned: 2013-02-15; the product is
    assuming the incoming value is GMT, thereby it subtracts out
    5hours, and the internal representation of the TW.Date is shown
    to have following value:
    
    
    <property name="field2" type="Date">
    <fullYear>2013</fullYear>
        <month>1</month>
    <date>14</date>
    <dayOfWeek>4</dayOfWeek>
    <hours>19</hours>
    <minutes>0</minutes>
    <seconds>0</seconds>
    <milliseconds>0</milliseconds>
    </property>
    
    
    the expected behavior should assume GMT and maintain the
    date, and zero out any hours/min/sec/milliseconds:
    
    <property name="field2" type="Date">
    <fullYear>2013</fullYear>
        <month>1</month>
    <date>15</date>
    <dayOfWeek>4</dayOfWeek>
    <hours>0</hours>
    <minutes>0</minutes>
    <seconds>0</seconds>
    <milliseconds>0</milliseconds>
    </property>
    
    
    This causes incorrect Day to be shown downstream of the call,
    and a customer's existing projects do not work the same in
    new BPM 8.0.1.
    

Local fix

  • As a temporary workaround, customer may change a
    preference of use-jaxws to "false" to use the prior
    7510 WebService engine for exact same behavior as 7510.
    
    
    This is not recommended or supported for production.  The prior
    7510 WebService engine will be phased out and does not
    contain any modification or corrections since intial
    release.
    
    
    Within the 99Local.xml or 100Custom.xml file, please find the
    configuration tag
      <use-jaxws>true</use-jaxws>
    
    please change the value to false to revert to the Axis engine.
    
    These configuration files are located within the profiles for
    the server runtime:
    e.g. on a system using the ProcessCenter as a playback server.
    
    E:\IBM\BPM\v8.0.1\profiles\ProcCtr01\config\cells\Test1Node03C
    ell\nodes\Test17Node04\servers\server1\process-center\config
    
    and
    
    E:\IBM\BPM\v8.0.1\profiles\ProcCtr01\config\cells\Test1Node03C
    ell\nodes\Test1Node04\servers\server1\process-center\config\sy
    stem
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  Applications using Date type variables in   *
    *                  web services.                               *
    ****************************************************************
    * PROBLEM DESCRIPTION: Timezone is inconsistent and may        *
    *                      result in an incorrect day in the       *
    *                      response.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    When using BPM 8.0.1  Web Service Integration component (in
    BPD) has incorrect treatment of timezones of xsd:Date.
    This is a change in behavior from BPM v7.5.1, as well as
    inconsistent with WPS/SCA and prior behavior.
    Assume the local timezone is a US time e.g. -0500 (New York).
    If an incoming date is un-timezoned: 2013-02-15; the product is
    assuming the incoming value is GMT, thereby it subtracts out
    5 hours, and the internal representation of the TW.Date is
    shown
    to have following value:
    <property name="field2" type="Date">
    <fullYear>2013</fullYear>
    <month>1</month>
    <date>14</date>
    <dayOfWeek>4</dayOfWeek>
    <hours>19</hours>
    <minutes>0</minutes>
    <seconds>0</seconds>
    <milliseconds>0</milliseconds>
    </property>
    The expected behavior should assume GMT and maintain the
    date accordingly.
    This causes incorrect Day to be shown downstream in the call.
    

Problem conclusion

  • Code changes have been made to properly calculate the date and
    keep it consistent. An interim fix is available on v8.0.1.0.
    The code will be integrated into the next fix pack and release.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR46002

  • Reported component name

    BPM ADVANCED

  • Reported component ID

    5725C9400

  • Reported release

    800

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-03-11

  • Closed date

    2013-05-05

  • Last modified date

    2013-05-05

  • 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



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

IBM Business Process Manager Advanced

Software version:

8.0

Reference #:

JR46002

Modified date:

2013-05-05

Translate my page

Machine Translation

Content navigation