[JBoss JIRA] (MODCLUSTER-93) Update httpd to lastest version
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-93?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-93.
------------------------------------
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
> Update httpd to lastest version
> -------------------------------
>
> Key: MODCLUSTER-93
> URL: https://issues.jboss.org/browse/MODCLUSTER-93
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.2.GA
> Environment: any
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Priority: Blocker
> Fix For: 1.0.2.GA, 1.1.0.Beta1
>
>
> Update httpd to 2.2.13.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-207) Add support for system properties used in 1.0.x
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-207?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-207.
-------------------------------------
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 support for system properties used in 1.0.x
> -----------------------------------------------
>
> Key: MODCLUSTER-207
> URL: https://issues.jboss.org/browse/MODCLUSTER-207
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.0.Final
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 1.1.1.Final
>
>
> To ease 1.0.x -> 1.1.x upgrades, we should support the system properties used in the default mod_cluster-jboss-beans.xml ModClusterConfig bean.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-229) Misbehaving client causes worker to go bad
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-229?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-229.
-------------------------------------
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
> Misbehaving client causes worker to go bad
> ------------------------------------------
>
> Key: MODCLUSTER-229
> URL: https://issues.jboss.org/browse/MODCLUSTER-229
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.9, 1.1.1.Final
> Environment: bad client could mark the worker bad...
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Priority: Blocker
>
> Sending an empty POST triggers the problem
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-265) jboss-admin.sh :list-proxies does not list the proxies I just added with :add-proxies()
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-265?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-265.
-------------------------------------
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
> jboss-admin.sh :list-proxies does not list the proxies I just added with :add-proxies()
> ---------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-265
> URL: https://issues.jboss.org/browse/MODCLUSTER-265
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Environment: modcluster subsystem of AS 7.1 trunk
> Reporter: Misty Stanley-Jones
> Assignee: Jean-Frederic Clere
>
> Apparently :list-proxies only lists proxies that are connected to AS7, not ones that you have added but aren't connected (or don't really resolve). How do you actually list what is in the config? It seems like there should be a command.
> (Sorry if these should be filed in AS7, I was not sure)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-231) mod_cluster forgets removed node too fast
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-231?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-231.
-------------------------------------
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 forgets removed node too fast
> -----------------------------------------
>
> Key: MODCLUSTER-231
> URL: https://issues.jboss.org/browse/MODCLUSTER-231
> Project: mod_cluster
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.10
> Reporter: Radoslav Husar
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Fix For: 1.2.0.Beta4
>
>
> See JBPAPP-6326.
> WAITFORREMOVE should be configurable (as it is currently hardcoded to be 10 seconds).
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-161) NoClassDefFoundError running demo app against AS6
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-161?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-161.
-------------------------------------
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
> NoClassDefFoundError running demo app against AS6
> -------------------------------------------------
>
> Key: MODCLUSTER-161
> URL: https://issues.jboss.org/browse/MODCLUSTER-161
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.0.CR2
> Reporter: Paul Ferraro
> Assignee: Paul Ferraro
> Fix For: 1.1.0.CR3
>
>
> RecordServlet uses an obsolete class (org.apache.catalina.ServerFactory) to obtain a reference to the JBoss Web's Server object. ServerFactory was removed in the upcoming JBoss Web 3.0 release (used in AS6).
> We'll need to use some other mechanism to obtain a reference to the Server.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-208) ClassCastException on updateClusterStatus()
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-208?page=com.atlassian.jira.pl... ]
Michal Babacek closed MODCLUSTER-208.
-------------------------------------
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 on updateClusterStatus()
> -------------------------------------------
>
> Key: MODCLUSTER-208
> URL: https://issues.jboss.org/browse/MODCLUSTER-208
> Project: mod_cluster
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 1.1.0.Final
> Environment: JBoss AS 6.0.0.final
> Reporter: Bela Ban
> Assignee: Jean-Frederic Clere
>
> 13:55:36,731 ERROR [org.apache.catalina.core.ContainerBase] Exception invoking periodic operation: : java.lang.ClassCastException: org.jboss.modcluster.ha.rpc.DefaultRpcResponse cannot be cast to org.jboss.modcluster.ha.rpc.RpcResponse
> at org.jboss.modcluster.ha.HAModClusterService$ClusteredModClusterService.updateClusterStatus(HAModClusterService.java:1222) [:1.1.0.Final]
> at org.jboss.modcluster.ha.HAModClusterService$ClusteredModClusterService.status(HAModClusterService.java:1167) [:1.1.0.Final]
> at org.jboss.modcluster.ha.HAModClusterService.status(HAModClusterService.java:359) [:1.1.0.Final]
> at org.jboss.modcluster.catalina.CatalinaEventHandlerAdapter.lifecycleEvent(CatalinaEventHandlerAdapter.java:314) [:1.1.0.Final]
> at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [:6.0.0.Final]
> at org.apache.catalina.core.ContainerBase.backgroundProcess(ContainerBase.java:1335) [:6.0.0.Final]
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.processChildren(ContainerBase.java:1599) [:6.0.0.Final]
> at org.apache.catalina.core.ContainerBase$ContainerBackgroundProcessor.run(ContainerBase.java:1588) [:6.0.0.Final]
> at java.lang.Thread.run(Thread.java:662) [:1.6.0_23]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months
[JBoss JIRA] (MODCLUSTER-92) add status from the proxy_worker_stat structure to the node information in mod_cluster-manage
by Michal Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-92?page=com.atlassian.jira.plu... ]
Michal Babacek closed MODCLUSTER-92.
------------------------------------
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 status from the proxy_worker_stat structure to the node information in mod_cluster-manage
> ---------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-92
> URL: https://issues.jboss.org/browse/MODCLUSTER-92
> Project: mod_cluster
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 1.0.1.GA
> Environment: any
> Reporter: Jean-Frederic Clere
> Assignee: Jean-Frederic Clere
> Priority: Minor
> Fix For: 1.1.0.Beta1
>
> Attachments: Screenshot-Mod_cluster Status - Mozilla Firefox.png
>
>
> We are already displaying proxystat->elected, proxystat->read, proxystat->transferred, proxystat->busy, proxystat->lbfactor, would be nice to have the proxystat->status.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
10 years, 4 months