IBM Support

PM01533: DEADLOCK IN NSSERIALPORT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Error Message: Following Deadlock can be seen in javacore:
    1LKDEADLOCK    Deadlock detected !!!
    NULL           ---------------------
    NULL
    2LKDEADLOCKTHR  Thread "Thread-133" (97F9A68)
    3LKDEADLOCKWTR    is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x0964FAD8 infl_mon_t: 0x00000000:
    4LKDEADLOCKOBJ      java.util.Vector@118B40F8/118B4100:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "Thread-132" (97F7A00)
    3LKDEADLOCKWTR    which is waiting for:
    4LKDEADLOCKMON      sys_mon_t:0x09B96DA8 infl_mon_t: 0x00000000:
    4LKDEADLOCKOBJ      com.ibm.comm.NSSerialPort@118B4E70/118B4E78:
    3LKDEADLOCKOWN    which is owned by:
    2LKDEADLOCKTHR  Thread "Thread-133" (97F9A68)
    .
    Stack Trace: The threads in deadlock have following stack
    traces:
    3XMTHREADINFO      "Thread-133" (TID:101F6EB0,
    sys_thread_t:97F9A68, state:R, native ID:2C80A8) prio=5
    4XESTACKTRACE          at
    com.ibm.comm.NSSerialPort$SerialEventDeliveryThread.addEvent(NSS
    erialPort.java:1282)
    4XESTACKTRACE          at
    com.ibm.comm.NSSerialPort.reportSerialEvent(NSSerialPort.java:12
    34)
    4XESTACKTRACE          at
    com.ibm.comm.NSSerialPort.setByteCount(NSSerialPort.java:1147)
    4XESTACKTRACE          at
    com.ibm.comm.SerialDataEventThread.monitorSerialDataNC(Native
    Method)
    4XESTACKTRACE          at
    com.ibm.comm.SerialDataEventThread.run(SerialDataEventThread.jav
    a:50)
    and
    3XMTHREADINFO      "Thread-132" (TID:101F6F10,
    sys_thread_t:97F7A00, state:R, native ID:2C40A7) prio=5
    4XESTACKTRACE          at
    com.ibm.comm.NSSerialPort.reportSerialEvent(NSSerialPort.java:12
    37)
    4XESTACKTRACE          at
    com.ibm.comm.NSDeviceOutputStream.write(NSDeviceOutputStream.jav
    a:194)
    4XESTACKTRACE          at
    com.ibm.comm.NSDeviceOutputStream.write(NSDeviceOutputStream.jav
    a:73)
    4XESTACKTRACE          at
    java.io.DataOutputStream.writeBytes(DataOutputStream.java:282)
    4XESTACKTRACE          at
    com.gap.pos.device.GapSerialConnection_FR.sendRequest(GapSerialC
    onnection_FR.java:428)
    4XESTACKTRACE          at
    com.gap.pos.device.GapSerialConnection_FR.sendACK(GapSerialConne
    ction_FR.java:658)
    4XESTACKTRACE          at
    com.gap.pos.device.GapSerialConnection_FR.readResponse(GapSerial
    Connection_FR.java:316)
    4XESTACKTRACE          at
    com.gap.pos.device.GapSerialConnection_FR.serialEvent(GapSerialC
    onnection_FR.java:375)
    4XESTACKTRACE          at
    com.ibm.comm.NSSerialPort$SerialEventDeliveryThread.run(NSSerial
    Port.java:1314)
    .
    

Local fix

Problem summary

  • The Problem is caused when two threads try to execute
    NSSerialPort$SerialEventDeliveryThread.addEvent() from
    reportSerialEvent() and NSSerialPort.reportSerialEvent().
    

Problem conclusion

  • This defect will be fixed in:
    1.4.2 SR13 FP4 (Linux)
    .
    The javacomm code has been updated to avoid the reported
    deadlock.
    .
    To obtain the fix:
    Install build 20091224 or later
    

Temporary fix

Comments

APAR Information

  • APAR number

    PM01533

  • Reported component name

    JAVA(1.3/1.4 CO

  • Reported component ID

    5648C9800

  • Reported release

    42L

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2009-11-18

  • Closed date

    2009-12-31

  • Last modified date

    2009-12-31

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

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

    IZ75293

Fix information

  • Fixed component name

    JAVA(1.3/1.4 CO

  • Fixed component ID

    5648C9800

Applicable component levels

  • R42L PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SUPPORT","label":"IBM Worldwide Support"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.4.2","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
09 February 2022