IBM Support

PI46358: Problem with notify call for updateTrigger="mbean"

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After updating server.xml or a file in the apps directory,
    if
    the first notify call made is not an update, we get stuck
    (subsequent calls to notify update have no effect) until a
    bounce or another server.xml or EAR/WAR file update.
    

Local fix

  • None
     -
    Keyword: liberty wlp PI43277 FileNotificationMBean
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Liberty Profile                      *
    ****************************************************************
    * PROBLEM DESCRIPTION: FileNotificationMbean caches file       *
    *                      modification timestamps for all         *
    *                      monitored files when notifyFileChanges  *
    *                      is invoked                              *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The FileNotificationMbean caches file modification timestamps
    for all monitored files when notifyFileChanges is invoked,
    regardless of the specific list of file changes that were passed
    to the method.  The consequence of this is that the user cannot
    make a subsequent MBean call to notifyFileChanges without first
    making the target filesystem change again before calling
    notifyFileChanges, indicating files which were omitted from the
    prior MBean call(s).
    
    The practical consequence of this behavior is that if a user
    makes a mistake in their call (leaving out an intended file
    change for example), or  if they want to stagger their MBean
    requests, they must again make the target filesystem updates so
    that the runtime will recognize the change as current and
    valid.
    

Problem conclusion

  • The behavior of the FileNotificationMbean notifyFileChanges
    method has been updated such that all filesystem changes remain
    valid until the user requests  them. Meaning if they make
    filesytem changes and that specific change is not specified on a
    given MBean call, that (unnotified) change will remain valid for
    subsequent calls until such time that it becomes invalidated. A
    given change becomes invalidated when a conflicting filesystem
    change is made.
    
    The fix for this APAR is currently targeted for inclusion in fix
    pack 8.5.5.8.  Please refer to the Recommended Updates page for
    delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

  • Update the filesystem with the target updates prior to calling
    notifyFileChanges.  Ensure that the target changes made to the
    filesystem exactly matches what is passed to notifyFileChanges.
    If it does not, make all the target updates again, and then re-
    invoke notifyFileChanges.
    

Comments

APAR Information

  • APAR number

    PI46358

  • Reported component name

    LIBERTY PROFILE

  • Reported component ID

    5724J0814

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2015-08-05

  • Closed date

    2015-10-26

  • Last modified date

    2015-10-26

  • 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

    LIBERTY PROFILE

  • Fixed component ID

    5724J0814

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud \u0026 Data Platform"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"850","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
15 October 2021