[jboss-jira] [JBoss JIRA] Commented: (JBPORTAL-2365) Admin Portal Failover Issues

[Mike Millson (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12460290#action_12460290 ] 

Mike Millson commented on JBPORTAL-2365:
----------------------------------------

Now I'm seeing this Nonserializable error:

2009-04-01 23:54:16,915 ERROR [facelets.viewhandler] Error Rendering View[/jsf/index.xhtml]
java.lang.IllegalArgumentException: setAttribute: Non-serializable attribute
        at org.jboss.web.tomcat.service.session.ClusteredSession.setAttribute(ClusteredSession.java:567)
        at org.apache.catalina.session.StandardSessionFacade.setAttribute(StandardSessionFacade.java:130)
        at org.jboss.portal.portlet.impl.jsr168.api.PortletSessionImpl.setAttribute(PortletSessionImpl.java:196)
        at org.jboss.portletbridge.context.PortletExternalContextImpl.setSessionAttribute(PortletExternalContextImpl.java:250)
        at org.jboss.portletbridge.context.AbstractExternalContext$8.setAttribute(AbstractExternalContext.java:487)
        at org.jboss.portletbridge.context.ContextAttributesMap.put(ContextAttributesMap.java:57)
        at org.jboss.portletbridge.context.ContextAttributesMap.put(ContextAttributesMap.java:32)
        at com.sun.faces.mgbean.BeanManager$ScopeManager$SessionScopeHandler.handle(BeanManager.java:442)
        at com.sun.faces.mgbean.BeanManager$ScopeManager.pushToScope(BeanManager.java:417)
        at com.sun.faces.mgbean.BeanManager.createAndPush(BeanManager.java:369)
        at com.sun.faces.mgbean.BeanManager.create(BeanManager.java:222)
        at com.sun.faces.el.ManagedBeanELResolver.getValue(ManagedBeanELResolver.java:88)
        at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:53)
        at com.sun.faces.el.FacesCompositeELResolver.getValue(FacesCompositeELResolver.java:72)
        at com.sun.faces.el.ChainAwareVariableResolver.resolveVariable(ChainAwareVariableResolver.java:108)
        at org.jboss.portal.core.identity.ui.faces.PortletVariableResolver.resolveVariable(PortletVariableResolver.java:102)
...

Also this:
2009-04-02 09:14:12,344 ERROR [org.jboss.web.tomcat.service.session.JBossCacheService] externalizeSession(): exception occurred externalizing session SessionBasedClusteredSession[id: mUIEfa+pyKjT6JCD1zHaXg**.node1 lastAccessedTime: 1238678045174 version: 1 lastOutdated: 0]
java.io.NotSerializableException: org.jboss.portal.core.admin.ui.PortalObjectManagerBean$PortalObjectAuthorizationBean
        - field (class "org.jboss.portal.core.admin.ui.PortalObjectManagerBean", name: "auth", type: "class org.jboss.portal.core.admin.ui.AuthorizationBean")
        - object (class "org.jboss.portal.core.admin.ui.PortalObjectManagerBean", org.jboss.portal.core.admin.ui.PortalObjectManagerBean at 2439a391)
        - custom writeObject data (class "java.util.concurrent.ConcurrentHashMap")
        - root object (class "java.util.concurrent.ConcurrentHashMap", {org.jboss.portletbridge.USER_PRINCIPAL=admin, javax.portlet.p./admin/default/AdminPortletWindow?javax.portlet.faces.viewIdHistory.view=/jsf/objects.xhtml?javax.faces.portletbridge.STATE_ID=AdminPortletmUIEfa+pyKjT6JCD1zHaXg**.node1:view:jbpns_2fadmin_2fdefault_2fAdminPortletWindowsnpbj&javax.portlet.faces.PortletMode=view, javax.portlet.p./admin/default/AdminPortletWindow?dashboardmgr=org.jboss.portal.core.admin.ui.PortalObjectManagerBean at 12d72107, javax.portlet.p./admin/default/AdminPortletWindow?com.sun.faces.application.StateManagerImpl.SerialId=3, javax.portlet.p./admin/default/AdminPortletWindow?org.jboss.portletbridge.WINDOW_ID_RETRIVER=org.jboss.portletbridge.application.PortletStateHolder$WindowIDRetriver at 353f9f30, javax.portlet.p./admin/default/AdminPortletWindow?com.sun.faces.logicalViewMap={j_id1={j_id2=[Ljava.lang.Object;@28fea41a}}, javax.portlet.p./admin/default/AdminPortletWindow?portalobjectmgr=org.jboss.portal.core.admin.ui.PortalObjectManagerBean at 2439a391})

This issue was fixed by these 2 commits:
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/portal?view=rev&revision=13106
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/portal?view=rev&revision=13115

> Admin Portal Failover Issues
> ----------------------------
>
>                 Key: JBPORTAL-2365
>                 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2365
>             Project: JBoss Portal
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Portal Core
>    Affects Versions: 2.7.2 Final
>            Reporter: Mike Millson
>
> Test case:
> 1) Start 2 nodes in a cluster.
> 2) Using jkstatus, stop node2 worker so requests are handled by node1.
> 2) Create new user.
> 3) After you submit the new user, there will be a screen to specify roles for the user. At this point stop node1 and make node2 active so there will be failover to node2.
> 4) Select Admin role for user and click submit.
> This works on 2.6.x.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira