[jboss-jira] [JBoss JIRA] Issue Comment Edited: (AS7-1431) JBREM00205 when starting domain controller

Mon Aug 1 13:00:23 EDT 2011

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

Andreas Tauber edited comment on AS7-1431 at 8/1/11 12:58 PM:
--------------------------------------------------------------

Sure, it is a domain setup problem.

I reconfigured everthing with two new AS 7 installations and followed "Domain Setup" manual. The problem remains. What I am doing wrong?

Step of configuration:
I start domain controller on linux (192.168.2.100), then host controller on windows (192.168.2.10) is started. 
host-controller boot.log on domain controller prints:
18:08:00,154 INFO  [org.jboss.domain] (pool-3-thread-8) Registered remote slave host staging

No additional instances in admin console.

Shutting down host controller on windows gives error messages of initial post.

I like to provide host.xml of both hosts:

Linux Domain Controller (192.168.2.10):

<host xmlns="urn:jboss:domain:1.0"
      name="master">

    <management>
	    <security-realms>
		    <security-realm name="PropertiesMgmtSecurityRealm">
			    <authentication>
				    <properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir" />
			    </authentication>
		    </security-realm>
	    </security-realms>
       <management-interfaces>
          <native-interface interface="management" port="9999" />
          <http-interface interface="management" port="9990"/>
       </management-interfaces>
    </management>

    <domain-controller>
       <local/>
       <!-- Alternative remote domain controller configuration with a host and port -->
       <!-- <remote host="192.168.100.1" port="9999"/> -->
    </domain-controller>

    <interfaces>
        <interface name="management">
            <inet-address value="192.168.2.100"/>
        </interface>
        <interface name="public">
           <inet-address value="127.0.0.1"/>
        </interface>
    </interfaces>

 	<jvms>
 	   <jvm name="default">
          <heap size="64m" max-size="128m"/>
       </jvm>
 	</jvms>

    <servers>
        <server name="server-one" group="main-server-group">
            <!-- server-one inherits the default socket-group declared in the server-group -->
            <jvm name="default"/>
        </server>

        <server name="server-two" group="main-server-group" auto-start="true">
            <!-- server-two avoids port conflicts by incrementing the ports in
                 the default socket-group declared in the server-group -->
            <socket-binding-group ref="standard-sockets" port-offset="150"/>
            <jvm name="default">
                <heap size="64m" max-size="256m"/>
            </jvm>
        </server>

        <server name="server-three" group="other-server-group" auto-start="false">
            <!-- server-three avoids port conflicts by incrementing the ports in
                 the default socket-group declared in the server-group -->
            <socket-binding-group ref="standard-sockets" port-offset="250"/>
        </server>
    </servers>
</host>

Windows Host Controller (192.168.2.100):
<host xmlns="urn:jboss:domain:1.0"
      name="staging">

    <management>
	    <security-realms>
		    <security-realm name="PropertiesMgmtSecurityRealm">
			    <authentication>
				    <properties path="mgmt-users.properties" relative-to="jboss.domain.config.dir" />
			    </authentication>
		    </security-realm>
	    </security-realms>
       <management-interfaces>
          <native-interface interface="management" port="9999" />
          <http-interface interface="management" port="9990"/>
       </management-interfaces>
    </management>

    <domain-controller>
       <!-- Alternative remote domain controller configuration with a host and port -->
       <remote host="192.168.2.100" port="9999"/> 
    </domain-controller>

    <interfaces>
        <interface name="management">
            <inet-address value="192.168.2.10"/>
        </interface>
        <interface name="public">
           <inet-address value="127.0.0.1"/>
        </interface>
    </interfaces>

 	<jvms>
 	   <jvm name="default">
          <heap size="64m" max-size="128m"/>
       </jvm>
 	</jvms>

    <servers>
        <server name="server-four" group="main-server-group">
            <!-- server-one inherits the default socket-group declared in the server-group -->
            <jvm name="default"/>
        </server>

        <server name="server-five" group="main-server-group" auto-start="true">
            <!-- server-two avoids port conflicts by incrementing the ports in
                 the default socket-group declared in the server-group -->
            <socket-binding-group ref="standard-sockets" port-offset="150"/>
            <jvm name="default">
                <heap size="64m" max-size="256m"/>
            </jvm>
        </server>

        <server name="server-six" group="other-server-group" auto-start="false">
            <!-- server-three avoids port conflicts by incrementing the ports in
                 the default socket-group declared in the server-group -->
            <socket-binding-group ref="standard-sockets" port-offset="250"/>
        </server>
    </servers>
</host>

Only these two files are changed in the two AS 7 installations. 
You are right, looks like a domain controller -> host controller issue. 

      was (Author: AndiTaube):
    Sure, it is a domain setup problem.