IBM Support

PM82965: MULTIBROKER.XML FILE GETS DELETED WHEN REPLICATION DOMAIN IS DELETED USING SCRIPT.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Not able to delete cluster member getting below error,
    The dmgr log shows [1/25/13 16:45:58:906 EST] 00016658
    ClusterMember
    E   Failed to delete cluster member:
    org.eclipse.emf.common.util.
    WrappedException: java.io.IOException: The system cannot find
    the specified file, either the filename is too long on Windows
    system or run out of file descriptor on UNIX platform.
    java.io.FileNotFoundException:
    /opt/local/software/websphere/v8/profiles/dmgr01/wstemp/92224000
    /workspace/cells/wass8100Cell/multibroker.xml (No such file or
    directory)
    
    this is because the multibroker.xml file got deleted.
    
    Removing replication domain from the console will not delete the
    multibroker.xml.
    
    When we run a wsadmin script to remove a replication domain it
    will delete the multibroker.xml file from the configuration.
    

Local fix

  • N/A
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server AdminConfig to remove replication    *
    *                  domains and then administrative console to  *
    *                  delete a cluster member                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Deleting the last replication domain    *
    *                      causes multibroker.xml to be deleted.   *
    *                      This causes console to log an error.    *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The administrative console expects the multibroker.xml to
    exist. When it does not, and exception is logged.
    

Problem conclusion

  • Rather than log the missing xml file as an exception, we now
    simply log it as information and continue with defaults.
    
    The fix for this APAR is currently targeted for inclusion in
    the fix pack following 8.5.0.2.  Please refer to the
    Recommended Updates page for delivery information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM82965

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-02-16

  • Closed date

    2013-03-11

  • Last modified date

    2013-03-11

  • 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

    WEBS APP SERV N

  • Fixed component ID

    5724H8800

Applicable component levels

  • R850 PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
02 November 2021