Only communication exceptions will cause a failover. If the client proxies know that the request was delivered, the clustering code will never failover. This is to avoid duplicate invocations and also the client proxies really have no way of knowing what you want to do with a request.
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:jboss-development-admin@;lists.sourceforge.net]On Behalf Of > Vishal Shukla > Sent: Thursday, November 07, 2002 1:14 AM > To: [EMAIL PROTECTED] > Subject: [JBoss-dev] JBoss Clustering problem > > > Hello, > > I am facing problem in JBoss Clustering.I am having Two nodes in > cluster.When One node is down.Client Automatically send request > to other node.But if any node is getting the exception like.. > > Could not create entity:org.jboss.util.NestedSQLException: No > ManagedConnections Available!; - nested throwable: > (javax.resource.ResourceException: No ManagedConnections Available!) > at > sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Str > eamRemoteCall.java:240) > at > sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:215) > at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:117) > at > org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) > at > org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPI > nvokerProxy.java:128) > at > org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor. > java:108) > at > org.jboss.proxy.TransactionInterceptor.invoke(TransactionIntercept > or.java:73) > at > org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:76) > at > org.jboss.proxy.ejb.HomeInterceptor.invoke(HomeInterceptor.java:185) > at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:76) > at $Proxy6.create(Unknown Source) > at > net4nuts.usermanagement.UserManagementServlet.processUserData(User > ManagementServlet.java:330) > at > net4nuts.usermanagement.UserManagementServlet.authenticate(UserMan > agementServlet.java:175) > at > net4nuts.usermanagement.UserManagementServlet.doPost(UserManagemen > tServlet.java:95) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:760) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) > at > org.apache.tomcat.core.ServletWrapper.doService(ServletWrapper.java:405) > at org.apache.tomcat.core.Handler.service(Handler.java:287) > at > org.apache.tomcat.core.ServletWrapper.service(ServletWrapper.java:372) > at > org.apache.tomcat.core.ContextManager.internalService(ContextManag > er.java:806) > at > org.apache.tomcat.core.ContextManager.service(ContextManager.java:752) > at > org.apache.tomcat.service.connector.Ajp12ConnectionHandler.process > Connection(Ajp12ConnectionHandler.java:166) > at > org.apache.tomcat.service.TcpWorkerThread.runIt(PoolTcpEndpoint.java:416) > at > org.apache.tomcat.util.ThreadPool$ControlRunnable.run(ThreadPool.java:501) > at java.lang.Thread.run(Thread.java:479) > > Second request again goes to same node....I mean the node which > is getting exception.So please elaborate on this ASAP > > thanks > vishal > > > ------------------------------------------------------- > This sf.net email is sponsored by: See the NEW Palm > Tungsten T handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en > _______________________________________________ > Jboss-development mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-development ------------------------------------------------------- This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
