Fail Over of an Web App
tdevos09 Jan 27, 2009 3:36 AMHi All,
our Cluster looks like the following: Two JBoss AS 4.2.3 with Portal 2.7.1 (clustered binaries) behind two Apache LoadBalancers 2.2.3 with mod_JK 1.2.18.
The Loadbalancing is workinging fine. But I hava a problem with the Failover. If I'm in a WebApp and then shutdown the Jboss I'm working on I will not be able to work on the second Jboss.
In short terms: Both are started up successfully and build a cluster. Then I browse to any webapp for example in the administration area of the portal. Then I shut down the Jboss I'm now working on and I want to switch to another Tab (in the admin area from portlet-Instances to portlet-definitions) then I got the following:
14:06:14,055 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-192.168.1.185-8080 14:06:14,081 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-192.168.1.185-8009 14:06:14,098 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200811061752)] Started in 2m:35s:753ms 08:52:35,646 INFO [JCRCMS] JBossCache Version=1.4.1 08:52:35,654 INFO [JCRCMS] Starting JCR CMS 08:52:37,854 INFO [RepositoryImpl] Starting repository... 08:52:45,957 INFO [JBossCachePersistenceManager] Pre-loading the PersistenceManager Cache in the background (started)....... 08:52:47,150 INFO [JBossCachePersistenceManager] Pre-loading the PersistenceManager Cache for/wsp_ref (finished)....... 08:52:49,908 INFO [JBossCachePersistenceManager] Pre-loading the PersistenceManager Cache for/version_ref (finished)....... 08:52:50,510 INFO [JBossCachePersistenceManager] Pre-loading the PersistenceManager Cache for/wsp_node (finished)....... 08:52:52,407 INFO [JBossCachePersistenceManager] Pre-loading the PersistenceManager Cache for/version_node (finished)....... 08:52:56,836 INFO [JBossCachePersistenceManager] Pre-loading the PersistenceManager Cache for/wsp_prop (finished)....... 08:52:58,925 INFO [JBossCachePersistenceManager] Pre-loading the PersistenceManager Cache for/version_prop (finished)....... 08:53:00,307 INFO [JBossCachePersistenceManager] ------------------------------------------------- 08:53:00,311 INFO [JBossCachePersistenceManager] JBossCachePersistenceManager is fully loaded..... 08:53:00,311 INFO [JBossCachePersistenceManager] ------------------------------------------------- 08:53:01,056 INFO [RepositoryImpl] initializing workspace 'default'... 08:53:01,647 INFO [RepositoryImpl] workspace 'default' initialized 08:53:04,399 INFO [LocalFileSystem] LocalFileSystem initialized at path /opt/jboss-4.2.3.GA/server/portal1/data/portal/cms/conf/workspaces/default/index 08:53:07,687 INFO [SearchIndex] Index initialized: /opt/jboss-4.2.3.GA/server/portal1/data/portal/cms/conf/workspaces/default/index Version: 2 08:53:07,687 INFO [RepositoryImpl] Repository started 08:53:07,688 INFO [JackrabbitJCRService] Repository 'PortalRepository' created 08:53:08,559 INFO [JackrabbitJCRService] The repository has already the CMS node types registered 08:53:08,763 INFO [JCRCMS] Started JCR CMS in: 33s:105ms 08:53:11,431 INFO [TreeCache] viewAccepted(): [192.168.1.186:32852|28] [192.168.1.185:32995] 08:53:11,858 INFO [TreeCache] viewAccepted(): [192.168.1.186:32850|12] [192.168.1.185:32993] 08:53:12,407 INFO [DefaultPartition] New cluster view for partition DefaultPartition (id: 28, delta: -1) : [192.168.1.185:1099] 08:53:12,559 INFO [DefaultPartition] I am (192.168.1.185:1099) received membershipChanged event: 08:53:12,559 INFO [DefaultPartition] Dead members: 1 ([192.168.1.186:1099]) 08:53:12,563 INFO [DefaultPartition] New Members : 0 ([]) 08:53:12,563 INFO [DefaultPartition] All Members : 1 ([192.168.1.185:1099]) 08:53:13,477 INFO [TreeCache] viewAccepted(): [192.168.1.186:32845|28] [192.168.1.185:32988] 08:53:16,483 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../deploy-hasingleton/jms/jbossmq-httpil.sar/jbossmq-httpil.war/ 08:53:19,039 INFO [TreeCache] viewAccepted(): [192.168.1.186:32842|28] [192.168.1.185:32986] 08:53:47,994 ERROR [STDERR] 27.01.2009 08:53:47 org.jboss.portletbridge.AjaxPortletBridge init INFO: Start portletbridge initialization for AdminPortlet 08:53:48,125 ERROR [STDERR] 27.01.2009 08:53:48 org.jboss.portletbridge.AjaxPortletBridge initFaces INFO: Create instance of a JSF lifecycle DEFAULT 08:53:49,301 ERROR [STDERR] 27.01.2009 08:53:49 org.jboss.portletbridge.AjaxPortletBridge init INFO: Done portletbridge initialisation for AdminPortlet 08:53:49,305 ERROR [STDERR] 27.01.2009 08:53:49 org.jboss.portletbridge.AjaxPortletBridge doFacesRequest INFO: Start bridge action request processing for portlet AdminPortlet 08:54:00,261 ERROR [lifecycle] JSF1054: (Phase ID: RESTORE_VIEW 1, View ID: ) Exception thrown during phase execution: javax.faces.event.PhaseEvent[source=com.sun.faces.lifecycle.LifecycleImpl@dd5a9d] 08:54:00,346 ERROR [javax_portlet_faces_GenericFacesPortlet] The portlet threw an exception javax.portlet.PortletException: Error process faces request at javax.portlet.faces.GenericFacesPortlet.processAction(GenericFacesPortlet.java:319) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:557) . . . Caused by: javax.portlet.faces.BridgeException: Error processing render lifecycle at org.jboss.portletbridge.ExceptionHandlerImpl.processActionException(ExceptionHandlerImpl.java:63) . . . Caused by: javax.faces.application.ViewExpiredException: viewId:/jsf/objects.xhtml - View /jsf/objects.xhtml could not be restored. at com.sun.faces.lifecycle.RestoreViewPhase.execute(RestoreViewPhase.java:186) . . . 08:54:00,485 ERROR [DefaultPortalControlPolicy] Rendering portlet window produced an error javax.portlet.PortletException: Error process faces request at javax.portlet.faces.GenericFacesPortlet.processAction(GenericFacesPortlet.java:319) at org.jboss.portal.portlet.impl.jsr168.PortletContainerImpl$Invoker.doFilter(PortletContainerImpl.java:557)
If I reload the WebApp, I have now issues, just when I follow up my original session...
This happens in the portal and with selfmade WebApps builded for running in a cluster... So I think this is a general error in configuration, maybe the loadbalancer, or what ever. At this point I'm out of ideas on how to get this work...
Thanks in advance for reply.
Regards
Thorsten