IBM Support

IT24157: IBM MQ Explorer hangs while viewing the MFT transfer log

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

  • After using the IBM MQ Explorer to view the Manager File
    Transfer transfer log for several hours, the Explorer becomes
    unresponsive. The .log file from the eclipse installation
    associated with the Explorer shows errors like this are
    continually being generated:
    
    org.eclipse.swt.SWTException: Failed to execute runnable
    (org.eclipse.swt.SWTError: No more handles)
    	at org.eclipse.swt.SWT.error(SWT.java:4397)
    	at org.eclipse.swt.SWT.error(SWT.java:4312)
    	at
    org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchroniz
    er.java:138)
    	at
    org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:41
    45)
    	at
    org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:376
    2)
    	at
    org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.r
    un(PartRenderingEngine.java:1113)
    	at
    org.eclipse.core.databinding.observable.Realm.runWithDefault(Rea
    lm.java:332)
    	at
    org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run
    (PartRenderingEngine.java:997)
    	at
    org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(
    E4Workbench.java:138)
    	at
    org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
    	at
    org.eclipse.core.databinding.observable.Realm.runWithDefault(Rea
    lm.java:332)
    	at
    org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbenc
    h.java:567)
    	at
    org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:
    150)
    	at
    com.ibm.mq.explorer.ui.rcp.internal.base.RcpApplication.start(Rc
    pApplication.java:155)
    <<< snip eclipse launcher stack >>>
    	at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
    Caused by: org.eclipse.swt.SWTError: No more handles
    	at org.eclipse.swt.SWT.error(SWT.java:4423)
    	at org.eclipse.swt.SWT.error(SWT.java:4312)
    	at org.eclipse.swt.SWT.error(SWT.java:4283)
    	at org.eclipse.swt.widgets.Widget.error(Widget.java:472)
    	at
    org.eclipse.swt.widgets.Control.internal_new_GC(Control.java:171
    9)
    	at org.eclipse.swt.graphics.GC.<init>(GC.java:166)
    	at org.eclipse.swt.graphics.GC.<init>(GC.java:132)
    	at
    com.ibm.wmqfte.explorer.content.TransferLogPage.setupTree(Transf
    erLogPage.java:1479)
    	at
    com.ibm.wmqfte.explorer.content.TransferLogPage.access$2(Transfe
    rLogPage.java:1478)
    	at
    com.ibm.wmqfte.explorer.content.TransferLogPage$16.run(TransferL
    ogPage.java:1746)
    	at
    org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
    	at
    org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchroniz
    er.java:135)
    	... 23 more
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This affects users of the IBM MQ Explorer Managed File Transfer
    plugin who view the IBM MQ Managed File Transfer Transfer Log
    for several hours.
    
    
    Platforms affected:
    MultiPlatform
    
    ****************************************************************
    PROBLEM DESCRIPTION:
    When the IBM MQ Explorer Managed File Transfer plugin was used
    to view the Transfer Log, each time the view was refreshed, a
    handle to a native graphics object was taken while redrawing the
    contents of the view. These handles were not released, and
    eventually the number of available handles ran out. Subsequent
    attempts to get one of these handles to refresh the view failed
    with an error:
    
    org.eclipse.swt.SWTError: No more handles
    
    The MQ Explorer then looped continually trying to get this
    handle. As a result of this error the Explorer became
    unresponsive, with the Explorer process using a lot of CPU
    

Problem conclusion

  • The handles to the native graphics objects taken while
    refreshing the transfer log view are now released after the
    refresh operation has completed, and so the IBM MQ Explorer does
    not hang when viewing the Transfer Log.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Version    Maintenance Level
    v7.5       7.5.0.9
    v8.0       8.0.0.10
    v9.0 LTS   9.0.0.5
    
    The latest available maintenance can be obtained from
    'WebSphere MQ Recommended Fixes'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006037
    
    If the maintenance level is not yet available information on
    its planned availability can be found in 'WebSphere MQ
    Planned Maintenance Release Dates'
    http://www-1.ibm.com/support/docview.wss?rs=171&uid=swg27006309
    ---------------------------------------------------------------
    

Temporary fix

Comments

APAR Information

  • APAR number

    IT24157

  • Reported component name

    WMQ BASE MULTIP

  • Reported component ID

    5724H7241

  • Reported release

    750

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-02-22

  • Closed date

    2018-04-15

  • Last modified date

    2018-04-15

  • APAR is sysrouted FROM one or more of the following:

    IT23855

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    WMQ BASE MULTIP

  • Fixed component ID

    5724H7241

Applicable component levels



Document information

More support for: WebSphere MQ
APAR / Maintenance

Software version: 7.5

Reference #: IT24157

Modified date: 15 April 2018


Translate this page: