PM79579: "CORBA.NO_IMPLEMENT FORWARD TIME LIMIT REACHED" IS THROWN INCORRECTLY IF A PRECEDING REQUEST ON THE SAME THREAD FAILED

8.0.0.6: WebSphere Application Server V8.0 Fix Pack 6
7.0.0.29: WebSphere Application Server V7.0 Fix Pack 29
8.0.0.7: WebSphere Application Server V8.0 Fix Pack 7
8.0.0.8: WebSphere Application Server V8.0 Fix Pack 8
7.0.0.31: WebSphere Application Server V7.0 Fix Pack 31
7.0.0.33: WebSphere Application Server V7.0 Fix Pack 33
8.0.0.9: WebSphere Application Server V8.0 Fix Pack 9
7.0.0.35: WebSphere Application Server V7.0 Fix Pack 35
8.0.0.10: WebSphere Application Server V8.0 Fix Pack 10
7.0.0.37: WebSphere Application Server V7.0 Fix Pack 37
8.0.0.11: WebSphere Application Server V8.0 Fix Pack 11
7.0.0.39: WebSphere Application Server V7.0 Fix Pack 39
8.0.0.12: WebSphere Application Server V8.0 Fix Pack 12
7.0.0.41: WebSphere Application Server V7.0 Fix Pack 41
8.0.0.13: WebSphere Application Server V8.0 Fix Pack 13
7.0.0.43: WebSphere Application Server V7.0 Fix Pack 43
8.0.0.14: WebSphere Application Server V8.0 Fix Pack 14
7.0.0.45: WebSphere Application Server V7.0 Fix Pack 45
8.0.0.15: WebSphere Application Server V8.0 Fix Pack 15
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

APAR status

• Closed as program error.

Error description

• A thread issued an IIOP request which failed with a
  non-retryable exception (in this case CORBA.NO_RESPONSE).  The
  same thread then issued another IIOP request which failed with
  CORBA.NO_IMPLEMENT Forward time limit reached.  The NO_IMPLEMENT
  exception is erroneous and is caused by residual error status
  saved on the thread from the previous exception.
  

Local fix

• na
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server                                      *
  ****************************************************************
  * PROBLEM DESCRIPTION: CORBA.NO_IMPLEMENT Forward time limit   *
  *                      reached                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  A thread issued an IIOP request which failed with a
  non-retryable exception (in this case CORBA.NO_RESPONSE). The
  same thread then issued another IIOP request which failed with
  CORBA.NO_IMPLEMENT Forward time limit reached.  The
  NO_IMPLEMENT exception is erroneous and is caused by residual
  error status saved on the thread from the previous exception.
  

Problem conclusion

• Code is corrected to clean up the error status of a non-
  retryable exception so that the next request is not affected by
  it.
  
  The fix for this APAR is currently targeted for inclusion in
  fix packs 7.0.0.29, 8.0.0.6, and 8.5.5.  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 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

• R700 PSY

     UP

• R800 PSY

     UP

• R850 PSY

     UP