IBM Support

PH33127: DFHSJ0007 UNEXPECTED SIGNAL RECEIVED BY JVMSERVER AND CEE5207E THE SIGNAL SIGABRT WAS RECEIVED

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • JVMSERVER hangs. The CICS log permanently shows the message:
    
    DFHSJ0007 Unexpected signal received by JVMSERVER
    
    The Java Error Log JVMERR shows:
    
    CEE5207E The signal SIGABRT was received.
    
    Two system dumps were generated. The dump shows that a TCB
    suffered an 0C4 in DFHCDK64 shortly after NO_ADD_RECOV.
    
    This problem can only occur if SJ level 4 tracing is enabled.
    

Local fix

  • No Local Fix.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All CICS Users.                              *
    ****************************************************************
    * PROBLEM DESCRIPTION: 'DFHSJ0007 UNEXPECTED SIGNAL RECEIVED   *
    *                      BY JVMSERVER' and 'CEE5207E THE SIGNAL  *
    *                      SIGABRT WAS RECEIVED' may be seen when  *
    *                      using a JVMSERVER with SJ level 4 trace *
    *                      enabled, when multiple threads end at   *
    *                      the same time.                          *
    ****************************************************************
    With SJ level 4 trace enabled, when a Java thread is signalled
    to end, trace point TID_SJSC_PTHREAD_EXIT (SJ 0D11) is output.
    However if multiple threads are ending at the same time, such as
    reducing JVMSERVER thread limit, or there are delays within the
    JVMSERVER, before the trace_put call for this point completes,
    the KTCB and associated control blocks including the TAS and
    TCA are freed. As as a result, if this occurs during the
    processing for the trace_put prior to the trace domain call
    errors can occur. This includes an 0C4 abend in DFHCDK64 when
    addressing the TCA, due to this being freed along with the KTCB.
    
    Due to these abends error messages:
     'DFHSJ0007 UNEXPECTED SIGNAL RECEIVED BY JVMSERVER'
    and
     'CEE5207E THE SIGNAL SIGABRT WAS RECEIVED'
    can be seen in the JVMSERVER and region message logs.
    

Problem conclusion

  • The trace point SJ 0D11 has been removed.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH33127

  • Reported component name

    CICS TS Z/OS V5

  • Reported component ID

    5655Y0400

  • Reported release

    100

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2021-01-07

  • Closed date

    2021-07-05

  • Last modified date

    2021-08-09

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

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

    UI76199 UI76200 UI76201 UI76202

Modules/Macros

  • DFHSJSC  DFHSJT8  DFJ@H356 DFJ@H467 DFJ@H468
    

Fix information

  • Fixed component name

    CICS TS Z/OS V5

  • Fixed component ID

    5655Y0400

Applicable component levels

  • R103 PSY UI76202

       UP21/07/08 P F107

  • R10D PSY UI76201

       UP21/07/07 P F107

  • R200 PSY UI76200

       UP21/07/07 P F107

  • R300 PSY UI76199

       UP21/07/07 P F107

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Line of Business":{"code":"LOB35","label":"Mainframe SW"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSGMGV","label":"CICS Transaction Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.4"}]

Document Information

Modified date:
10 August 2021