[ https://issues.jboss.org/browse/AS7-1431?page=com.atlassian.jira.plugin.s... ] Paul Ferraro updated AS7-1431: ------------------------------ Summary: JBREM00205 when starting domain controller (was: JBREM00205 when creating cluster) Assignee: Brian Stansberry (was: Paul Ferraro) Component/s: Domain Management (was: Clustering) I'm re-categorizing and re-titling this jira, as it is not a clustering issue, but rather looks like a domain controller -> host controller communication issue, though probably due to misconfiguration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1431?page=com.atlassian.jira.plugin.s... ] Andreas Tauber edited comment on AS7-1431 at 8/1/11 12:26 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 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. I restarted with two new AS 7 installations and followed "Domain Setup" manual. What I am doing wrong? 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 two AS 7 installations. You are right, looks like a domain controller -> host controller issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1431?page=com.atlassian.jira.plugin.s... ] 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. 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 two AS 7 installations. You are right, looks like a domain controller -> host controller issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1431?page=com.atlassian.jira.plugin.s... ] David Lloyd commented on AS7-1431: ---------------------------------- This may be fixed in the latest upstream. Can you verify? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1431?page=com.atlassian.jira.plugin.s... ] Andreas Tauber commented on AS7-1431: ------------------------------------- Communication between AdminServer and Windows XP Host Controller works, so I am closing ticket. And creating new on with AS7-2268. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira