IBM Support

IC92093: WMQFTE 7.0.4 FTECREATETRANSFER COMMAND IN BATCH FILE UNEXPECTEDLY HANGS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When calling the fteCreateTransfer.cmd the
    prompt does not return. The file has been successfully
    transferred, however the JVM which executes the
    fteCreateTransfer command is hung and does not terminate
    as expected. The IBM Java Support team determined that JAVA APAR
    IV20122 was the cause of the hang.
    

Local fix

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    This issue affects users of WebSphere MQ File Transfer Edition
    v7.0.4 who are using the fteCreateTransfer command to submit a
    new transfer request to a WebSphere MQ File Transfer Edition
    agent.
    
    
    Platforms affected:
    AIX, IBM iSeries, Linux on Power, Linux on S390, Linux on x86,
    Linux on x86-64, Linux on zSeries, Windows, z/OS
    
    ****************************************************************
    PROBLEM SUMMARY:
    The problem summary as documented in Java APAR IV20122 reads:
    When large numbers of JVMs terminate simultaneously, the
    thread "Attach API wait loop" may not terminate cleanly when the
    JVM exits.
    
    For WebSphere MQ File Transfer Edition this issue manifests
    itself as a hang on shutdown of the JVM running the
    fteCreateTransfer command. A set of Javacores taken during the
    hang on shutdown show the "main" thread having finished
    running the fteCreateTransfer command and System.exit() being
    called:
    
    Java callstack:
    at java/lang/Object.wait(Native Method)
    at java/lang/Object.wait(Object.java:196)
    at java/lang/Thread.join(Thread.java:616)
    at
    java/lang/ApplicationShutdownHooks.run(ApplicationShutdownHooks.
    java:91)
    at java/lang/Shutdown.runHooks(Shutdown.java:101)
    at java/lang/Shutdown.sequence(Shutdown.java:145)
    at java/lang/Shutdown.exit(Shutdown.java:190)
    at java/lang/Runtime.exit(Runtime.java:101)
    at java/lang/System.exit(System.java:279)
    at
    com/ibm/wmqfte/api/CreateTransfer.main(CreateTransfer.java:1300)
    at sun/reflect/NativeMethodAccessorImpl.invoke0(Native Method)
    at
    sun/reflect/NativeMethodAccessorImpl.invoke(NativeMethodAccessor
    Impl.java:60)
    at
    sun/reflect/DelegatingMethodAccessorImpl.invoke(DelegatingMethod
    AccessorImpl.java:37)
    at java/lang/reflect/Method.invoke(Method.java:611)
    at
    com/ibm/wmqfte/agent/bootstrap/impl/BootstrapMain.run(BootstrapM
    ain.java:228)
    at
    com/ibm/wmqfte/agent/bootstrap/impl/BootstrapMain.main(Bootstrap
    Main.java:109)
    
    The main thread waits to be notified by the Attach API threads
    that their processing has completed however the Javacores show
    they remain in the following states:
    
    Attach API wait loop:
    Java callstack:
    at com/ibm/tools/attach/javaSE/IPC.waitSemaphore(Native Method)
    at
    com/ibm/tools/attach/javaSE/CommonDirectory.waitSemaphore(Common
    Directory.java:220)
    at
    com/ibm/tools/attach/javaSE/AttachHandler$WaitLoop.waitForNotifi
    cation(AttachHandler.java:329)
    at
    com/ibm/tools/attach/javaSE/AttachHandler$WaitLoop.run(AttachHan
    dler.java:396)
    
    
    Attach API teardown
    Java callstack:
    at java/lang/Thread.sleep(Native Method)
    at java/lang/Thread.sleep(Thread.java:851(Compiled Code))
    at
    com/ibm/tools/attach/javaSE/AttachHandler.terminate(AttachHandle
    r.java:414(Compiled Code))
    at
    com/ibm/tools/attach/javaSE/AttachHandler$teardownHook.run(Attac
    hHandler.java:525)
    
    
    In order to exit the JVM, the user is required to kill the
    process.
    

Problem conclusion

  • The fteCreateTransfer command has been updated to disable the
    Attach API as per the local fix described in Java APAR IV20122.
    
    ---------------------------------------------------------------
    The fix is targeted for delivery in the following PTFs:
    
    Platform           v7.0
    --------           --------------------
    Multiplatforms     7.0.4.3
    
    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

    IC92093

  • Reported component name

    WMQ FILE TRANSF

  • Reported component ID

    5724R1000

  • Reported release

    704

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-05-03

  • Closed date

    2013-05-30

  • Last modified date

    2013-05-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

    WMQ FILE TRANSF

  • Fixed component ID

    5724R1000

Applicable component levels

  • R704 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEP7X","label":"WebSphere MQ File Transfer Edition"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"7.0.4","Edition":"","Line of Business":{"code":"LOB36","label":"IBM Automation"}}]

Document Information

Modified date:
30 May 2013