IBM Support

PI36070: PROCESS MARKED AS "FAILED" EVEN THOUGH ALL STEPS MARKED AS "SUCCEEDED" IN HA

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Intermittently, processes that were successful can be marked as
    failed in HA setups. An error similar to the following will
    appear in the server logs:
    
    org.hibernate.StaleObjectStateException: Row was updated or
    deleted by another transaction (or unsaved-value mapping was
    incorrect):
    [com.urbancode.ds.subsys.process.property_context.PropertyContex
    t#9170b1f0-93f4-480b-85a7-403f2e05c5fa]
        at
    org.hibernate.persister.entity.AbstractEntityPersister.check(Abs
    tractEntityPersister.java:1950)
        at
    org.hibernate.persister.entity.AbstractEntityPersister.update(Ab
    stractEntityPersister.java:2594)
        at
    org.hibernate.persister.entity.AbstractEntityPersister.updateOrI
    nsert(AbstractEntityPersister.java:2494)
        at
    org.hibernate.persister.entity.AbstractEntityPersister.update(Ab
    stractEntityPersister.java:2821)
        at
    org.hibernate.action.EntityUpdateAction.execute(EntityUpdateActi
    on.java:113)
        at
    org.hibernate.engine.ActionQueue.execute(ActionQueue.java:273)
    ...
    com.urbancode.ds.subsys.deploy.workflow.activity.RunComponentPro
    cessActivity.workflowFinished(RunComponentProcessActivity.java:6
    49)
        at sun.reflect.GeneratedMethodAccessor172.invoke(Unknown
    Source)
        at
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:55)
        at java.lang.reflect.Method.invoke(Method.java:619)
    ...
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users                                                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Issues with incorrect statuses on processes in               *
    * high-availability environment                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix is available in IBM UrbanCode Deploy 6.1.1.3
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI36070

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-03-02

  • Closed date

    2015-04-14

  • Last modified date

    2015-04-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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

  • R600 PSN

       UP

  • R600 PSY

       UP

  • R601 PSN

       UP

  • R601 PSY

       UP

  • R610 PSN

       UP

  • R610 PSY

       UP

  • R611 PSN

       UP

  • R611 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"610","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 October 2021