[JBoss JIRA] Created: (JBAS-7538) Intermittent failure on org.jboss.test.cluster.defaultcfg.test.HAInvokerUnitTestCase.testHttpHAProxyFailover
by Brian Stansberry (JIRA)
Intermittent failure on org.jboss.test.cluster.defaultcfg.test.HAInvokerUnitTestCase.testHttpHAProxyFailover
------------------------------------------------------------------------------------------------------------
Key: JBAS-7538
URL: https://jira.jboss.org/jira/browse/JBAS-7538
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Test Suite
Affects Versions: JBossAS-6.0.0.M1
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M2
Test intermittently fails with:
java.lang.IllegalArgumentException: null object name
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:515)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:662)
at org.jboss.invocation.http.server.HttpInvokerHA.invoke(HttpInvokerHA.java:135)
at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:88)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
at org.jboss.invocation.http.servlet.InvokerServlet.processRequest(InvokerServlet.java:162)
at org.jboss.invocation.http.servlet.InvokerServlet.doPost(InvokerServlet.java:224)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:754)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:847)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:336)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:242)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:276)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191)
at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:183)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:481)
at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:93)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.process(SecurityContextEstablishmentValve.java:126)
at org.jboss.web.tomcat.security.SecurityContextEstablishmentValve.invoke(SecurityContextEstablishmentValve.java:70)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
at org.jboss.web.tomcat.service.jca.CachedConnectionValve.invoke(CachedConnectionValve.java:158)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:366)
at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:872)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653)
at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:951)
at java.lang.Thread.run(Thread.java:619)
--
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
15 years, 10 months
[JBoss JIRA] Created: (JBREM-1160) CLONE -Version compatibility problem with leasing
by Ron Sigal (JIRA)
CLONE -Version compatibility problem with leasing
-------------------------------------------------
Key: JBREM-1160
URL: https://jira.jboss.org/jira/browse/JBREM-1160
Project: JBoss Remoting
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 2.5.1 (Flounder)
Reporter: Ron Sigal
Assignee: Ron Sigal
Fix For: 2.5.2 (Flounder)
If "useClientConnectionIdentity" is set to "true, then org.jboss.remoting.ServerInvoker.updateClientLease() tries to get a leasePingerId from the request map and compare it to the leasePingerId in a Lease. But if the InvocationRequest came from an older client that doesn't know about connection identity, the value of leasePingerId is null. The test calls
leasePingerId.equals(clientLease.getLeasePingerId()
which causes a NullPointerException. The test should be reversed. Also, org.jboss.test.remoting.versioning.lease.LeaseVersionTestCase should be strengthened to catch this problem.
--
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
15 years, 10 months
[JBoss JIRA] Created: (JBAS-7544) HttpInvokerHA doesn't check reachability of HATarget before invoking
by Brian Stansberry (JIRA)
HttpInvokerHA doesn't check reachability of HATarget before invoking
--------------------------------------------------------------------
Key: JBAS-7544
URL: https://jira.jboss.org/jira/browse/JBAS-7544
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: JBossAS-6.0.0.M1, JBossAS-5.1.0.GA
Reporter: Brian Stansberry
Assignee: Brian Stansberry
Fix For: JBossAS-6.0.0.M2
HttpInvokerHA.invoke is missing logic like this found in the other HA detached invokers:
HATarget target = (HATarget)beanMap.get(invocation.getObjectName());
if (target == null)
{
// We could throw IllegalStateException but we have a race condition that could occur:
// when we undeploy a bean, the cluster takes some time to converge
// and to recalculate a new viewId and list of replicant for each HATarget.
// Consequently, a client could own an up-to-date list of the replicants
// (before the cluster has converged) and try to perform an invocation
// on this node where the HATarget no more exist, thus receiving a
// wrong exception and no failover is performed with an IllegalStateException
//
throw new GenericClusteringException(GenericClusteringException.COMPLETED_NO,
"target is not/no more registered on this node");
}
if (!target.invocationsAllowed ())
throw new GenericClusteringException(GenericClusteringException.COMPLETED_NO,
"invocations are currently not allowed on this target");
This is why HAInvokerUnitTestCase.testHttpHAProxyFailover intermittently fails with
java.lang.IllegalArgumentException: null object name
at org.jboss.mx.server.registry.BasicMBeanRegistry.get(BasicMBeanRegistry.java:515)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:662)
at org.jboss.invocation.http.server.HttpInvokerHA.invoke(HttpInvokerHA.java:135)
If the missing code were there, the MBeanServer.invoke call with the null object name would never occur and the client would get a GenericClusteringException that would trigger failover.
--
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
15 years, 10 months