[JBoss JIRA] (MODCLUSTER-5) HASingletonElectionPolicy suitable for mod_cluster
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-5?page=com.atlassian.jira.plug... ]
Michal Babacek closed MODCLUSTER-5.
-----------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> HASingletonElectionPolicy suitable for mod_cluster
> --------------------------------------------------
>
> Key: MODCLUSTER-5
> URL: https://issues.jboss.org/browse/MODCLUSTER-5
> Project: mod_cluster
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Clustering, Web (Tomcat) service
> Reporter: Brian Stansberry
> Assignee: Paul Ferraro
> Fix For: JBossAS-5.1.0.Beta1
>
>
> The determination of a singleton master for the mod_cluster intra-cluster comm component has a couple twists:
> 1) Possibility of one master per mod_cluster domain, rather than one per "cluster"
> 2) Nodes that are unable to communicate with the httpd side for some reason should not be eligible to servce as master.
> Need an HASingletonElectionPolicy impl that can handle these requirements.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-13) LoadMetricSource API
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-13?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-13.
------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> LoadMetricSource API
> --------------------
>
> Key: MODCLUSTER-13
> URL: https://issues.jboss.org/browse/MODCLUSTER-13
> Project: mod_cluster
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: Clustering, Web (Tomcat) service
> Reporter: Brian Stansberry
> Assignee: Paul Ferraro
> Fix For: JBossAS-5.1.0.Beta1
>
>
> Define the API for the LoadMetricSource; what attributes and operations the LoadManager needs.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-214) memory usage growning
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-214?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-214.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> memory usage growning
> ---------------------
>
> Key: MODCLUSTER-214
> URL: https://issues.jboss.org/browse/MODCLUSTER-214
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.8, 1.1.1.Final
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.9, 1.1.2.Final
>
>
> Memory consumption grows by time when using mod_cluster.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-230) Improve documentation on how to use load metrics with Tomcat 6
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-230?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-230.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Improve documentation on how to use load metrics with Tomcat 6
> --------------------------------------------------------------
>
> Key: MODCLUSTER-230
> URL: https://issues.jboss.org/browse/MODCLUSTER-230
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.8
> Reporter: Radoslav Husar
> Assignee: Jean-Frederic Clere
>
> So that people don't get when they only specify the class name (or maybe its more of a problem like MODCLUSTER-183?)
> {code}
> INFO: Starting Coyote AJP/1.3 on ajp-8009
> java.lang.reflect.InvocationTargetException
> 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:597)
> at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:289)
> at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:414)
> Caused by: java.lang.NullPointerException
> at org.jboss.modcluster.ModClusterListener.createLoadBalanceFactorProvider(ModClusterListener.java:104)
> at org.jboss.modcluster.CatalinaEventHandler.init(CatalinaEventHandler.java:119)
> at org.jboss.modcluster.CatalinaEventHandler.init(CatalinaEventHandler.java:56)
> at org.jboss.modcluster.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:127)
> at org.jboss.modcluster.AbstractModClusterService.lifecycleEvent(AbstractModClusterService.java:90)
> at org.jboss.modcluster.ModClusterListener.lifecycleEvent(ModClusterListener.java:132)
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:142)
> at org.apache.catalina.core.StandardServer.start(StandardServer.java:759)
> at org.apache.catalina.startup.Catalina.start(Catalina.java:595)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-88) ClassCastException upon redeploy after mod-cluster-jboss-beans.xml modification
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-88?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-88.
------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> ClassCastException upon redeploy after mod-cluster-jboss-beans.xml modification
> -------------------------------------------------------------------------------
>
> Key: MODCLUSTER-88
> URL: https://issues.jboss.org/browse/MODCLUSTER-88
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.1.GA
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 1.0.2.GA, 1.1.0.Beta1
>
>
> Looks like a classloader problem.
> 2009-07-31 09:52:40,084 INFO
> [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner)
> undeploy, ctxPath=/invoker
> 2009-07-31 09:52:40,168 INFO
> [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner)
> undeploy, ctxPath=/juddi
> 2009-07-31 09:52:40,170 INFO
> [org.apache.juddi.registry.RegistryServlet] (HDScanner) jUDDI Stopping:
> Cleaning up existing resources.
> 2009-07-31 09:52:40,172 INFO
> [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner)
> undeploy, ctxPath=/jbossws
> 2009-07-31 09:52:40,176 INFO
> [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner)
> undeploy, ctxPath=/web-console
> 2009-07-31 09:52:40,182 INFO
> [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner)
> undeploy, ctxPath=/admin-console
> 2009-07-31 09:52:40,186 INFO
> [org.jboss.web.tomcat.service.deployers.TomcatDeployment] (HDScanner)
> undeploy, ctxPath=/jmx-console
> 2009-07-31 09:52:40,225 INFO [org.apache.coyote.http11.Http11Protocol]
> (HDScanner) Pausing Coyote HTTP/1.1 on http-10.254.203.178-8080
> 2009-07-31 09:52:40,230 INFO [org.apache.coyote.http11.Http11Protocol]
> (HDScanner) Stopping Coyote HTTP/1.1 on http-10.254.203.178-8080
> 2009-07-31 09:52:40,231 INFO [org.apache.coyote.ajp.AjpProtocol]
> (HDScanner) Pausing Coyote AJP/1.3 on ajp-10.254.203.178-8009
> 2009-07-31 09:52:40,236 INFO [org.apache.coyote.ajp.AjpProtocol]
> (HDScanner) Stopping Coyote AJP/1.3 on ajp-10.254.203.178-8009
> 2009-07-31 09:52:40,292 INFO [org.apache.catalina.core.StandardService]
> (HDScanner) Stopping service jboss.web
> 2009-07-31 09:52:41,506 ERROR
> [org.jboss.kernel.plugins.dependency.AbstractKernelController]
> (HDScanner) Error installing to Start: name=HAModClusterService
> state=Create mode=On Demand requiredState=Installed
> java.lang.ClassCastException:
> org.jboss.modcluster.ha.ModClusterServiceDRMEntry cannot be cast to
> org.jboss.modcluster.ha.ModClusterServiceDRMEntry
> at
> org.jboss.modcluster.ha.HAModClusterService.narrowCandidateList(HAModClusterService.java:496)
> at
> org.jboss.modcluster.ha.HAModClusterService.getElectionCandidates(HAModClusterService.java:477)
> at
> org.jboss.ha.framework.server.HASingletonImpl.election(HASingletonImpl.java:206)
> at
> org.jboss.ha.framework.server.HASingletonImpl.elected(HASingletonImpl.java:199)
> at
> org.jboss.ha.framework.server.HASingletonImpl.partitionTopologyChanged(HASingletonImpl.java:162)
> at
> org.jboss.ha.framework.server.HASingletonImpl.registerDRMListener(HASingletonImpl.java:124)
> at
> org.jboss.ha.framework.server.HAServiceImpl.start(HAServiceImpl.java:180)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at
> org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at
> org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at
> org.jboss.kernel.plugins.dependency.KernelControllerContextAction$JoinpointDispatchWrapper.execute(KernelControllerContextAction.java:241)
> at
> org.jboss.kernel.plugins.dependency.ExecutionWrapper.execute(ExecutionWrapper.java:47)
> at
> org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchExecutionWrapper(KernelControllerContextAction.java:109)
> at
> org.jboss.kernel.plugins.dependency.KernelControllerContextAction.dispatchJoinPoint(KernelControllerContextAction.java:70)
> at
> org.jboss.kernel.plugins.dependency.LifecycleAction.installActionInternal(LifecycleAction.java:221)
> at
> org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:54)
> at
> org.jboss.kernel.plugins.dependency.InstallsAwareAction.installAction(InstallsAwareAction.java:42)
> at
> org.jboss.dependency.plugins.action.SimpleControllerContextAction.simpleInstallAction(SimpleControllerContextAction.java:62)
> at
> org.jboss.dependency.plugins.action.AccessControllerContextAction.install(AccessControllerContextAction.java:71)
> at
> org.jboss.dependency.plugins.AbstractControllerContextActions.install(AbstractControllerContextActions.java:51)
> at
> org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
> at
> org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at
> org.jboss.system.ServiceController.doChange(ServiceController.java:688)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:460)
> at
> org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
> at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at
> org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at
> org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at
> org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
> at
> org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:286)
> at
> org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
> at
> org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1568)
> at
> org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1533)
> at
> org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:943)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at
> org.jboss.system.ServiceController.doChange(ServiceController.java:688)
> at
> org.jboss.system.ServiceController.start(ServiceController.java:460)
> at
> org.jboss.system.microcontainer.jmx.ServiceControllerStartStopLifecycleCallback.install(ServiceControllerStartStopLifecycleCallback.java:44)
> at sun.reflect.GeneratedMethodAccessor252.invoke(Unknown Source)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:616)
> at
> org.jboss.reflect.plugins.introspection.ReflectionUtils.invoke(ReflectionUtils.java:59)
> at
> org.jboss.reflect.plugins.introspection.ReflectMethodInfoImpl.invoke(ReflectMethodInfoImpl.java:150)
> at
> org.jboss.joinpoint.plugins.BasicMethodJoinPoint.dispatch(BasicMethodJoinPoint.java:66)
> at
> org.jboss.beans.info.plugins.AbstractBeanInfo.invoke(AbstractBeanInfo.java:300)
> at
> org.jboss.kernel.plugins.dependency.AbstractKernelControllerContext.invoke(AbstractKernelControllerContext.java:286)
> at
> org.jboss.dependency.plugins.AbstractLifecycleCallbackItem.install(AbstractLifecycleCallbackItem.java:87)
> at
> org.jboss.dependency.plugins.AbstractController.handleLifecycleCallbacks(AbstractController.java:1568)
> at
> org.jboss.dependency.plugins.AbstractController.handleInstallLifecycleCallbacks(AbstractController.java:1533)
> at
> org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:943)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
> at
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:774)
> at
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:540)
> at
> org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:121)
> at
> org.jboss.deployers.vfs.deployer.kernel.BeanMetaDataDeployer.deploy(BeanMetaDataDeployer.java:51)
> at
> org.jboss.deployers.spi.deployer.helpers.AbstractSimpleRealDeployer.internalDeploy(AbstractSimpleRealDeployer.java:62)
> at
> org.jboss.deployers.spi.deployer.helpers.AbstractRealDeployer.deploy(AbstractRealDeployer.java:50)
> at
> org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:171)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1439)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1157)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1178)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1098)
> at
> org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at
> org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1631)
> at
> org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:934)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at
> org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:984)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:822)
> at
> org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:553)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:781)
> at
> org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:702)
> at
> org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at
> org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:362)
> at
> org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:636)
> 2009-07-31 09:52:41,530 WARN
> [org.jboss.system.server.profileservice.hotdeploy.HDScanner] (HDScanner)
> Failed to process changes
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of
> incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> DEPLOYMENTS IN ERROR:
> Deployment "HAModClusterService" is in error due to the following
> reason(s): java.lang.ClassCastException:
> org.jboss.modcluster.ha.ModClusterServiceDRMEntry cannot be cast to
> org.jboss.modcluster.ha.ModClusterServiceDRMEntry
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:993)
> at
> org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:939)
> at
> org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:873)
> at
> org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
> at
> org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:369)
> at
> org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:255)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at
> java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
> at
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
> at java.lang.Thread.run(Thread.java:636)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-27) Add an httpd handler to display nodes information
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-27?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-27.
------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Add an httpd handler to display nodes information
> -------------------------------------------------
>
> Key: MODCLUSTER-27
> URL: https://issues.jboss.org/browse/MODCLUSTER-27
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.0.Beta1, 1.0.0.Beta2
> Environment: httpd + mod_cluster
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.0.Beta3
>
>
> An httpd handler to display the information in httpd relative to the nodes, contexts and balancers (something like a DUMP or INFO
> command but returned an HTML page).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-121) Mod_cluster does support more that 3 Alias in <Host/>
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-121?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-121.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> Mod_cluster does support more that 3 Alias in <Host/>
> -----------------------------------------------------
>
> Key: MODCLUSTER-121
> URL: https://issues.jboss.org/browse/MODCLUSTER-121
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: 1.0.2 and 1.1.0 Beta1
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Fix For: 1.0.3.GA, 1.1.0.CR1
>
>
> Create <Host/> like:
> <Host name="localhost">
> <Alias>xxxxx.xxxx.xx</Alias>
> <Alias>yyyyy.xxxx.xx</Alias>
> <Alias>yyyy1.xxxx.xx</Alias>
> Start AS and httpd will complain:
> [Wed Jan 06 16:15:39 2010] [debug] mod_manager.c(2053): manager_handler ENABLE-APP (/) processing: "JVMRoute=jfcpc&Alias=localhost,xxxxx.xxxx.xx,yyyyy.xxxx.xx,yyyy1.xxxx.xx&Context=%2fsslapp"
> [Wed Jan 06 16:15:39 2010] [debug] mod_manager.c(1743): manager_handler ENABLE-APP error: MEM: Can't read host alias
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-273) sticky-session-force change requires httpd restart
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-273?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-273.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> sticky-session-force change requires httpd restart
> --------------------------------------------------
>
> Key: MODCLUSTER-273
> URL: https://issues.jboss.org/browse/MODCLUSTER-273
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.4.Final
> Reporter: Christoph Gostner
> Assignee: Jean-Frederic Clere
> Labels: clustering, httpd, jboss-as7
> Fix For: 1.2.0.Final
>
>
> The change of the {{sticky-session-force}} attribute requires a httpd restart.
> Environment:
> Apache with {{mod_cluster}} and two JBoss AS7 (standalone mode but with ha configuration).
> Initial setting:
> # {{sticky-session=true}}
> # {{sticky-session-force=false}}
> Example output:
> {quote}
> 27 28520f70
> Switch to node c178529b
> 28 c178529b took 2 seconds
> 29 c178529b
> {quote}
> The documentation for {{sticky-session-force}} says:
> {quote}
> Indicates whether the httpd proxy should return an error in the event that the balancer is unable to route a request to the node to which it is stuck. This property is ignored if stickySession is false.
> {quote}
> We change {{sticky-session-force}} to {{true}}. Now I expect an 503 error ...
> But nothing happens...
> {quote}
> 5 28520f70
> Switch to node c178529b
> 6 c178529b
> 7 c178529b
> {quote}
> ... after a restart of httpd and JBoss the expected error happens:
> {quote}
> 3 28520f70
> Failed to open "http://ci.objectbay.com:8000/demo7/". Error code - 503.
> Broken between 3 and 0 for 0 seconds.
> Failed to open "http://ci.objectbay.com:8000/demo7/". Error code - 503.
> Broken between 0 and 0 for 1 seconds.
> {quote}
> It seems that the change in the settings requires a complete restart of the cluster environment.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-172) mod_advertise: Invalid ServerAdvertise Address too often
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-172?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-172.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> mod_advertise: Invalid ServerAdvertise Address too often
> --------------------------------------------------------
>
> Key: MODCLUSTER-172
> URL: https://issues.jboss.org/browse/MODCLUSTER-172
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.0.CR3
> Environment: any
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Fix For: 1.1.0.Final
>
>
> The configuration:
> <VirtualHost *:6666>
> ServerName titi.toto.com
> Gives:
> [Fri Jun 25 15:22:16 2010] [crit] (22)Invalid argument: mod_advertise: Invalid ServerAdvertise Address titi.toto.com:0
> Configuration Failed
> but we should be able to guess the port from the VirtualHost...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months
[JBoss JIRA] (MODCLUSTER-102) random 404 errors
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-102?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-102.
-------------------------------------
Closing. Clean-up.
At least one of the following applies:
* the issue has been thoroughly tested as a part of one of the current releases
or
* it hasn't occurred in ~2 years
or
* it's utterly harmless
> random 404 errors
> -----------------
>
> Key: MODCLUSTER-102
> URL: https://issues.jboss.org/browse/MODCLUSTER-102
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.2.GA
> Environment: Linux 2.6.28-15-generic #49-Ubuntu SMP, apache 2.2, JBoss EAP 4.3
> Reporter: Gabor Veres
> Assignee: Jean-Frederic Clere
> Labels: 404
> Fix For: 1.0.3.GA
>
> Attachments: apache2.conf, apache_compiled_modules.txt, demo_client_stdout.log, error.log, httpd.conf, mod_cluster-manager_after.html, mod_cluster-manager_before.html, other_vhosts_access.log, patch.MODCLUSTER-102.ok
>
>
> Stress testing with the mod_cluster provided demo client, or any other web stressing tool shows random 404 errors when accessing resources meant to be provided by the backend JBoss Application Servers. Please see the forum reference for some more details.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
9 years, 8 months