[jboss-jira] [JBoss JIRA] Resolved: (JBCLUSTER-126) Lookup fails during failover

[Brian Stansberry (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBCLUSTER-126?page=all ]

Brian Stansberry resolved JBCLUSTER-126.
----------------------------------------

    Resolution: Rejected

Please discuss on user forum at http://www.jboss.com/index.html?module=bb&op=viewforum&f=64 before opening a bug.  Also, please file Application Server bugs under the Application Server project, not the Cluster project.  The Cluster project is for high-level planning, and bugs or fixes there can't be associated with specific releases.  Not blaming you for reporting here; it's confusing :)

> Lookup fails during failover
> ----------------------------
>
>                 Key: JBCLUSTER-126
>                 URL: http://jira.jboss.com/jira/browse/JBCLUSTER-126
>             Project: JBoss Clustering
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: Q2Y6
>         Environment: jboss 3.2.6
> OS: SUSE LINUX 10
>            Reporter: Sangeetha Pisharody
>         Assigned To: Brian Stansberry
>             Fix For: Bugs
>
>
> I have a 4 node jboss(3.2.6) cluster. I have a test MBean that runs as a HASingleton on this cluster. All the test MBean does is lookup XAConnectionFactory. Here is the code that does the lookup
> Properties p = System.getProperties();
> p.put(Context.PROVIDER_URL, "localhost:1100");
> Context jndiContext = new InitialContext(p);
> jndiContext.lookup("XAConnectionFactory");
> I tried to stop jboss on the master node and this failed. During this period, another node tried to started this service and it could never get a XAConnectionFactory. This is the exception it threw
> javax.naming.NameNotFoundException: XAConnectionFactory
> at org.jboss.ha.jndi.TreeHead.lookup(TreeHead.java:237)
> at org.jboss.ha.jndi.HAJNDI.lookup(HAJNDI.java:148)
> 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:324)
> at org.jboss.ha.framework.interfaces.HARMIClient.invoke(HARMIClient.java:201)
> at $Proxy42.lookup(Unknown Source)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:621)
> at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:583)
> at javax.naming.InitialContext.lookup(InitialContext.java:347)
> at com.racoman.ccc.mbeansUtils.jmsMonitorService.TestFailoverService.connectToMessageQueue(TestFailoverService.java:133)
> at com.racoman.ccc.mbeansUtils.jmsMonitorService.TestFailoverService.startSingleton(TestFailoverService.java:62)
> 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:324)
> at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:74)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:76)
> at org.jboss.mx.server.Invocation.dispatch(Invocation.java:68)
> at org.jboss.mx.server.Invocation.invoke(Invocation.java:96)
> at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:213)
> at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:484)
> at org.jboss.ha.singleton.HASingletonController.invokeSingletonMBeanMethod(HASingletonController.java:207)
> at org.jboss.ha.singleton.HASingletonController.startSingleton(HASingletonController.java:144)
> at org.jboss.ha.singleton.HASingletonSupport.makeThisNodeMaster(HASingletonSupport.java:197)
> at org.jboss.ha.singleton.HASingletonSupport.partitionTopologyChanged(HASingletonSupport.java:133)
> at org.jboss.ha.jmx.HAServiceMBeanSupport$1.replicantsChanged(HAServiceMBeanSupport.java:211)
> at org.jboss.ha.framework.server.DistributedReplicantManagerImpl.notifyKeyListeners(DistributedReplicantManagerImpl.java:780)
> at org.jboss.ha.framework.server.DistributedReplicantManagerImpl._remove(DistributedReplicantManagerImpl.java:587)
> 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:324)
> at org.jgroups.blocks.MethodCall.invoke(MethodCall.java:236)
> at org.jboss.ha.framework.server.HAPartitionImpl.handle(HAPartitionImpl.java:898)
> at org.jgroups.blocks.RequestCorrelator.handleRequest(RequestCorrelator.java:615)
> at org.jgroups.blocks.RequestCorrelator.receiveMessage(RequestCorrelator.java:512)
> at org.jgroups.blocks.RequestCorrelator.receive(RequestCorrelator.java:326)
> at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.handleUp(MessageDispatcher.java:722)
> at org.jgroups.blocks.MessageDispatcher$ProtocolAdapter.access$300(MessageDispatcher.java:554)
> at org.jgroups.blocks.MessageDispatcher$1.run(MessageDispatcher.java:691)
> at java.lang.Thread.run(Thread.java:534) 
> This happened on our test cluster. 
> On the production cluster, we saw a similar issue when because of a brief network issue the master failed over.
> Services that lookup XAConnectionFactory threw a similar exception.

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