Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

profiles: ha as well as full-ha fail (Wildfly 10) #4

Open
typekpb opened this issue Jul 15, 2016 · 0 comments
Open

profiles: ha as well as full-ha fail (Wildfly 10) #4

typekpb opened this issue Jul 15, 2016 · 0 comments

Comments

@typekpb
Copy link
Contributor

typekpb commented Jul 15, 2016

I'd need to setup ha setup (or even better the full-ha one) on Wildfly 10.

I've tried following:

  1. ha case:
    in: wildfly/domain/domain/configuration/domain.xml changed to:
...
 <server-groups>
        <server-group name="main-server-group" profile="ha">
        ...
        <server-group name="other-server-group" profile="ha">
         ...

once started slave I get:

...
09:11:30,905 INFO  [org.jboss.as.process.Host Controller.status] (main) WFLYPC0018: Starting process 'Host Controller'
[Host Controller] 09:11:31,205 INFO  [org.jboss.modules] (main) JBoss Modules version 1.5.1.Final
[Host Controller] 09:11:31,319 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final
[Host Controller] 09:11:31,351 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) starting
[Host Controller] 09:11:31,755 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.4.Final
[Host Controller] 09:11:31,759 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.4.Final
[Host Controller] 09:11:31,781 INFO  [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 4.0.18.Final
[Host Controller] 09:11:31,789 WARN  [org.jboss.as.domain.management] (MSC service thread 1-8) WFLYDM0002: Whitespace has been trimmed from the Base64 representation of the secret identity.
[Host Controller] 09:11:31,804 INFO  [org.jboss.as.remoting] (MSC service thread 1-6) WFLYRMT0001: Listening on 127.0.0.1:9999
[Host Controller] 09:11:32,972 ERROR [org.jboss.as.controller] (Host Controller Service Threads - 5) WFLYCTL0362: Capabilities required by resource '/profile=ha/subsystem=jgroups/stack=udp/protocol=FD_SOCK' are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-udp-fd in context 'profile=ha'; There are no known registration points which can provide this capability.
[Host Controller] 09:11:32,973 ERROR [org.jboss.as.controller] (Host Controller Service Threads - 5) WFLYCTL0362: Capabilities required by resource '/profile=ha/subsystem=jgroups/stack=udp/transport=UDP' are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-udp in context 'profile=ha'; There are no known registration points which can provide this capability.
[Host Controller] 09:11:32,973 ERROR [org.jboss.as.controller] (Host Controller Service Threads - 5) WFLYCTL0362: Capabilities required by resource '/profile=ha/subsystem=jgroups/stack=tcp/protocol=MPING' are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-mping in context 'profile=ha'; There are no known registration points which can provide this capability.
[Host Controller] 09:11:32,973 ERROR [org.jboss.as.controller] (Host Controller Service Threads - 5) WFLYCTL0362: Capabilities required by resource '/profile=ha/subsystem=jgroups/stack=tcp/transport=TCP' are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-tcp in context 'profile=ha'; There are no known registration points which can provide this capability.
[Host Controller] 09:11:32,974 ERROR [org.jboss.as.controller] (Host Controller Service Threads - 5) WFLYCTL0362: Capabilities required by resource '/profile=ha/subsystem=jgroups/stack=tcp/protocol=FD_SOCK' are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-tcp-fd in context 'profile=ha'; There are no known registration points which can provide this capability.
[Host Controller] 09:11:32,975 ERROR [org.jboss.as.host.controller] (Host Controller Service Threads - 5) WFLYHC0143: Failed to apply domain-wide configuration from master host controller. Operation outcome: failed. Failure description {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {
[Host Controller]     "Operation step-79" => "WFLYCTL0369: Required capabilities are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-udp-fd in context 'profile=ha'; There are no known registration points which can provide this capability.",
[Host Controller]     "Operation step-89" => "WFLYCTL0369: Required capabilities are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-udp in context 'profile=ha'; There are no known registration points which can provide this capability.",
[Host Controller]     "Operation step-95" => "WFLYCTL0369: Required capabilities are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-mping in context 'profile=ha'; There are no known registration points which can provide this capability.",
[Host Controller]     "Operation step-97" => "WFLYCTL0369: Required capabilities are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-tcp-fd in context 'profile=ha'; There are no known registration points which can provide this capability.",
[Host Controller]     "Operation step-106" => "WFLYCTL0369: Required capabilities are not available:
[Host Controller]     org.wildfly.network.socket-binding.jgroups-tcp in context 'profile=ha'; There are no known registration points which can provide this capability."
[Host Controller] }}
[Host Controller] 09:11:32,986 WARN  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0001: Could not connect to remote domain controller remote://172.17.0.2:9999 -- 1-$-
[Host Controller] 09:11:32,986 WARN  [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0147: No domain controller discovery options remain.
[Host Controller] 09:11:32,987 ERROR [org.jboss.as.host.controller] (Controller Boot Thread) WFLYHC0002: Could not connect to master. Aborting. Error was: java.lang.IllegalStateException: WFLYHC0120: Tried all domain controller discovery option(s) but unable to connect
[Host Controller] 09:11:32,997 INFO  [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: WildFly Full 10.0.0.Final (WildFly Core 2.0.10.Final) stopped in 6ms
[Host Controller] 
09:11:33,324 INFO  [org.jboss.as.process.Host Controller.status] (reaper for Host Controller) WFLYPC0011: Process 'Host Controller' finished with an exit status of 99
09:11:33,325 INFO  [org.jboss.as.process] (Thread-8) WFLYPC0017: Shutting down process controller
09:11:33,325 INFO  [org.jboss.as.process] (Thread-8) WFLYPC0016: All processes finished; exiting

  1. full-ha case:
    in: wildfly/domain/domain/configuration/domain.xml changed to:
...
 <server-groups>
        <server-group name="main-server-group" profile="full-ha">
        ...
        <server-group name="other-server-group" profile="full-ha">
         ...

the same trouble as in ha case.

Any idea how to enable ha/full-ha in dockerized setup?

@typekpb typekpb changed the title profiles: ha as well as full-ha fail (Wildfly 9) profiles: ha as well as full-ha fail (Wildfly 10) Jul 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant