IBM Support

IJ36983: MAXIMO FOR OIL AND GAS MEMORY LEAK IN PSDI.PLUSC.APP.PLUSCDS.PLUSCFLDDSPLANNUM.DATASHEETALREADYADDED(MBOREMOTE)

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • PROBLEM DESCRIPTION
    
    Maximo for Oil and Gas memory leak in  psdi.plusc.app.pluscds.
    PlusCFldDSPlanNum.dataSheetAlreadyAdded(MboRemote)
    
    REPRODUCTION STEPS
    Memory leaks identified that mbosets are being opened but are
    not then being closed.
    Failing to close the mboset means that the mboset will be open
    until the JVM is restarted and DB Connections are left open
    potentially for hours at a time.
    
    RESULTS
    The mboset should be given closed after it has been used.
    
    UNEXPECTED BEHAVIOUR
    Database connection remains open causing the memory leak.
    
    
    Code sample
    psdi.plusc.app.pluscds.PlusCFldDSPlanNum.dataSheetAlreadyAdded(
    MboRemote)
    
    /*     */   private void dataSheetAlreadyAdded(MboRemote
    thisMbo) throws RemoteException, MXException {
    /* 144 */     MboSetRemote dsPlanSetForQbe =
    MXServer.getMXServer().getMboSet("PLUSCDSASSETLINK",
    thisMbo.getUserInfo());
    /* 146 */     MboRemote owner = thisMbo.getOwner();
    /* 147 */     dsPlanSetForQbe.resetQbe();
    /* 148 */     dsPlanSetForQbe.setQbe("DSPLANNUM",
    getMboValue().getString());
    /* 149 */     dsPlanSetForQbe.setQbe("assetnum",
    thisMbo.getString("assetnum"));
    /* 150 */     dsPlanSetForQbe.setQbe("orgid",
    thisMbo.getString("orgid"));
    /* 151 */     dsPlanSetForQbe.setQbe("siteid",
    thisMbo.getString("siteid"));
    /* 152 */     dsPlanSetForQbe.setQbeExactMatch(true);
    /* 153 */     dsPlanSetForQbe.reset();
    /* 154 */     if (dsPlanSetForQbe.count() > 0) {
    /* 156 */       MboValue mboValue = getMboValue("dsplannum");
    /* 157 */       Object[] params = { mboValue.getColumnTitle(),
    getMboValue().getString() };
    /* 159 */       throw new MXApplicationException("plusdsplan",
    "NotValidDS", params);
    /*     */     }
    
    /*     */   }
    
    REPORTED IN VERSION
    
    Maximo Asset Management 7.6.1.2
    

Local fix

Problem summary

  • ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Database connection leak.                                    *
    ****************************************************************
    

Problem conclusion

  • _The fix for this APAR is contained in the following maintenance
    package: release\fix pack for Release 7.6.1.3 Product_
    

Temporary fix

Comments

APAR Information

  • APAR number

    IJ36983

  • Reported component name

    MAXIMO ASST MGM

  • Reported component ID

    5724R46AM

  • Reported release

    761

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2022-01-06

  • Closed date

    2022-03-31

  • Last modified date

    2022-03-31

  • 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

    MAXIMO ASST MGM

  • Fixed component ID

    5724R46AM

Applicable component levels

[{"Line of Business":{"code":"LOB59","label":"Sustainability Software"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"761"}]

Document Information

Modified date:
01 April 2022