IBM Support

PM32955: INSTALLATION FACTORY DISPLAYS GRAPHICS SLOWLY OR HANGS UNDER SOME CIRCUMSTANCES ON AIX, HP-UX, AND SOLARIS

Fixes are available

7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • This issue mirrors a similar problem which affects the Profile
    Management Tool for WebSphere Application Server.  That issue is
    described in APAR PM14623.  Note that this issue was originally
    reported on AIX, but further research indicated that this issue
    also affected HP-UX and Solaris.
    
    This APAR addresses two performance/hang issues with
    Installation Factory V7.0.  The Installation Factory graphical
    wizard (ifgui.sh) may hang on startup, or it may display
    graphics very slowly and hang for several minutes when
    displaying certain wizard panels.  This may prevent a user from
    finishing the process of creating a Build Definition File.
    
    When starting Installation Factory, it may hang without
    displaying any graphics at all, or it may display an
    introductory splash screen and then hang.  This can occur when
    running certain Xwindows window managers (or when running no
    window manager at all).
    
    If Installation Manager starts successfully, it may draw the
    graphics on each wizard panel very slowly.  On certain wizard
    panels, it may hang for several minutes without drawing any
    graphics at all, and it does not accept input until the drawing
    is complete.  Sometimes, the hang does not resolve at all.  This
    can occur when running Xwindows over a remote connection where
    the network latency is over 30 milliseconds.
    
    The issues described above are related to defects in Eclipse
    libraries shipped with Installation Factory.  The technical
    details of these defects are described in Eclipse Bugzilla Bug
    305991 and 36086.
    
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=305991
    https://bugs.eclipse.org/bugs/show_bug.cgi?id=36806
    

Local fix

  • As a workaround, consider using the Installation Factory
    graphical wizard tool on a different system (or different
    operating system).  The tool can be run in "disconnected mode",
    which allows the user to generate a Build Definition File
    without actually creating a Custom Installation Package.
    
    The Build Definition File can then be transferred to the
    targeted system, and then a Custim Installation Package can be
    generated from that file using the ifcli.sh tool.  This allows
    the Custom Installation Pacakge to be built while avoiding using
    the graphical wizard on the system affected by this defect.
    
    For details how to implement this workaround, refer to this
    article:
    
    http://www14.software.ibm.com/webapp/wsbroker/redirect?version=c
    ompass&product=ifactory&topic=tins_if_createbuild3
    
    Note that due to word-wrapping in this report, you may need to
    manually reconstruct that URL.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Installation     *
    *                  Factory 7.0.                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Install Factory runs slowly on AIX,     *
    *                      HP-UX and Solaris. It happens only on   *
    *                      64bit while using Reflection X.         *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    The software launches fine but hangs as soon as any button (or
    link) is clicked. The INDERTERMINATE progress bar is flooding
    the event queue with timer events causing application hang.
    The code inside the timer takes about 100 milliseconds to run
    on this system and the progress update timeout is 100
    milliseconds as well.
    

Problem conclusion

  • This patch adjusts the progress update timeout according to
    how long it takes to run the code. When there is no window
    manager running or the window manager is rootless, and the
    parent window containing the window frame is a native window,
    not an X window, no reparent occurs. isVisible() fails for an
    unparented Shell, so the application hangs after verifying if
    the Shell has become visible. The patch reacts to specific X
    event, and once it happens,the window is treated as parented.
    The fix for this APAR is currently targeted for
    inclusion in Installation Factory 7.0.0.19. 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

    PM32955

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2011-02-16

  • Closed date

    2011-04-18

  • Last modified date

    2011-04-18

  • 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

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 7.0

Reference #: PM32955

Modified date: 18 April 2011