[jboss-jira] [JBoss JIRA] (WFLY-179) CLONE - Adding modcluster via the CLI fails.

[RH Bugzilla Integration (JIRA)]

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

RH Bugzilla Integration commented on WFLY-179:
----------------------------------------------

Radoslav Husar <rhusar at redhat.com> made a comment on [bug 900801|https://bugzilla.redhat.com/show_bug.cgi?id=900801]

I cannot reproduce this issue. I have created 2 servers using default configuration, where I removed mod_cluster subsystem. I let the servers autostart. I start the domain.

I run the following batch:

> [domain at localhost:9999 /] batch 
> [domain at localhost:9999 / #] /profile=default/subsystem=modcluster:add
> #1 /profile=default/subsystem=modcluster:add
> [domain at localhost:9999 / #] /profile=default/subsystem=modcluster/mod-cluster-config=configuration:add(advertise=false, proxy-list="localhost:6666", connector=http)
> #2 /profile=default/subsystem=modcluster/mod-cluster-config=configuration:add(advertise=false, proxy-list="localhost:6666", connector=http)
> [domain at localhost:9999 / #] /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration:add
> #3 /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration:add
> [domain at localhost:9999 / #] /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration/load-metric=busyness:add(type=busyness)
> #4 /profile=default/subsystem=modcluster/mod-cluster-config=configuration/dynamic-load-provider=configuration/load-metric=busyness:add(type=busyness)
> [domain at localhost:9999 / #] run-batch 
> The batch executed successfully


I get correct logging (from server1) which I am expecting:

> 19:29:48,306 DEBUG [org.jboss.as.controller.management-operation] (host-controller-connection-threads - 1) Entered VERIFY stage; waiting for service container to settle
> 19:29:48,306 DEBUG [org.jboss.as.modcluster] (ServerService Thread Pool -- 48) Starting Mod_cluster Extension
> 19:29:48,327 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 48) MODCLUSTER000001: Initializing mod_cluster ${project.version}
> 19:29:48,331 DEBUG [org.jboss.modcluster] (ServerService Thread Pool -- 48) MODCLUSTER000003: Received server start event
> 19:29:48,334 ERROR [org.jboss.modcluster] (ServerService Thread Pool -- 48) MODCLUSTER000043: Failed to send INFO to localhost/127.0.0.1:6666: java.net.ConnectException: Connection refused

@Alex, what should I do differently to hit an issue?
                
> CLONE - Adding modcluster via the CLI fails.
> --------------------------------------------
>
>                 Key: WFLY-179
>                 URL: https://issues.jboss.org/browse/WFLY-179
>             Project: WildFly
>          Issue Type: Bug
>          Components: CLI, Clustering
>            Reporter: Tom Fonteyne
>            Assignee: Radoslav Husar
>             Fix For: 8.0.0.Alpha1
>
>
> Adding modcluster via the CLI fails.

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