[
https://issues.jboss.org/browse/MODCLUSTER-349?page=com.atlassian.jira.pl...
]
Gregory Lardiere commented on MODCLUSTER-349:
---------------------------------------------
To reproduce the bug, run the attached Java class on a working mod_cluster setup :
{code}java ModCluster349 <apache_hostname> <port> <jvmRoute>
split{code}
You can see on the status page that the context root "/" has been added (instead
of "/ModCluster349") with a incomplete alias list.
On the other hand, if you run :
{code}java ModCluster349 <apache_hostname> <port> <jvmRoute>{code}
then the context-root "/ModCluster349" is correctly added and the alias list is
complete.
mod_manager truncates ENABLE-APP messages
-----------------------------------------
Key: MODCLUSTER-349
URL:
https://issues.jboss.org/browse/MODCLUSTER-349
Project: mod_cluster
Issue Type: Bug
Affects Versions: MOD_CLUSTER_1_0_10_GA_CP04
Environment: Windows Server 2008
JBoss EAP 5.1.0
EWS 1.0.1
Reporter: Gregory Lardiere
Assignee: Jean-Frederic Clere
Attachments: ModCluster349.java, mod_cluster.patch
With lots of aliases, ENABLE-APP messages can be big enough to span several IP packets.
Sometimes, mod_manager will read only the first packet.
The message is therefore incomplete and mod_cluster configuration ends up corrupted :
some aliases are missing and the context-root is replaced by "/".
This is caused by a wrong usage of ap_get_brigade() : it's called only once whereas
it should be called until there's nothing left to read (see the attached patch).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira