IBM Support

PM20073: FINDBYPRIMARYKEY FOR A NEWLY DELETED ENTITY OBJECT RETURNS THE DELETED ENTITY, NOT OBJECTNOTFOUNDEXCEPTION.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Customer's application deletes an Entity, and then issues a
    FindByPrimaryKey for the newly deleted object. In V5.1 the
    WebSphere runtime returns ObjectNotFoundException. In V6.1 the
    runtime returns the recently deleted object.
    The application next does a remove of this "ghost" object and
    the runtime returns NoSuchEntityException.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: Customers migrating EJB applications         *
    *                 containing CMP beans to WebSphere            *
    *                 Application Server V6.1.                     *
    *                                                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: There is a behavior change between      *
    *                      WebSphere Application Server V5.1       *
    *                      and V6.1 when a call to                 *
    *                      'FindByPrimaryKey'is invoked after      *
    *                      the entity bean has been removed.       *
    *                                                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The problem shows up when within the same transaction the
    following actions take place on the same instance of a CMP 2.0
    bean:
    
    1. The application looks up the bean instance.  The bean is
    persisted in the memory by the persistence manager
    2. The application removes the bean instance.  Persistence
    manager flags the instance as "removed".
    3. The application looks up the bean instance again.  This
    time the deleted bean instance is retrieved. If one attempts
    to remove this bean instance again a 'NoSuchEntityException'
    is thrown.
    

Problem conclusion

  • This APAR will allow Persistence Manager to better handle the
    exception observed in this specific scenario.
    
    APAR PM20073 is currently targeted for inclusion in Service
    Level (Fix Pack) 6.1.0.35 of WebSphere Application Server V6.1.
    
    Please refer to URL:
    //www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
    for Fix Pack availability.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM20073

  • Reported component name

    WEBSPHERE FOR Z

  • Reported component ID

    5655I3500

  • Reported release

    610

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-08-06

  • Closed date

    2010-11-30

  • Last modified date

    2011-01-04

  • APAR is sysrouted FROM one or more of the following:

    PK82854

  • APAR is sysrouted TO one or more of the following:

Modules/Macros

  • BBGUBINF BBOUBINF
    

Fix information

  • Fixed component name

    WEBSPHERE FOR Z

  • Fixed component ID

    5655I3500

Applicable component levels

  • R610 PSY UK62676

       UP10/12/17 P F012

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS7K4U","label":"WebSphere Application Server for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
10 February 2022