[mod_cluster-issues] [JBoss JIRA] (MODCLUSTER-341) REMOVE-APP with 2 Aliases removes only the first one

[Radoslav Husar (JIRA)]

    [ https://issues.jboss.org/browse/MODCLUSTER-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776350#comment-12776350 ] 

Radoslav Husar commented on MODCLUSTER-341:
-------------------------------------------

Hm, it looks like a little bigger problem -- the unremoved Aliases seems to survive restart as well.

I tried to 
# deploy app on host with 2 aliases
# undeploy it
# the /context is undeployed, first alias is removed, but the remainig aliases stay there:

{noformat}
mod_cluster/1.2.0.Final
Auto Refresh show DUMP output show INFO output
Node 4e6189af-0502-3305-8ff3-fad7fee8b516 (ajp://127.0.0.1:8009):
Enable Contexts Disable Contexts
Balancer: mycluster,LBGroup: ,Flushpackets: Off,Flushwait: 10000,Ping: 10000000,Smax: 26,Ttl: 60000000,Status: OK,Elected: 0,Read: 0,Transferred: 0,Connected: 0,Load: 88
Virtual Host 1:
Contexts:

Aliases:

localhost
example.com

{noformat}

I ll test it more and let you know. Thanks!
                
> REMOVE-APP with 2 Aliases removes only the first one
> ----------------------------------------------------
>
>                 Key: MODCLUSTER-341
>                 URL: https://issues.jboss.org/browse/MODCLUSTER-341
>             Project: mod_cluster
>          Issue Type: Feature Request
>    Affects Versions: 1.2.0.Final
>            Reporter: Radoslav Husar
>            Assignee: Jean-Frederic Clere
>
> Seems like only 1 Alias is removed if the application has been deployed with 2 different Aliases.
> This results in virtual host not being removed.
> Uncovered when testing with Undertow, since it has default-host and localhost defined in the stock config.
> {noformat}
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(1667): manager_trans INFO (/)
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(2323): manager_handler INFO (/) processing: ""
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(2366): manager_handler INFO  OK
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(1667): manager_trans CONFIG (/)
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(2323): manager_handler CONFIG (/) processing: "JVMRoute=5d08300e-37a2-390c-8197-142a84543d60&Host=127.0.0.1&Maxattempts=1&Port=8009&Reversed=true&StickySessionForce=No&Type=ajp&ping=10"
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(2366): manager_handler CONFIG  OK
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(1667): manager_trans ENABLE-APP (/)
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(2323): manager_handler ENABLE-APP (/) processing: "JVMRoute=5d08300e-37a2-390c-8197-142a84543d60&Alias=default-host%2Clocalhost&Context=%2Fclusterbench-ee6-web"
> [Wed May 22 13:57:57 2013] [debug] mod_manager.c(2366): manager_handler ENABLE-APP  OK
> [Wed May 22 13:58:19 2013] [debug] mod_manager.c(1667): manager_trans REMOVE-APP (/)
> [Wed May 22 13:58:19 2013] [debug] mod_manager.c(2323): manager_handler REMOVE-APP (/) processing: "JVMRoute=5d08300e-37a2-390c-8197-142a84543d60&Alias=default-host%2Clocalhost&Context=%2Fclusterbench-ee6-web"
> [Wed May 22 13:58:19 2013] [debug] mod_manager.c(2366): manager_handler REMOVE-APP  OK
> {noformat}

--
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