IBM Support

PH55273: PRINT PM.TOSTRING IN FFDC&GENERATE JAVACORE J2CA0045E

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

  • Print PM.toString in FFDC&generate javacore J2CA0045E
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server using trace to debug datasources     *
    ****************************************************************
    * PROBLEM DESCRIPTION: Java cores are not generated at the     *
    *                      time of J2CA0045E messages and are      *
    *                      difficult to capture manually.          *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    Customers are asked to generate java core when a J2CA0045E
    error occurs.  Normally this is a slowdown in the system or a
    deadlock that may be occurring at the time of the J2CA0045E
    erros.  If the problem has already resolve its self and is
    intermittent, capturing java cores after the problem does not
    help.
    The following custom connection pool properties
    ConnWaitTimeoutJavacoreInterval - time between dumps
    MaxConnWaitTimeoutJavacore - times to generate dumps, every
    time, 3 javacores with ConnWaitTimeoutJavacoreInterval interval
    will be generated.
    will automatically generate the java cores closer to the time
    of the problem.
    This APAR also introduces a trace string
    "ConnWaitTimeoutPoolContent=all", if you enable this trace
    string with above 2 properties with value larger than 0, then
    when J2CA0045E or J2CA1010E reports, it will print the pool's
    content into trace.log.
    

Problem conclusion

  • Added custom connection pool properties
    ConnWaitTimeoutJavacoreInterval and MaxConnWaitTimeoutJavacore
    for J2CA0045E errors to help capture intermittent slow downs or
    dead locks that are difficult to capture when manually
    generate java cores. If enable trace string
    "ConnWaitTimeoutPoolContent=all" at same time with the 2
    properties, it will print the pool content into trace log.
    
    The fix for this APAR is targeted for inclusion in fix pack
    8.5.5.25. For more information, see 'Recommended Updates for
    WebSphere Application Server':
    https://www.ibm.com/support/pages/node/715553
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH55273

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2023-06-20

  • Closed date

    2024-02-06

  • Last modified date

    2024-02-06

  • 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

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Line of Business":{"code":"LOB67","label":"IT Automation \u0026 App Modernization"}}]

Document Information

Modified date:
06 February 2024