[JBoss JIRA] (MODCLUSTER-439) Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-439?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-439:
--------------------------------------
Fix Version/s: 2.0.0.Alpha1
(was: 1.3.3.Final)
> Installation for Tomcat 6/7/8 is cumbersome, revamp distribution profile
> ------------------------------------------------------------------------
>
> Key: MODCLUSTER-439
> URL: https://issues.jboss.org/browse/MODCLUSTER-439
> Project: mod_cluster
> Issue Type: Feature Request
> Components: Documentation & Demos
> Affects Versions: 1.3.0.Final
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Labels: tomcat
> Fix For: 2.0.0.Alpha1
>
>
> The installation in the docs now expects to go around and copy lots of jars to the /lib dir, the package we ship has all the tomcat 6 and 7 jars in the same spot... we shoud align this to be easier and/or include a readme file in the directory. Also update the documentation for people bulding from source.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (MODCLUSTER-508) &balancer->name[11], becasue of default: balancer://mycluster: Change magic number 11 to something meaningful
by Michal Karm Babacek (JIRA)
Michal Karm Babacek created MODCLUSTER-508:
----------------------------------------------
Summary: &balancer->name[11], becasue of default: balancer://mycluster: Change magic number 11 to something meaningful
Key: MODCLUSTER-508
URL: https://issues.jboss.org/browse/MODCLUSTER-508
Project: mod_cluster
Issue Type: Bug
Components: Native (httpd modules)
Affects Versions: 1.3.2.Final, 1.2.13.Final
Reporter: Michal Karm Babacek
Assignee: Michal Karm Babacek
Priority: Minor
Fix For: 1.3.3.Final
While we compare balancers URL char by char, we start at index 11, because
the default beginning: {{balancer://}} is always there. It would be nice to change 11 to a named constant so as it is clear why it's 11 without debugger :)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ]
Michal Karm Babacek commented on MODCLUSTER-397:
------------------------------------------------
Porting to 1.2.x & tetsing atm.
> StickySessions don't work for ProxyPass from unenabled context
> --------------------------------------------------------------
>
> Key: MODCLUSTER-397
> URL: https://issues.jboss.org/browse/MODCLUSTER-397
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.2.8.Final
> Reporter: Aaron Ogburn
> Assignee: Michal Karm Babacek
> Fix For: 1.3.3.Final, 1.2.13.Final
>
>
> Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd:
> CreateBalancers 1
> ...
> ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (MODCLUSTER-397) StickySessions don't work for ProxyPass from unenabled context
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-397?page=com.atlassian.jira.pl... ]
Michal Karm Babacek reassigned MODCLUSTER-397:
----------------------------------------------
Assignee: Michal Karm Babacek (was: Jean-Frederic Clere)
> StickySessions don't work for ProxyPass from unenabled context
> --------------------------------------------------------------
>
> Key: MODCLUSTER-397
> URL: https://issues.jboss.org/browse/MODCLUSTER-397
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.2.8.Final
> Reporter: Aaron Ogburn
> Assignee: Michal Karm Babacek
> Fix For: 1.3.3.Final, 1.2.13.Final
>
>
> Sticky sessions are not maintained if you try to ProxyPass from an unenabled context to an enabled one. For example, consider JBoss with just /foo deployed and enabled via MCMP. Then try to ProxyPass / to /foo/ on httpd:
> CreateBalancers 1
> ...
> ProxyPass / balancer://mycluster/foo/ stickysession=JSESSIONID|jsessionid nofailover=On
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (MODCLUSTER-466) mod_cluster undersizes the connection pool on httpd 2.2
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-466?page=com.atlassian.jira.pl... ]
Michal Karm Babacek resolved MODCLUSTER-466.
--------------------------------------------
Resolution: Done
It is fixed in 1.2.12+, i.e. 1.2.13 too; and 1.3.2+.
> mod_cluster undersizes the connection pool on httpd 2.2
> -------------------------------------------------------
>
> Key: MODCLUSTER-466
> URL: https://issues.jboss.org/browse/MODCLUSTER-466
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Reporter: Aaron Ogburn
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.13.Final, 1.3.2.Final
>
>
> If all threads in a httpd child worker process are saturated with long requests, then all connections in the pool are exhausted, likely leaving none available for additional pings, which then fail with errors like:
> [error] (70007)The timeout specified has expired: proxy: ajp: failed to acquire connection for ...
> Documentation suggests the connection pool will be sized to ThreadsPerChild+1 to avoid that, but it looks like it is really just ThreadsPerChild on httpd 2.2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months
[JBoss JIRA] (MODCLUSTER-466) mod_cluster undersizes the connection pool on httpd 2.2
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-466?page=com.atlassian.jira.pl... ]
Michal Karm Babacek updated MODCLUSTER-466:
-------------------------------------------
Fix Version/s: 1.3.2.Final
> mod_cluster undersizes the connection pool on httpd 2.2
> -------------------------------------------------------
>
> Key: MODCLUSTER-466
> URL: https://issues.jboss.org/browse/MODCLUSTER-466
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Reporter: Aaron Ogburn
> Assignee: Jean-Frederic Clere
> Fix For: 1.3.2.Final, 1.2.13.Final
>
>
> If all threads in a httpd child worker process are saturated with long requests, then all connections in the pool are exhausted, likely leaving none available for additional pings, which then fail with errors like:
> [error] (70007)The timeout specified has expired: proxy: ajp: failed to acquire connection for ...
> Documentation suggests the connection pool will be sized to ThreadsPerChild+1 to avoid that, but it looks like it is really just ThreadsPerChild on httpd 2.2.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 3 months