[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-347) mod_cluster-manager may break up aliases from a single VirtualHost, causing a messy page

[Michal Babacek (JIRA)]

     [ https://issues.jboss.org/browse/MODCLUSTER-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michal Babacek closed MODCLUSTER-347.
-------------------------------------



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-manager may break up aliases from a single VirtualHost, causing a messy page
> ----------------------------------------------------------------------------------------
>
>                 Key: MODCLUSTER-347
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-347
>             Project: mod_cluster
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.2.4.Final
>         Environment: -JBoss Enterprise Application Platform (EAP 6.1.0)
> -mod_cluster 1.2.4.Final
>            Reporter: Aaron Ogburn
>            Assignee: Jean-Frederic Clere
>             Fix For: 1.2.5.Final
>
>         Attachments: mod_cluster-manager.html
>
>
> Now that we properly show all the individual virtual hosts for a node, mod_cluster-manager may display a messy page with the aliases from a single Virtual Host broken up with multiple instances of the Virtual Host and its contexts.  This can occur with our concurrent start ups now when JBoss has multiple applications bound to virtual servers that are deploying and enabling at once.  The dump output demonstrates the cause:
> balancer: [1] Name: mycluster Sticky: 1 [JSESSIONID]/[jsessionid] remove: 0 force: 0 Timeout: 0 maxAttempts: 1
> node: [1:1],Balancer: mycluster,JVMRoute: 4e6189af-0502-3305-8ff3-fad7fee8b516,LBGroup: [],Host: 127.0.0.1,Port: 8009,Type: ajp,flushpackets: 0,flushwait: 10,ping: 10,smax: 1,ttl: 60,timeout: 0
> host: 1 [example3.com] vhost: 3 node: 1
> host: 2 [example2.com] vhost: 3 node: 1
> host: 3 [example.com] vhost: 3 node: 1
> host: 4 [localhost] vhost: 3 node: 1
> host: 5 [example6.com] vhost: 1 node: 1
> host: 6 [example5.com] vhost: 1 node: 1
> host: 7 [example4.com] vhost: 1 node: 1
> host: 8 [testhost2] vhost: 1 node: 1
> host: 9 [default-host] vhost: 3 node: 1 
> host: 10 [example9.com] vhost: 2 node: 1
> host: 11 [example8.com] vhost: 2 node: 1
> host: 12 [example7.com] vhost: 2 node: 1
> host: 13 [testhost3] vhost: 2 node: 1
> context: 1 [/helloworld2] vhost: 3 node: 1 status: 1
> context: 2 [/helloworld3] vhost: 1 node: 1 status: 1
> context: 3 [/] vhost: 2 node: 1 status: 1
> The messy html representative of this bad output is attached.  Note host entry 9 is for vhost 3, but separated in the html from the other vhost 3 entries.
> The problem is in manager_info_hosts.  It assumes all of those entries will be in order, printing out the Virtual Host/Context lines whenever a different vhost entry is seen.  It'd be much cleaner if we ensured each VirtualHost was only ever printed once on the page.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)