[JBoss JIRA] (MODCLUSTER-429) Some problems were encountered while building the effective model for org.jboss:User-Guide-en:jdocbook:1.3.1.Alpha3-SNAPSHOT
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-429?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-429:
--------------------------------------
Fix Version/s: 1.3.1.Beta2
(was: 1.3.1.Beta1)
> Some problems were encountered while building the effective model for org.jboss:User-Guide-en:jdocbook:1.3.1.Alpha3-SNAPSHOT
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-429
> URL: https://issues.jboss.org/browse/MODCLUSTER-429
> Project: mod_cluster
> Issue Type: Bug
> Components: Core & Container Integration (Java)
> Reporter: Radoslav Husar
> Assignee: Radoslav Husar
> Priority: Minor
> Fix For: 1.3.1.Beta2
>
>
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.jboss:User-Guide-en:jdocbook:1.3.1.Alpha3-SNAPSHOT
> [WARNING] 'artifactId' contains an expression but should be a constant. @ org.jboss:User-Guide-${translation}:1.3.1.Alpha3-SNAPSHOT, /home/rhusar/git/mod_cluster/docs/userguide/pom.xml, line 31, column 17
> [WARNING] 'parent.relativePath' points at org.jboss.mod_cluster:org.jboss.mod_cluster-docs instead of org.jboss:jboss-parent, please verify your project structure @ org.jboss:User-Guide-${translation}:1.3.1.Alpha3-SNAPSHOT, /home/rhusar/git/mod_cluster/docs/userguide/pom.xml, line 24, column 13
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[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: 1.3.1.Beta2
(was: 1.3.1.Beta1)
> 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: 1.3.1.Beta2
>
>
> 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.3.11#6341)
10 years
[JBoss JIRA] (MODCLUSTER-443) mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-443?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-443:
--------------------------------------
Fix Version/s: 1.2.11.Final
> mod_cluster doesn't recognize ; as a proper context delimiter causing 404s on requests with URL jsessionids
> -----------------------------------------------------------------------------------------------------------
>
> Key: MODCLUSTER-443
> URL: https://issues.jboss.org/browse/MODCLUSTER-443
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.2.9.Final, 1.3.1.Alpha2
> Reporter: Aaron Ogburn
> Assignee: Jean-Frederic Clere
> Fix For: 1.3.1.Alpha3, 1.2.11.Final
>
>
> This is similar to MODCLUSTER-328, but in regards to ; instead of ?.
> mod_cluster does not recognize ; as a delimiter when checking the request context. Thus with no trailing slash on index page requests, it treats ;jsessionid as part of the request context and tries to check the balancer for a deployed context of /helloworld;jsessionid=..., which doesn't exist and 404s. Adding the trailing slash, mod_cluster can properly delimit this and then sees the context (so /helloworld/;jsessionid=... works just fine).
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years
[JBoss JIRA] (MODCLUSTER-168) mod_cluster should use hostname provided in address instead a IP address
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-168?page=com.atlassian.jira.pl... ]
Radoslav Husar updated MODCLUSTER-168:
--------------------------------------
Fix Version/s: 1.2.11.Final
(was: 1.2.10.Final)
> mod_cluster should use hostname provided in address instead a IP address
> ------------------------------------------------------------------------
>
> Key: MODCLUSTER-168
> URL: https://issues.jboss.org/browse/MODCLUSTER-168
> Project: mod_cluster
> Issue Type: Feature Request
> Affects Versions: 1.1.0.CR3
> Environment: any
> Reporter: Jean-Frederic Clere
> Assignee: Radoslav Husar
> Fix For: 1.3.1.Alpha3, 1.2.11.Final
>
>
> The CONFIG message contains something like:
> JVMRoute=51ec121e-2976-3d75-bfd9-9e662bbb4bcd&Host=10.33.144.3&Port=8009&Type=ajp
> Even if the Connector is defined like:
> <Connector port="8009" address= "jfcpc" protocol="AJP/1.3" redirectPort="8443" />
> There are 2 ways to fix:
> - Use the String (Change the Connector.java in mod_cluster).
> - Use parameters.put("Host", connector.getAddress().getHostName()); when building the CONFIG message.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years