Fixes are available
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
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
APAR status
Closed as program error.
Error description
This issue addresses two performance/hang issues with the Profile Management Tool (PMT) for WebSphere Application Server V7.0. The Profile Management Tool may hang on startup, or it may display graphics very slowly and hang for several minutes when displaying certain panels. When starting the Profile Management Tool, 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 the Profile Management Tool 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 hang is most noticeable when using the Profile Mangement Tool to create a new profile. After choosing the profile type (profile template), the wizard will begin drawing the panel to prompt for the profile creation type. The text "Typical Profile Creation" will appear, and then the drawing will hang for several minutes before the rest of the text appears. The issues described above are related to defects in Eclipse libraries shipped with the Profile Management Tool. 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 The "hang on startup" issue has been reported on AIX 64-bit systems, whereas the "slow performance and hang" issue has been reported on both AIX 32-bit and AIX 64-bit systems. (Note that the Profile Management Tool is only available for the 32-bit edition of WebSphere Application Server V7.0 on AIX.)
Local fix
As a workaround, consider using the command-line "manageprofiles.sh" tool to create and manage profiles. The manageprofiles.sh tool avoids the graphics-related issues entirely. If it is necessary to use the graphical tool, the following workarounds mitigate the hang and performance issues: - Try to use a different Xwindows window manager. For example, instead of using an Xwindows product on Microsoft Windows, try using the Xwindows capabilities on a Linux or Unix system. When using Cygwin XFree86 on Microsoft Windows, try an alternative window manager to the "multi-window" window manager. - Try to use the Profile Management Tool on a local system with a display attached. - When connecting to a remote system using Xwindows, try to connect from a location with as little latency as possible between the client and server. - When using the profile tool, try not to allow any other window draw on top of the profile tool windows. This increases the window drawing time.
Problem summary
**************************************************************** * USERS AFFECTED: All users of IBM WebSphere Application * * Server V7.0 * **************************************************************** * PROBLEM DESCRIPTION: PMT runs slowly on AIX. 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 fix pack 7.0.0.15 Please refer to the Recommended Updates page for delivery information: http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
Temporary fix
Using manageprofile command to create profiles.
Comments
APAR Information
APAR number
PM14623
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
2010-05-14
Closed date
2010-09-02
Last modified date
2010-11-30
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
Modified date:
24 October 2021