PM54193: An EmptyStackException occurs when enabling JSF tracing

Interim fix 1 - Rational Application Developer for WebSphere Software, v7.5.5.5

APAR status

• Closed as program error.

Error description

• Abstract:
  
  An EmptyStackExceptions is created as a side effect of the
  debugger trying to access values of components in the wrong
  time.
  
  Problem:
  
  An EmptyStackExceptions is created as a side effect of the
  debugger trying to access values of components in the wrong
  time.
  
  This error message print out only when jsp debug enabled, e.g.:
  'com.ibm.ws.jsf*=all'
  
  Error message example as below:
  [12/2/11 13:46:18:303 GMT+08:00] 00000035 servlet      E
  com.ibm.ws.webcontainer.servlet.ServletWrapper service
  SRVE0068E:
  Uncaught exception created in one of the service methods of the
  servlet Faces Servlet in application MyEAR. Exception created :
  javax.servlet.ServletException
  at
  javax.faces.webapp.FacesServlet.service(FacesServlet.java:277)
  at
  com.ibm.ws.cache.servlet.ServletWrapper.serviceProxied(ServletWr
  apper.java:307)
  ......
  at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905)
  at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1604)
  Caused by: java.util.EmptyStackException
  
  Local fix:
  
  There is no workaround at this time.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  In some particular cases, an EmptyStackException can be
  thrown in JWL's CustomComponentELResolver when for some
  reason the JSF stack view is empty. This should not occur
  but if for any reason the stack view has no items, the
  exception will be shown by the server's log.
  
  This exception is not disrupting or causing any problems in
  the affected applications by it self, but the stack traces
  introduce noise in the logs and debugging of the real
  problem can be harder.
  

Problem conclusion

• A check for empty stack is now performed before attempting
  to peek inside the stack view. The fix for this APAR is
  included in Rational Application Developer v7.5.5.5 iFix1.
  

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

  RATL APP DEV WI

• Fixed component ID

  5724J1901

Applicable component levels

• R700 PSN

     UP