[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-2354) HA-CMS: NullPointerException after fail-over

HA-CMS: NullPointerException after fail-over -------------------------------------------- Key: JBPORTAL-2354 URL: https://jira.jboss.org/jira/browse/JBPORTAL-2354 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal CMS Affects Versions: 2.7.1 Final Environment: 2 clustered JBP nodes, loadbalanced with httpd/mod_jk Reporter: Martin Putz Assignee: Sohil Shah Attachments: npe.on.failover.stacktrace.txt If I follow this process: - Boot both nodes, waiting until they are both fully up - Hit a node through load balancer - Click on the 'Register' tab in the 'User profile' portlet - Kill the node serving the portal request - Refresh the browser, failing over to second node - Click on 'Register' tab again I get the following NPE: 2009-03-24 15:29:10,828 DEBUG [org.jnp.interfaces.NamingContext] Failed to connect to 127.0.0.1:1100 javax.naming.CommunicationException: Failed to connect to server 127.0.0.1:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused]] ... 2009-03-24 15:29:10,840 ERROR [org.jboss.portal.jems.ha.HASingletonInvoker] Cannot invoke proxy will no more retry java.lang.NullPointerException at org.jboss.portal.jems.ha.HASingletonInvoker.invoke(HASingletonInvoker.java:147) at org.jboss.portal.cms.impl.jcr.ha.HAJCRCMS.execute(HAJCRCMS.java:107) [full stack trace is attached] We should add a more user friendly exception handling.