Not able to setup a cluster on two W2K machines

Question

          Hi all,
          When I try to start the manager server with
          StartManagedWebLogic.cmd machine1 machine:7001
          I get this exception:
          Starting WebLogic Server ....
          Connecting to http://machine:7001...
          The WebLogic Server did not start up properly.
          Exception raised: weblogic.management.configuration.ConfigurationException: machine1
          not found
          weblogic.management.configuration.ConfigurationException: machine1 not foun
          d
          at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
          at weblogic.management.Admin.initialize(Admin.java:287)
          at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
          at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
          at weblogic.Server.main(Server.java:35)
          Reason: Fatal initialization exception
          Of course, I've created the machine1 on the administration console.
          Please, any suggestions?
          Thanks a lot!
          Pablo.
          

Answer 1

I couldn't find references to "machine1" in your config.xml.
          The error message clearly says "machine1" not found. It appears somehow the
          changes were not written to the config.xml . you might want to double-check that.
          When you create a new server, you should have "machine1" entries as follows
          (replace cls1 with machine1)
          <Server AdministrationPort="0" Cluster="MyCluster"
          ListenAddress="172.17.12.209" ListenPort="7001"
          LogRemoteExceptionsEnabled="true"
          Name="cls1" PreferredSecondaryGroup="G2" ReplicationGroup="G1" StdoutSeverityLevel="64">
          <SSL Name="cls1"/>
          <ServerDebug Name="cls1"/>
          <Log FileName="cls1.log" Name="cls1"/>
          <WebServer DefaultWebApp="DefaultWebApp_cls1" Name="cls1"/>
          <KernelDebug Name="cls1"/>
          </Server>
          Pablo Estades wrote:
          > Yes of course, but they are basically the defaults config.xml.
          >
          > config.xml for machine1 (lab1):
          >
          > <?xml version="1.0" encoding="UTF-8"?>
          > <!--If your domain is active, please do not edit the config.xml file. Any changes
          > made to that file while the domain is active will not have any effect on the domain's
          > configuration and are likely to be lost. If your domain is inactive, you may edit
          > this file with an XML editor. If you do so, please refer to the configuration
          > documentation at http://edocs.bea.com/wls/docs60/adminguide/config_xml.html.
          > In general, we recommend that changes to your configuration file be made through
          > the Administration Console.-->
          > <Domain Name="mydomain">
          > <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          > <Application Deployed="true" Name="certificate" Path=".\config\mydomain\applications">
          > <WebAppComponent Name="certificate" Targets="myserver" URI="certificate.war"/>
          > </Application>
          > <Application Deployed="true" Name="DefaultWebApp_myserver" Path=".\config\mydomain\applications">
          > <WebAppComponent Name="DefaultWebApp_myserver"
          > Targets="myserver" URI="DefaultWebApp_myserver"/>
          > </Application>
          > <Application Deployed="true" Name="console" Path=".\config\mydomain\applications">
          > <WebAppComponent Name="console" Targets="myserver" URI="console.war"/>
          > </Application>
          > <Server ListenPort="7001" Name="myserver" NativeIOEnabled="true">
          > <WebServer DefaultWebApp="DefaultWebApp_myserver"
          > LogFileName="./config/mydomain/logs/access.log"
          > LoggingEnabled="true" Name="myserver"/>
          > <SSL Enabled="true" ListenPort="7002" Name="myserver"
          > ServerCertificateChainFileName="config/mydomain/ca.pem"
          > ServerCertificateFileName="config/mydomain/democert.pem" ServerKeyFileName="config/mydomain/demokey.pem"/>
          > <Log FileName="config/mydomain/logs/weblogic.log" Name="myserver"/>
          > <ServerDebug Name="myserver"/>
          > <KernelDebug Name="myserver"/>
          > </Server>
          > <LDAPRealm AuthProtocol="simple" Credential="MyLDAPCredential"
          > GroupDN="o=airius.com,ou=Groups" GroupIsContext="false"
          > GroupNameAttribute="cn" GroupUsernameAttribute="uniquemember"
          > LDAPURL="ldap://dap:389"
          > Name="defaultLDAPRealmForNetscapeDirectoryServer"
          > Notes="This is provided as an example. Before enabling this Realm, you
          > must edit the configuration parameters as appropriate for your environment."
          > Principal="uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot"
          > UserAuthentication="local" UserDN="o=airius.com,ou=People"
          > UserNameAttribute="uid" UserPasswordAttribute="userpassword"/>
          > <LDAPRealm AuthProtocol="simple" Credential="MyLDAPCredential"
          > GroupDN="o=Microsoft, ou=Groups" GroupIsContext="true"
          > GroupNameAttribute="cn" GroupUsernameAttribute="memberObject"
          > LDAPURL="ldap://ldapserver:389"
          > Name="defaultLDAPRealmForMicrosoftSiteServer"
          > Notes="This is provided as an example. Before enabling this Realm, you
          > must edit the configuration parameters as appropriate for your environment."
          > Principal="cn=ldapadmin" UserAuthentication="local"
          > UserDN="o=Microsoft, ou=Members" UserNameAttribute="cn" UserPasswordAttribute="userpassword"/>
          > <Security GuestDisabled="false" Name="mydomain"
          > PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
          > <ApplicationManager Name="mydomain"/>
          > <FileRealm Name="wl_default_file_realm"/>
          > <Application Name="wl_management_internal1" Path=".\config\tmp">
          > <WebAppComponent Name="wl_management_internal1"
          > Targets="myserver" URI="wl_management_internal1.war"/>
          > </Application>
          > <PasswordPolicy Name="wl_default_password_policy"/>
          > <LDAPRealm AuthProtocol="simple" Credential="MyLDAPCredential"
          > GroupDN="o=airius.com,ou=Groups" GroupIsContext="true"
          > GroupNameAttribute="cn" GroupUsernameAttribute="member"
          > LDAPURL="ldap://ldapserver:363"
          > Name="defaultLDAPRealmForNovellDirectoryServices"
          > Notes="This is provided as an example. Before enabling this Realm, you
          > must edit the configuration parameters as appropriate for your environment."
          > Principal="cn=Admin,o=airius.com" SSLEnable="true"
          > UserAuthentication="bind" UserDN="o=airius.com,ou=People"
          > UserNameAttribute="cn" UserPasswordAttribute="userpassword"/>
          > <CachingRealm
          > BasicRealm="defaultLDAPRealmForNetscapeDirectoryServer"
          > CacheCaseSensitive="true" Name="defaultCachingRealm"/>
          > <Application Name="wl_management_internal2" Path=".\config\tmp">
          > <WebAppComponent Name="wl_management_internal2"
          > Targets="myserver" URI="wl_management_internal2.war"/>
          > </Application>
          > <JTA Name="mydomain"/>
          > <Log FileName="config/mydomain/logs/wl-domain.log" Name="mydomain"/>
          > </Domain>
          >
          > config.xml for machine (pef)
          >
          > <?xml version="1.0" encoding="UTF-8"?>
          > <!--If your domain is active, please do not edit the config.xml file. Any changes
          > made to that file while the domain is active will not have any effect on the domain's
          > configuration and are likely to be lost. If your domain is inactive, you may edit
          > this file with an XML editor. If you do so, please refer to the configuration
          > documentation at http://edocs.bea.com/wls/docs60/adminguide/config_xml.html.
          > In general, we recommend that changes to your configuration file be made through
          > the Administration Console.-->
          > <Domain Name="mydomain">
          > <LDAPRealm AuthProtocol="simple" Credential="MyLDAPCredential"
          > GroupDN="o=Microsoft, ou=Groups" GroupIsContext="true"
          > GroupNameAttribute="cn" GroupUsernameAttribute="memberObject"
          > LDAPURL="ldap://ldapserver:389"
          > Name="defaultLDAPRealmForMicrosoftSiteServer"
          > Notes="This is provided as an example. Before enabling this Realm, you
          > must edit the configuration parameters as appropriate for your environment."
          > Principal="cn=ldapadmin" UserAuthentication="local"
          > UserDN="o=Microsoft, ou=Members" UserNameAttribute="cn" UserPasswordAttribute="userpassword"/>
          > <Log FileName="config/mydomain/logs/wl-domain.log" Name="mydomain"/>
          > <Application Deployed="true" Name="certificate" Path=".\config\mydomain\applications">
          > <WebAppComponent Name="certificate" Targets="miservidor" URI="certificate.war"/>
          > </Application>
          > <JTA Name="mydomain"/>
          > <Realm FileRealm="wl_default_file_realm" Name="wl_default_realm"/>
          > <Application Name="wl_management_internal1" Path=".\config\tmp">
          > <WebAppComponent Name="wl_management_internal1"
          > Targets="miservidor" URI="wl_management_internal1.war"/>
          > </Application>
          > <Server ListenPort="7001" Name="miservidor" NativeIOEnabled="true">
          > <SSL Enabled="true" ListenPort="7002" Name="miservidor"
          > ServerCertificateChainFileName="config/mydomain/ca.pem"
          > ServerCertificateFileName="config/mydomain/democert.pem" ServerKeyFileName="config/mydomain/demokey.pem"/>
          > <ServerDebug Name="miservidor"/>
          > <Log FileName="config/mydomain/logs/weblogic.log" Name="miservidor"/>
          > <WebServer DefaultWebApp="DefaultWebApp_miservidor"
          > LogFileName="./config/mydomain/logs/access.log"
          > LoggingEnabled="true" Name="miservidor"/>
          > <KernelDebug Name="miservidor"/>
          > </Server>
          > <Application Name="wl_management_internal2" Path=".\config\tmp">
          > <WebAppComponent Name="wl_management_internal2"
          > Targets="miservidor" URI="wl_management_internal2.war"/>
          > </Application>
          > <PasswordPolicy Name="wl_default_password_policy"/>
          > <Cluster ClusterAddress="pef" DefaultLoadAlgorithm="round-robin"
          > Name="testCluster" ServiceAgeThresholdSeconds="180"/>
          > <FileRealm Name="wl_default_file_realm"/>
          > <ApplicationManager Name="mydomain"/>
          > <Machine Name="dap"/>
          > <LDAPRealm AuthProtocol="simple" Credential="MyLDAPCredential"
          > GroupDN="o=airius.com,ou=Groups" GroupIsContext="false"
          > GroupNameAttribute="cn" GroupUsernameAttribute="uniquemember"
          > LDAPURL="ldap://ldapserver:389"
          > Name="defaultLDAPRealmForNetscapeDirectoryServer"
          > Notes="This is provided as an example. Before enabling this Realm, you
          > must edit the configuration parameters as appropriate for your environment."
          > Principal="uid=admin, ou=Administrators, ou=TopologyManagement, o=NetscapeRoot"
          > UserAuthentication="local" UserDN="o=airius.com,ou=People"
          > UserNameAttribute="uid" UserPasswordAttribute="userpassword"/>
          > <Application Deployed="true" Name="console" Path=".\config\mydomain\applications">
          > <WebAppComponent Name="console" Targets="miservidor" URI="console.war"/>
          > </Application>
          > <Application Deployed="true" Name="DefaultWebApp_miservidor" Path=".\config\mydomain\applications">
          > <WebAppComponent Name="DefaultWebApp_miservidor"
          > Targets="miservidor" URI="DefaultWebApp_miservidor"/>
          > </Application>
          > <Security GuestDisabled="false" Name="mydomain"
          > PasswordPolicy="wl_default_password_policy" Realm="wl_default_realm"/>
          > <Machine Name="lab1"/>
          > <Machine Name="myserver"/>
          > <LDAPRealm AuthProtocol="simple" Credential="MyLDAPCredential"
          > GroupDN="o=airius.com,ou=Groups" GroupIsContext="true"
          > GroupNameAttribute="cn" GroupUsernameAttribute="member"
          > LDAPURL="ldap://ldapserver:363"
          > Name="defaultLDAPRealmForNovellDirectoryServices"
          > Notes="This is provided as an example. Before enabling this Realm, you
          > must edit the configuration parameters as appropriate for your environment."
          > Principal="cn=Admin,o=airius.com" SSLEnable="true"
          > UserAuthentication="bind" UserDN="o=airius.com,ou=People"
          > UserNameAttribute="cn" UserPasswordAttribute="userpassword"/>
          > </Domain>
          >
          > Thanks.
          >
          > Kumar Allamraju <[email protected]> wrote:
          > >would you mind posting your config.xml?
          > >especially i'm interested in "machine1" related entries..
          > >
          > >Pablo Estades wrote:
          > >
          > >> Hi all,
          > >>
          > >> When I try to start the manager server with
          > >>
          > >> StartManagedWebLogic.cmd machine1 machine:7001
          > >>
          > >> I get this exception:
          > >>
          > >> Starting WebLogic Server ....
          > >> Connecting to http://machine:7001...
          > >> ***************************************************************************
          > >> The WebLogic Server did not start up properly.
          > >> Exception raised: weblogic.management.configuration.ConfigurationException:
          > >machine1
          > >> not found
          > >> weblogic.management.configuration.ConfigurationException: machine1
          > >not foun
          > >> d
          > >> at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:927)
          > >> at weblogic.management.Admin.initialize(Admin.java:287)
          > >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:317)
          > >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
          > >> at weblogic.Server.main(Server.java:35)
          > >> Reason: Fatal initialization exception
          > >> ***************************************************************************
          > >>
          > >> Of course, I've created the machine1 on the administration console.
          > >>
          > >> Please, any suggestions?
          > >>
          > >> Thanks a lot!
          > >> Pablo.
          > >