PJ40881: PE 5.X BASED MONITORS THAT CALL VWTOOL LEAVE ORPHANED PROCESSES IF VWTOOL NEVER RETURNS ANYTHING (PE IS DOWN).

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

  • If PE is down, the FSM monitors that call vwtool eventually
    timeout.  This is expected.  However, the cleanup and detection
    of this problem is not appropriate.  The cepest command is
    killed, but the sh, cmd, and java command are not cleaned up.
    On the next run of the monitor, it does not know that this
    happened, and the monitor is executed again.  If PE is still
    down, the issue happens again.  Now, there are two sets of
    orphaned processes.  This will continue to happen as long as PE
    is down.  Furthermore, those orphaned processes need manual
    intervention to be terminated.
    

Local fix

  • When PE (or any P8 product is shutdown), stop Cala client.  If
    it was not stopped, stop Cala, check for orphaned sh, cmd, and
    java processes, and terminate those processes.  Once PE is back
    up, start Cala client again.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * FSM 4.5 clients that use monitors involving vwtool           *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply FSM 4.5 FP3 only if you never plan to go to ECM SM     *
    * 5.1.  If this is not the case, it is highly suggested to     *
    * upgrade to 5.1 first since there are changes in FP3 that     *
    * make it harder to upgrade to ECM SM 5.1 GA had the FP not    *
    * been applied.  The upgrade procedure from 4.5 to 5.1 GA      *
    * takes the same amount of effort as applying this FP.  If     *
    * this route is taken, apply the latest 5.1 FP after the       *
    * upgrade.                                                     *
    ****************************************************************
    

Problem conclusion

  • The problem is fixed in FSM 4.5 FP3 and ECM SM 5.1 FP1
    

Temporary fix

Comments

APAR Information

  • APAR number

    PJ40881

  • Reported component name

    SYSTEM MONITOR

  • Reported component ID

    5724R9100

  • Reported release

    450

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-04

  • Closed date

    2013-07-10

  • Last modified date

    2013-07-10

  • 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

    SYSTEM MONITOR

  • Fixed component ID

    5724R9100

Applicable component levels

  • R450 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

FileNet System Monitor
FileNet System Monitor

Software version:

4.5.0

Reference #:

PJ40881

Modified date:

2013-07-10

Translate my page

Machine Translation

Content navigation