August 2014 - mod_cluster-issues - Jboss List Archives

[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)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-111) Create SPI and Isolate tomcat/jbossweb usage into service provider implementation

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-111?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-111. ------------------------------------- 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 > Create SPI and Isolate tomcat/jbossweb usage into service provider implementation > --------------------------------------------------------------------------------- > > Key: MODCLUSTER-111 > URL: https://issues.jboss.org/browse/MODCLUSTER-111 > Project: mod_cluster > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.GA > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.1.0.Beta1 > > > Create SPI for Server, Engine, Connector, Host, Context > Isolate catalina SPI implementation, ContainerEventHandler adapter, and monolithic ModClusterListener into a separate sub-package. > Replace any utilities from JBossWeb/Tomcat with standard/custom facilities, e.g. replace StringManager usage with separate resource bundle facility. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-108) Allow thread factory injection for advertise listener

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-108?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-108. ------------------------------------- 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 > Allow thread factory injection for advertise listener > ----------------------------------------------------- > > Key: MODCLUSTER-108 > URL: https://issues.jboss.org/browse/MODCLUSTER-108 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.0.2.GA > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Minor > Fix For: 1.1.0.Beta1 > > > Isolate advertise configuration from mcmp configuration. Add thread factory method to advertise configuration object. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-66) HAModClusterService needs to handle cluster splits

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-66?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-66. ------------------------------------ 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 > HAModClusterService needs to handle cluster splits > -------------------------------------------------- > > Key: MODCLUSTER-66 > URL: https://issues.jboss.org/browse/MODCLUSTER-66 > Project: mod_cluster > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Beta4 > Reporter: Brian Stansberry > Assignee: Paul Ferraro > Fix For: 1.1.0.Beta1 > > > The case where a split of the JGroups group occurs but nodes are still able to contact the httpd servers needs to be handled. There is a brief discussion of this on https://www.jboss.org/community/docs/DOC-11431 under "Split-Brain Syndrome". Problem is split-brain will result in nodes removing each other from httpd, resulting in no nodes active. > The wiki page describes a simple approach. A more complex approach would be to take a "primary partition" approach, whereby say an initial cluster of size n==6 {A, B, C, D, E, F} splits into two cluster {A, B, C, D} and { E, F}. To continue to handle requests a partition would need to have at least Math.floor((float) n / 2 + 1) members. > What kind of approach is appropriate would probably depend on the deployed webapps and how they interact with the cluster. If there is no clustered state that can become inconsistent across the cluster split, the simple approach described on the wiki can work fine (an HAModClusterService master doesn't disable a node if httpd reports it is still available). If there is shared state that needs to remain consistent (e.g. a clustered Hibernate Second Level Cache) then primary partition works better. > Most likely this overall problem will be resolved in stages, e.g. the simple approach from the wiki first. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-141) Use versioned docs

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-141?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-141. ------------------------------------- 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 > Use versioned docs > ------------------ > > Key: MODCLUSTER-141 > URL: https://issues.jboss.org/browse/MODCLUSTER-141 > Project: mod_cluster > Issue Type: Task > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.CR1 > Reporter: Paul Ferraro > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.1.0.Final > > > Trying to maintain one copy of the documentation for multiple versions simultaneously is proving to be a pain in the @ss... > Magnolia is very cumbersome as a documentation tool because of its treatment of "paragraphs", especially with respect to code fragments (of which our docs have many). > I recommend we keep all of the documentation in subversion (using doxia, docbook or similar) so that it is versioned along with the source code. The download page would contain links to the docs along side binary and source distributions. This seems to be how most jboss.org projects are setup. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-258) Error 503 using mod_cluster

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-258?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-258. ------------------------------------- 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 > Error 503 using mod_cluster > --------------------------- > > Key: MODCLUSTER-258 > URL: https://issues.jboss.org/browse/MODCLUSTER-258 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP02, 1.1.3.Final > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Blocker > Fix For: MOD_CLUSTER_1_0_10_GA_CP03, 1.2.0.Beta4 > > -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-170) Demo servlets throw InstanceNotFoundException against EAP5

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-170?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-170. ------------------------------------- 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 > Demo servlets throw InstanceNotFoundException against EAP5 > ---------------------------------------------------------- > > Key: MODCLUSTER-170 > URL: https://issues.jboss.org/browse/MODCLUSTER-170 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.CR3 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.1.0.Final > > > Thanks to MODCLUSTER-161, now running demo in EAP5 causes: > javax.management.InstanceNotFoundException: jboss.web:type=Server is not registered. > So, make sure we handle both cases. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-56) httpd.worker is a shell script

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-56?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-56. ------------------------------------ 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 > httpd.worker is a shell script > ------------------------------ > > Key: MODCLUSTER-56 > URL: https://issues.jboss.org/browse/MODCLUSTER-56 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.0.CR1 > > > the httpd.worker should be the default mpm model. The build script is wrong it copy an intermediate shell script instead the executable. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-202) the STATUS MCMP message is send before the connector is started

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-202?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-202. ------------------------------------- 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 > the STATUS MCMP message is send before the connector is started > --------------------------------------------------------------- > > Key: MODCLUSTER-202 > URL: https://issues.jboss.org/browse/MODCLUSTER-202 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.5, 1.1.0.Final > Environment: any > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Priority: Minor > Fix For: 1.0.6, 1.1.1.Final > > > If you have an application slow to start the STATUS messages are sent before the connectors are started which causes error messages to be written in the log. > Additionally that can delay the availability of the application to httpd. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-42) mod_proxy_cluster.so missing in hp-ux

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-42?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-42. ------------------------------------ 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_proxy_cluster.so missing in hp-ux > ------------------------------------- > > Key: MODCLUSTER-42 > URL: https://issues.jboss.org/browse/MODCLUSTER-42 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Beta3 > Environment: hp-ux > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.0.0.Beta4 > > > The patch config.m4.patch wasn't applied. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

mod_cluster-issues August 2014