IBM Support

PK44835: 'RASD0023W: NO DPNAME ASSOCIATED WITH THAT DPID' WARNING MESSAGE IS LOGGED TO SYSTEMOUT AFTER APPLYING PK38940.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • After applying APAR PK38940, the following warning messages are
    logged many times to SystemOut.log:
    
    [4/27/07 8:17:21:979 EDT] 000000a6 DiagnosticPro W
    com.ibm.ws.rasdiag.DiagnosticProviderRegistry getDPid4DPName
    RASD0023W: No DPName associated with that DPID:
    DPName:ConnMgrDP_JMS$jwds.di.qcf$JMSManagedConnection@923023108
    [4/27/07 8:22:52:000 EDT] 000000a7 DiagnosticPro W
    com.ibm.ws.rasdiag.DiagnosticProviderRegistry getDPid4DPName
    RASD0023W: No DPName associated with that DPID:
    DPName:ConnMgrDP_JMS$jwds.di.qcf$JMSManagedConnection@68420628
    
    The messages can fill up the SystemOut.log file and cause other
    relevant messages to be obscured.  The messages do not cause
    harm and can be safely ignored.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: IBM WebSphere Application Server version     *
    *                 6.1 users seeing too many RASD0023 messages  *
    *                 in their logs                                *
    ****************************************************************
    * PROBLEM DESCRIPTION: Due to a change in the logic flows,     *
    *                      what had been a warning msg is now      *
    *                      a trace msg.                            *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    After handling a memory leak, objects were getting cleaned up
    as expected.  This sometimes led to a phase 2 cleanup finding
    nothing to do.
    

Problem conclusion

  • Because this is no longer an error condition, so the message
    has been modified accordingly.
    
    The fix for this APAR is currently targeted for inclusion
    in fixpack 6.1.0.11.
    Please refer to the recommended updates page for delivery
    information:
    http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK44835

  • Reported component name

    WEBSPH APP SERV

  • Reported component ID

    5724J0800

  • Reported release

    61I

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-05-09

  • Closed date

    2007-08-10

  • Last modified date

    2007-08-10

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

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

Modules/Macros

  • RAS
    

Fix information

  • Fixed component name

    WEBSPH APP SERV

  • Fixed component ID

    5724J0800

Applicable component levels

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"6.1","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
29 December 2021