August 2014 - mod_cluster-issues - Jboss List Archives

[JBoss JIRA] (MODCLUSTER-114) move the web site to magnolia

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-114?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-114. ------------------------------------- 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 > move the web site to magnolia > ----------------------------- > > Key: MODCLUSTER-114 > URL: https://issues.jboss.org/browse/MODCLUSTER-114 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: The web site needs to be migrated. > Reporter: Jean-Frederic Clere > Assignee: Ryszard Kozmik > Fix For: 1.1.0.CR1 > > > shell scripts will be used for downloads and docs. Docs will be reviewed and edited by hands. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-205) The windoze bundle don't have the default configuration

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-205?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-205. ------------------------------------- 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 windoze bundle don't have the default configuration > ------------------------------------------------------- > > Key: MODCLUSTER-205 > URL: https://issues.jboss.org/browse/MODCLUSTER-205 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.Final > Environment: windows any archu > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.1.1.Final > > > The default files aren't in the bundle so the install fails -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-69) Add ability to disable/enable all/individual apps on a worker from mod_cluster-manager status page

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-69?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-69. ------------------------------------ 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 ability to disable/enable all/individual apps on a worker from mod_cluster-manager status page > -------------------------------------------------------------------------------------------------- > > Key: MODCLUSTER-69 > URL: https://issues.jboss.org/browse/MODCLUSTER-69 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.CR1 > Reporter: Paul Ferraro > Assignee: Jean-Frederic Clere > Fix For: 1.0.0.CR2 > > Attachments: Screenshot-Mod_cluster Status - Mozilla Firefox-1.png > > > Request from Bela. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-181) Read only view of mod_cluster-manager

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-181?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-181. ------------------------------------- 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 > Read only view of mod_cluster-manager > ------------------------------------- > > Key: MODCLUSTER-181 > URL: https://issues.jboss.org/browse/MODCLUSTER-181 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.CR3 > Reporter: Ben Schofield > Assignee: Jean-Frederic Clere > Fix For: 1.1.0.Final > > > mod_cluster-manager lets you view the state of mod_cluster but at the same time exposes admin functions for enabling and disabling contexts. For use cases where someone needs to check the status of mod_cluster but should not have access to modify the state of contexts it would be useful to have a view of mod_cluster-manager without the ability to enable/disable contexts. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-97) httpd should remove workers who crashed

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-97?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-97. ------------------------------------ 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 should remove workers who crashed > --------------------------------------- > > Key: MODCLUSTER-97 > URL: https://issues.jboss.org/browse/MODCLUSTER-97 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.0.1.GA > Reporter: Bela Ban > Assignee: Jean-Frederic Clere > Fix For: 1.1.0.Beta1 > > > When worker W crashes, httpd will not remove it from its worker tables and still try to send requests to W. > We should implement something like ping_mode=I (interval), ping_timeout and connection_ping_interval in mod_jk [1]. > It should work as follows: > - W crashes > - httpd waits for connection_ping_interval of idle time, then starts checking the connection to W every ping_timeout seconds (or ms) > - When the connection to W is broken, httpd should remove W from its worker table and stop the connection checker > - When (if !) W is started again, mod-cluster will register it again with httpd > The configuration above should be done entirely on the AS side, e.g. in HAModClusterConfig. maybe we can find just 1 attribute rather than 3. > [1] http://tomcat.apache.org/connectors-doc/reference/workers.html -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-142) Use UUID for auto-generated jvmRoute

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-142?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-142. ------------------------------------- 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 UUID for auto-generated jvmRoute > ------------------------------------ > > Key: MODCLUSTER-142 > URL: https://issues.jboss.org/browse/MODCLUSTER-142 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.1.0.CR1 > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Fix For: 1.1.0.CR2 > > > Currently, auto-generated jvm-routes are of the form: bind-address:port:engine-name > This exposes internal addresses/ports and is not appropriate for production systems. > To fix that, we can use UUIDs. > e.g. > InetAddress connectorAddress; > int connectorPort; > String engineName; > int addressBytes = connectorAddress.getAddress().length; > int intBytes = Integer.SIZE / Byte.SIZE; > int charBytes = Character.SIZE / Byte.SIZE; > ByteBuffer buffer = ByteBuffer.allocate(addressBytes + intBytes + (engineName.length() * charBytes)); > buffer.put(connectorAddress.getAddress()); > buffer.putInt(connectorPort); > buffer.asCharBuffer().put(engine); > String jvmRoute = UUID.nameUUIDFromBytes(buffer.array()).toString(); > I can think of 2 disadvantages: > 1. UUID jvm-routes will be, on average, longer than the current default, i.e. 36 characters as opposed to ~28. Not a significant difference there. > 2. For development, exposing the address and port via the jvm route might be useful. To satisfy this requirement, we can make the use of UUIDs configurable. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-192) Add SSL stuff in the FAQ

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-192?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-192. ------------------------------------- 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 SSL stuff in the FAQ > ------------------------ > > Key: MODCLUSTER-192 > URL: https://issues.jboss.org/browse/MODCLUSTER-192 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Environment: docs > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.2.1.Final > > > we need something like: > openssl pkcs12 -export -nokeys -in /home/jfclere/CA/cacert.pem -out ca.p12 > because nothing explains how the ca.p12 is created. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-57) Advertise doesn't work when static

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-57?page=com.atlassian.jira.plu... ] Michal Babacek closed MODCLUSTER-57. ------------------------------------ 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 > Advertise doesn't work when static > ---------------------------------- > > Key: MODCLUSTER-57 > URL: https://issues.jboss.org/browse/MODCLUSTER-57 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 1.0.0.Beta3 > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: 1.1.0.Beta1 > > > Advertise doesn't work when static. When buiding a static httpd (to profile it for example) Advertise doesn't work: > [error] mod_advertise: ServerAdvertise Address or Port not defined, Advertise disabled!!! > but when any Advertise directives: > Duplicate ServerAdvertise directives are not allowed -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-300) mod_cluster does generate a JVMRoute with EAP5

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-300?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-300. ------------------------------------- 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 generate a JVMRoute with EAP5 > ---------------------------------------------- > > Key: MODCLUSTER-300 > URL: https://issues.jboss.org/browse/MODCLUSTER-300 > Project: mod_cluster > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: MOD_CLUSTER_1_0_10_GA_CP02 > Reporter: Jean-Frederic Clere > Assignee: Jean-Frederic Clere > Fix For: MOD_CLUSTER_1_0_10_GA_CP03 > > > you get: > [Mon Apr 09 18:18:15 2012] [debug] mod_manager.c(2473): manager_handler CONFIG (/) processing: "Port=8009&Host=127.0.0.1&Type=ajp&StickySessionForce=No&Maxattempts=1" > [Mon Apr 09 18:18:15 2012] [warn] manager_handler CONFIG error: SYNTAX: JVMRoute can't be empty > when you don't configure JvmRoute in the engine. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (MODCLUSTER-281) Make stickySessionForce default to false in native part from 1.2.0 release

by Michal Babacek (JIRA)

[ https://issues.jboss.org/browse/MODCLUSTER-281?page=com.atlassian.jira.pl... ] Michal Babacek closed MODCLUSTER-281. ------------------------------------- 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 > Make stickySessionForce default to false in native part from 1.2.0 release > -------------------------------------------------------------------------- > > Key: MODCLUSTER-281 > URL: https://issues.jboss.org/browse/MODCLUSTER-281 > Project: mod_cluster > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.2.0.Beta4 > Reporter: Radoslav Husar > Assignee: Jean-Frederic Clere > Fix For: 1.2.1.Beta1 > > > Reasoning see AS7-3529, in short, clustering and mod_cluster is about HA, thus the default behavior should be HA as well. > As 7 change: https://github.com/rhusar/jboss-as/commit/f56f9b1c3472a36d17642b18b785402... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

9 years, 8 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