IBM Support

PM17751: THE CORBA.NO_RESPONSE IS SEEN IN THE NODEAGENT AND SERVERS DUE TO "WSNOPTIMISED", "ADMINAUTHORIZ", "APPSERVERSTAT CODE IN DMGR.

Fixes are available

6.1.0.35: Java SDK 1.5 SR12 FP2 Cumulative Fix for WebSphere
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for AIX
7.0.0.15: Java SDK 1.6 SR9 Cumulative Fix for WebSphere Application Server
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for HP-UX
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for IBM i
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Linux
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Solaris
7.0.0.15: WebSphere Application Server V7.0 Fix Pack 15 for Windows
6.1.0.37: Java SDK 1.5 SR12 FP3 Cumulative Fix for WebSphere
7.0.0.17: WebSphere Application Server V7.0 Fix Pack 17
7.0.0.17: Java SDK 1.6 SR9 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.19: WebSphere Application Server V7.0 Fix Pack 19
7.0.0.21: WebSphere Application Server V7.0 Fix Pack 21
7.0.0.23: WebSphere Application Server V7.0 Fix Pack 23
7.0.0.25: WebSphere Application Server V7.0 Fix Pack 25
7.0.0.27: WebSphere Application Server V7.0 Fix Pack 27
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
6.1.0.47: WebSphere Application Server V6.1 Fix Pack 47
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.27: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
6.1.0.39: Java SDK 1.5 SR12 FP4 Cumulative Fix for WebSphere Application Server
6.1.0.41: Java SDK 1.5 SR12 FP5 Cumulative Fix for WebSphere Application Server
6.1.0.43: Java SDK 1.5 SR13 Cumulative Fix for WebSphere Application Server
6.1.0.45: Java SDK 1.5 SR14 Cumulative Fix for WebSphere Application Server
6.1.0.47: Java SDK 1.5 SR16 Cumulative Fix for WebSphere Application Server
7.0.0.19: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.21: Java SDK 1.6 SR9 FP2 Cumulative Fix for WebSphere
7.0.0.23: Java SDK 1.6 SR10 FP1 Cumulative Fix for WebSphere
7.0.0.25: Java SDK 1.6 SR11 Cumulative Fix for WebSphere Application Server
7.0.0.27: Java SDK 1.6 SR12 Cumulative Fix for WebSphere Application Server
7.0.0.29: Java SDK 1.6 SR13 FP2 Cumulative Fix for WebSphere Application Server
7.0.0.45: Java SDK 1.6 SR16 FP60 Cumulative Fix for WebSphere Application Server
7.0.0.31: Java SDK 1.6 SR15 Cumulative Fix for WebSphere Application Server
7.0.0.35: Java SDK 1.6 SR16 FP1 Cumulative Fix for WebSphere Application Server
7.0.0.37: Java SDK 1.6 SR16 FP3 Cumulative Fix for WebSphere Application Server
7.0.0.39: Java SDK 1.6 SR16 FP7 Cumulative Fix for WebSphere Application Server
7.0.0.41: Java SDK 1.6 SR16 FP20 Cumulative Fix for WebSphere Application Server
7.0.0.43: Java SDK 1.6 SR16 FP41 Cumulative Fix for WebSphere Application Server

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • A CORBA.NO_RESPONSE error is seen in the nodeagent and servers
    due to a delay in response from the deployment manager on the
    following code operations.
    
    "WsnOptimised", "AdminAuthoriz", "AppServerStat" this is short
    classnames that are taking a longer time. Here are the trace
    entries from the dmgr.
    
    1.
    [6/29/10 17:25:37:109 CDT] 000000ed WsnOptimizedN >
    
    performAuthorizationCheck: executeSinglePersistentOperation
    Entry
    [6/29/10 17:25:37:109 CDT] 000000ed WsnOptimizedN <
    performAuthorizationCheck : access granted for
    executeSinglePersistentOperation Exit
    
    2.
    [6/29/10 17:25:37:110 CDT] 000000ed PersistentXml >
    do_executeSinglePersistentOperation Entry
    ..
    [6/29/10 17:28:37:851 CDT] 000000ed PersistentXml <
    do_executeSinglePersistentOperation Exit
    
    3. trace.log:[6/23/10 13:26:21:143 CDT] 000000de PersistentNam >
    
    sendUpdateToSlaveServers Entry
    trace.log:[6/23/10 13:26:21:143 CDT] 000000de PersistentNam 3
    sendUpdateToSlaveServers:
    queryObjectName=WebSphere:type=NameServerPrivate,name=websphere.
    naming.persistent.updates,WsnSlaveProcType=NodeAgent,*
    trace.log:[6/23/10 13:33:37:862 CDT] 000000de PersistentNam 1
    sendUpdateToSlaveServers: querySetSize=2
    trace.log:[6/23/10 13:33:37:863 CDT] 000000de PersistentNam <
    sendUpdateToSlaveServers Exit
    
    The dmgr in fact responds to the nodeagent after the default ORB
    request timeout of 3 minutes by then the nodeagent and client
    also timeout. The folowing queries are changed to improve
    performance.
    
    In the trace,
    
    [6/29/10 17:25:37:269 CDT] 000000ed PersistentNam 3
    sendUpdateToSlaveServers:
    queryObjectName=WebSphere:type=NameServerPrivate,name=websphere.
    naming.persistent.updates,WsnSlaveProcType=NodeAgent,*
    Name=WebSphere:type=NameServerPrivate,name=websphere.naming.pers
    istent.updates,WsnSlaveProcType=NodeAgent,process=nodeagent,*
    
    This is just to improve the query performance as there are fewer
    connections to servers (only node agent, instead of node agent
    and all the servers in the node previously) to look for this
    naming MBean that only exists in the node agent.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:  All users of IBM WebSphere Application      *
    *                  Server Network Deployment edition V6.1 and  *
    *                  V7.0                                        *
    ****************************************************************
    * PROBLEM DESCRIPTION: On a slow network or system, an         *
    *                      org.omg.CORBA.NO_RESPONSE error is      *
    *                      seen when updating persistent name      *
    *                      bindings.                               *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    To enhance the query performance, "process=nodeagent" is added
    to the query where the name server in the dmgr is trying to
    update the node with the new persistent binding info.
    

Problem conclusion

  • Adding "process=nodeagent" to the query for the naming MBean in
    the node agent improves the performance of update persistent
    bindings. Thus avoiding the connection timeout and the
    org.omg.CORBA.NO_RESPONSE error.
    
    The fix for this APAR is currently targeted for inclusion in
    fix packs 6.1.0.35 and fixpack 7.0.0.15. 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

    PM17751

  • Reported component name

    WEBS APP SERV N

  • Reported component ID

    5724H8800

  • Reported release

    61A

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2010-07-01

  • Closed date

    2010-09-10

  • Last modified date

    2010-09-10

  • 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

  • R61A PSY

       UP

  • R61H PSY

       UP

  • R61I PSY

       UP

  • R61P PSY

       UP

  • R61S PSY

       UP

  • R61W PSY

       UP

  • R61Z PSY

       UP

  • R700 PSY

       UP



Document information

More support for: WebSphere Application Server
General

Software version: 6.1

Reference #: PM17751

Modified date: 10 September 2010