10:35 a.m.
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
10:43 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-2365) Admin Portal Failover Issues
[
https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira....
]
Mike Millson commented on JBPORTAL-2365:
----------------------------------------
Initial exception. This was fixed by portlet bridge revs. 344[1] and 345[2], to be
included in portlet bridge CR1.
2009-04-01 13:20:20,876 ERROR [org.jboss.web.tomcat.service.session.JBossCacheService]
externalizeSession(): exception occurred externalizing session
SessionBasedClusteredSession[id: 8SElm9OxuzBeZVGU57p7Rw**.node1 lastAccessedTime:
1238606418052 version: 1 lastOutdated: 0]
java.io.NotSerializableException: org.jboss.portletbridge.application.PortletStateHolder
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1156)
at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1509)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1474)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at java.util.concurrent.ConcurrentHashMap.writeObject(ConcurrentHashMap.java:1247)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:945)
at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1461)
at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1392)
at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1150)
at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:326)
at
org.jboss.web.tomcat.service.session.SessionBasedClusteredSession.writeExternal(SessionBasedClusteredSession.java:175)
[1]http://fisheye.jboss.org/changelog/PortletBridge/?cs=344
[2]http://fisheye.jboss.org/changelog/PortletBridge/?cs=345
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
10:52 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-2365) Admin Portal Failover Issues
[
https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira....
]
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@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@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@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@2439a391})
This issue was fixed by these 2 commits:
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/portal?view=rev&revision=1...
http://viewvc.jboss.org/cgi-bin/viewvc.cgi/portal?view=rev&revision=1...
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
10:54 a.m.
New subject: [JBoss JIRA] Commented: (JBPORTAL-2365) Admin Portal Failover Issues
[
https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira....
]
Mike Millson commented on JBPORTAL-2365:
----------------------------------------
We are now seeing this error on node2 after set #4 in test case:
2009-04-02 11:17:06,456 ERROR [org.jboss.portal.server.servlet.PortalServlet] Unexpected
exception
java.lang.NullPointerException
at
org.jboss.portal.portlet.controller.PortletRequestHandler.invoke(PortletRequestHandler.java:300)
at
org.jboss.portal.portlet.controller.PortletRequestHandler.invoke(PortletRequestHandler.java:58)
at org.jboss.portal.portlet.controller.RequestHandler.handle(RequestHandler.java:64)
at
org.jboss.portal.portlet.controller.PortletController.process(PortletController.java:179)
at
org.jboss.portal.core.model.portal.command.action.InvokePortletWindowActionCommand.execute(InvokePortletWindowActionCommand.java:181)
at
org.jboss.portal.core.controller.ControllerCommand$1.invoke(ControllerCommand.java:68)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
at
org.jboss.portal.core.aspects.controller.node.EventBroadcasterInterceptor.invoke(EventBroadcasterInterceptor.java:124)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.PageCustomizerInterceptor.invoke(PageCustomizerInterceptor.java:134)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.PolicyEnforcementInterceptor.invoke(PolicyEnforcementInterceptor.java:78)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.node.PortalNodeInterceptor.invoke(PortalNodeInterceptor.java:81)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.BackwardCompatibilityInterceptor.invoke(BackwardCompatibilityInterceptor.java:48)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.ControlInterceptor.invoke(ControlInterceptor.java:56)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.NavigationalStateInterceptor.invoke(NavigationalStateInterceptor.java:42)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.controller.ajax.AjaxInterceptor.invoke(AjaxInterceptor.java:55)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.controller.ResourceAcquisitionInterceptor.invoke(ResourceAcquisitionInterceptor.java:50)
at
org.jboss.portal.core.controller.ControllerInterceptor.invoke(ControllerInterceptor.java:40)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.common.invocation.Invocation.invoke(Invocation.java:157)
at
org.jboss.portal.core.controller.ControllerContext.execute(ControllerContext.java:134)
at org.jboss.portal.core.controller.Controller.processCommand(Controller.java:279)
at org.jboss.portal.core.controller.Controller.handle(Controller.java:261)
at
org.jboss.portal.server.RequestControllerDispatcher.invoke(RequestControllerDispatcher.java:51)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:131)
at
org.jboss.portal.core.cms.aspect.IdentityBindingInterceptor.invoke(IdentityBindingInterceptor.java:47)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.server.aspects.server.ContentTypeInterceptor.invoke(ContentTypeInterceptor.java:68)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.PortalContextPathInterceptor.invoke(PortalContextPathInterceptor.java:45)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.LocaleInterceptor.invoke(LocaleInterceptor.java:96)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at org.jboss.portal.core.aspects.server.UserInterceptor.invoke(UserInterceptor.java:196)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.server.aspects.server.SignOutInterceptor.invoke(SignOutInterceptor.java:98)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.impl.api.user.UserEventBridgeTriggerInterceptor.invoke(UserEventBridgeTriggerInterceptor.java:65)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.IdentityCacheInterceptor.invoke(IdentityCacheInterceptor.java:68)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor.org$jboss$portal$core$aspects$server$TransactionInterceptor$invoke$aop(TransactionInterceptor.java:49)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:253)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
at org.jboss.aspects.tx.TxPolicy.invokeInOurTx(TxPolicy.java:79)
at org.jboss.aspects.tx.TxInterceptor$RequiresNew.invoke(TxInterceptor.java:262)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor$invoke_N5143606530999904530.invokeNext(TransactionInterceptor$invoke_N5143606530999904530.java)
at
org.jboss.portal.core.aspects.server.TransactionInterceptor.invoke(TransactionInterceptor.java)
at org.jboss.portal.server.ServerInterceptor.invoke(ServerInterceptor.java:38)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
at
org.jboss.portal.server.aspects.LockInterceptor$InternalLock.invoke(LockInterceptor.java:69)
at org.jboss.portal.server.aspects.LockInterceptor.invoke(LockInterceptor.java:130)
at org.jboss.portal.common.invocation.Invocation.invokeNext(Invocation.java:115)
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
10:56 a.m.
New subject: [JBoss JIRA] Assigned: (JBPORTAL-2365) Admin Portal Failover Issues
[
https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira....
]
Prabhat Jha reassigned JBPORTAL-2365:
-------------------------------------
Assignee: Chris Laprun
Assigning to Chris because all fixes so far have been done by him.
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
Assignee: Chris Laprun
Fix For: 2.7.3 Final
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
10:56 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-2365) Admin Portal Failover Issues
[
https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira....
]
Prabhat Jha updated JBPORTAL-2365:
----------------------------------
Fix Version/s: 2.7.3 Final
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
Assignee: Chris Laprun
Fix For: 2.7.3 Final
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
10:56 a.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-2365) Admin Portal Failover Issues
[
https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira....
]
Mike Millson updated JBPORTAL-2365:
-----------------------------------
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
Assignee: Chris Laprun
Fix For: 2.7.3 Final
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
1:08 p.m.
New subject: [JBoss JIRA] Updated: (JBPORTAL-2365) Admin Portal Failover Issues
[
https://jira.jboss.org/jira/browse/JBPORTAL-2365?page=com.atlassian.jira....
]
Mike Millson updated JBPORTAL-2365:
-----------------------------------
Description:
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 does not work on 2.6.x either. It appears to because no errors are displayed on
screen or in the server log, but the user is not added to the database. It silently
fails.
was:
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.
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
Assignee: Chris Laprun
Fix For: 2.7.3 Final
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 does not work on 2.6.x either. It appears to because no errors are displayed on
screen or in the server log, but the user is not added to the database. It silently fails.
--
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
6331
days inactive
6336
days old
7 comments
2 participants
participants (2)
-
Mike Millson (JIRA) -
Prabhat Jha (JIRA)