Upgrade WebSphere login exception - java.lang.UnsupportedOperationException

book

Article ID: 38582

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal CA Risk Analytics CA Secure Cloud SaaS - Arcot A-OK (WebFort) CLOUDMINDER ADVANCED AUTHENTICATION CA Secure Cloud SaaS - Advanced Authentication CA Secure Cloud SaaS - Identity Management CA Secure Cloud SaaS - Single Sign On

Issue/Introduction

Description:

Some customers upgraded Identity Manager from WAS 6.x to WAS 7.x and ran into the following exception trace in the webphere 7.x log when trying to login into the upgraded Identity Manager:


[8/2/12 10:09:02:195 EDT] 00000025 servlet I
com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [iam_im]
[iam/im] [app/index.jsp]: Initialization successful.
[8/2/12 10:09:02:414 EDT] 00000025 servlet I
com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [iam_im]
[iam/im] [app/ca12/index.jsp]: Initialization successful.
[8/2/12 10:09:02:555 EDT] 00000025 servlet I
com.ibm.ws.webcontainer.servlet.ServletWrapper init SRVE0242I: [iam_im]
[iam/im] [500.jsp]: Initialization successful.
[8/2/12 10:09:02:570 EDT] 00000025 SystemOut O 10:09:02,570 ERROR
[ims.ui] Exception during page display:
java.lang.UnsupportedOperationException
at javax.faces.context.FacesContext.getELContext(FacesContext.java:148)
at javax.faces.component.UIViewRoot.setLocale(UIViewRoot.java:899)
at com.netegrity.webapp.page.jsf.ViewHandler.createView(ViewHandler.java:72)
at
org.apache.myfaces.lifecycle.RestoreViewExecutor.execute(RestoreViewExecutor.j
ava:83)
at
org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:95)
at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:70)
at
com.netegrity.taglib.skin.TagUtilLocal.jsfProcessing(TagUtilLocal.java:359)
at com.netegrity.taglib.skin.TagUtilLocal.update(TagUtilLocal.java:268)
at com.netegrity.taglib.skin.UpdateTag.doEndTag(UpdateTag.java:131)
at ibmjsp.app.ca12.index._jspx_meth_skin_update_0(_index.java:768)
at ibmjsp.app.ca12.index._jspService(_index.java:122)
at com.ibm.ws.jsp.runtime.HttpJspBase.service(HttpJspBase.java:99)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:831)




Solution:

This could be for the reason of the class loading sequence of Web Sphere. 
Look into installation guide for web sphere pages: 78-82. Specifically look into the following on page 80: Edit the user_console.war. Use this procedure to reset the class loader order in the user_console.war file.
Follow these steps to solve this issue:
1. Click Application, WebSphere enterprise applications, iam_im.
2. Under Modules, click Manage modules.
3. Click IMS-UI.
4. Set the class loader order to the following choice:
Classes loaded with local class loader first (parent last)

Environment

Release: CAIDMB99000-12.6.7-Identity Manager-B to B
Component: