Can't start manager server on other machine from admin console

hi, m fredzh
i have weblogic 10.3.2 where i created a cluster named cluster1 on production mode
the machines and servers list as follow:
cluster1 192.168.1.100
--machine1
--server1 192.168.1.100
--machine2
-server2 192.168.1.101
i create nodemanager on machine2, and set the type as ssl, the listener address 192.168.1.101,
then login on 192.168.1.101, and run wlst.sh , nmEnroll and then start startNodemanaged.sh ..
start server2 on the admin console(on 192.168.1.100), failed and the log as follow:
can anbody help me, thank you..
==============================================================================
<Critical> <WebLogicServer> <localhost.localdomain> <managerServer2> <main> <<WLS Kernel>> <> <> <1286788326928> <BEA-000386> <Server subsystem failed. Reason: java.lang.AssertionError: java.lang.reflect.InvocationTargetException
java.lang.AssertionError: java.lang.reflect.InvocationTargetException
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:175)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused By: weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte.
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptBytes(JSafeEncryptionServiceImpl.java:125)
at weblogic.security.internal.encryption.JSafeEncryptionServiceImpl.decryptString(JSafeEncryptionServiceImpl.java:173)
at weblogic.security.internal.encryption.ClearOrEncryptedService.decrypt(ClearOrEncryptedService.java:96)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy._invokeServiceMethod(DescriptorManager.java:173)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl$SecurityProxy.decrypt(DescriptorManager.java:192)
at weblogic.descriptor.DescriptorManager$SecurityServiceImpl.decrypt(DescriptorManager.java:114)
at weblogic.descriptor.internal.AbstractDescriptorBean._decrypt(AbstractDescriptorBean.java:991)
at weblogic.management.configuration.SecurityConfigurationMBeanImpl.getCredential(SecurityConfigurationMBeanImpl.java:709)
at weblogic.security.internal.ServerPrincipalValidatorImpl.getSecret(ServerPrincipalValidatorImpl.java:88)
at weblogic.security.internal.ServerPrincipalValidatorImpl.sign(ServerPrincipalValidatorImpl.java:67)
at weblogic.security.service.PrivilegedActions$SignPrincipalAction.run(PrivilegedActions.java:62)
at java.security.AccessController.doPrivileged(Native Method)
at weblogic.security.service.SecurityServiceManager.createServerID(SecurityServiceManager.java:1098)
at weblogic.security.service.SecurityServiceManager.getServerID(SecurityServiceManager.java:1111)
at weblogic.security.service.SecurityServiceManager.sendASToWire(SecurityServiceManager.java:602)
at weblogic.server.channels.ChannelService.resetQOS(ChannelService.java:284)
at weblogic.server.channels.ChannelService.start(ChannelService.java:250)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Edited by: fredzh on 2010-10-12 下午6:54

hi,Jay
i followed the steps as follow:
1、change prod mode to dev
2、modified the config.xml entrys on the all two servers:
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<credential-encrypted>test</credential-encrypted>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
3、enrolled the node, then started the two adminservers, started server2's nodemanager..server2 can be started from the cluster admin console.
4、change the dev mode to prod mode on admin console, it failed throw error:
"in production mode, it's not allowed to set a clear text value to the property: CredentialEncrypted of SecurityConfigurationMBean"
i checked the config.xml ,the entrys i had changed were not aotomatically encrypted,may i manually encryp the clear text value? ..follow is the config.xml :
<?xml version='1.0' encoding='UTF-8'?>
<domain xmlns="http://xmlns.oracle.com/weblogic/domain" xmlns:sec="http://xmlns.oracle.com/weblogic/security" xmlns:wls="http://xmlns.oracle.com/weblogic/security/wls" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://xmlns.oracle.com/weblogic/security/xacml http://xmlns.oracle.com/weblogic/security/xacml/1.0/xacml.xsd http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator/1.0/passwordvalidator.xsd http://xmlns.oracle.com/weblogic/domain http://xmlns.oracle.com/weblogic/1.0/domain.xsd http://xmlns.oracle.com/weblogic/security http://xmlns.oracle.com/weblogic/1.0/security.xsd http://xmlns.oracle.com/weblogic/security/wls http://xmlns.oracle.com/weblogic/security/wls/1.0/wls.xsd">
<name>cluster_domain</name>
<domain-version>10.3.2.0</domain-version>
<security-configuration>
<name>cluster_domain</name>
<realm>
<sec:authentication-provider xsi:type="wls:default-authenticatorType"></sec:authentication-provider>
<sec:authentication-provider xsi:type="wls:default-identity-asserterType">
<sec:active-type>AuthenticatedUser</sec:active-type>
</sec:authentication-provider>
<sec:role-mapper xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-role-mapperType"></sec:role-mapper>
<sec:authorizer xmlns:xac="http://xmlns.oracle.com/weblogic/security/xacml" xsi:type="xac:xacml-authorizerType"></sec:authorizer>
<sec:adjudicator xsi:type="wls:default-adjudicatorType"></sec:adjudicator>
<sec:credential-mapper xsi:type="wls:default-credential-mapperType"></sec:credential-mapper>
<sec:cert-path-provider xsi:type="wls:web-logic-cert-path-providerType"></sec:cert-path-provider>
<sec:cert-path-builder>WebLogicCertPathProvider</sec:cert-path-builder>
<sec:name>myrealm</sec:name>
<sec:password-validator xmlns:pas="http://xmlns.oracle.com/weblogic/security/providers/passwordvalidator" xsi:type="pas:system-password-validatorType">
<sec:name>SystemPasswordValidator</sec:name>
<pas:min-password-length>8</pas:min-password-length>
<pas:min-numeric-or-special-characters>1</pas:min-numeric-or-special-characters>
</sec:password-validator>
</realm>
<default-realm>myrealm</default-realm>
<anonymous-admin-lookup-enabled>false</anonymous-admin-lookup-enabled>
<credential-encrypted>test</credential-encrypted>
<web-app-files-case-insensitive>false</web-app-files-case-insensitive>
<compatibility-connection-filters-enabled>false</compatibility-connection-filters-enabled>
<node-manager-username>weblogic</node-manager-username>
<node-manager-password-encrypted>test</node-manager-password-encrypted>
<principal-equals-case-insensitive>false</principal-equals-case-insensitive>
<principal-equals-compare-dn-and-guid>false</principal-equals-compare-dn-and-guid>
<downgrade-untrusted-principals>false</downgrade-untrusted-principals>
<enforce-strict-url-pattern>true</enforce-strict-url-pattern>
<cross-domain-security-enabled>false</cross-domain-security-enabled>
</security-configuration>
<jta>
<security-interop-mode>default</security-interop-mode>
</jta>
<server>
<name>AdminServer</name>
<ssl>
<hostname-verifier xsi:nil="true"></hostname-verifier>
<hostname-verification-ignored>true</hostname-verification-ignored>
<export-key-lifespan>500</export-key-lifespan>
<client-certificate-enforced>false</client-certificate-enforced>
<two-way-ssl-enabled>false</two-way-ssl-enabled>
<ssl-rejection-logging-enabled>true</ssl-rejection-logging-enabled>
<inbound-certificate-validation>BuiltinSSLValidationOnly</inbound-certificate-validation>
<outbound-certificate-validation>BuiltinSSLValidationOnly</outbound-certificate-validation>
<allow-unencrypted-null-cipher>false</allow-unencrypted-null-cipher>
<use-server-certs>false</use-server-certs>
</ssl>
<listen-port>7110</listen-port>
<listen-address></listen-address>
</server>
<server>
<name>server2</name>
<machine>machine2</machine>
<listen-port>7110</listen-port>
<listen-address>192.168.1.101</listen-address>
<server-start>
<java-vendor>Sun</java-vendor>
<java-home>/opt/jdk1.6.0_21</java-home>
<bea-home>/root/Oracle/Middleware</bea-home>
<root-directory>/root/Oracle/Middleware/user_projects/domains/cluster_domain</root-directory>
<username>weblogic</username>
<password-encrypted>{AES}xhSI75AxXtXdMrCXRgA2uY5pfcxUGE9X4YXTjfe1XEY=</password-encrypted>
</server-start>
</server>
<embedded-ldap>
<name>cluster_domain</name>
<credential-encrypted>test</credential-encrypted>
</embedded-ldap>
<configuration-version>10.3.2.0</configuration-version>
<machine xsi:type="unix-machineType">
<name>machine2</name>
<node-manager>
<nm-type>SSL</nm-type>
<listen-address>192.168.1.101</listen-address>
<listen-port>5556</listen-port>
<debug-enabled>false</debug-enabled>
</node-manager>
</machine>
<admin-server-name>AdminServer</admin-server-name>
</domain>
Edited by: fredzh on 2010-10-13 下午7:57

Similar Messages

MANAGED SERVER NOT COMMING UP FROM ADMIN CONSOLE,

Hi All,
I can't start managed server from admin console.
The status is showing FAILED_NOT_RESTARTABLE.
below is the error it is showing in the node manager.
But i can start managed server from the back-end successfully. If i start the nodemanager then managed server is not comming up.
<May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed
_server'>
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
May 24, 2011 4:12:22 AM weblogic.nodemanager.server.Handler handleStart
WARNING: Exception while starting server 'my_managed_server'
java.io.IOException: Server failed to start up. See server output log for more d
etails.
at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServe
rManager.java:200)
at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23
at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Please help.
Regards,
nag.

<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Working directory is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain'>
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Rotated server output log to "C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out00039">
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server error log also redirected to server log>
<May 24, 2011 4:12:18 AM> <INFO> <weblogic_domain> <my_managed_server> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\weblogic_domain\servers\my_managed_server\logs\my_managed_server.out'>
<May 24, 2011 4:12:22 AM> <INFO> <weblogic_domain> <my_managed_server> <Server failed during startup so will not be restarted>
<May 24, 2011 4:12:22 AM> <WARNING> <Exception while starting server 'my_managed_server'>
java.io.IOException: Server failed to start up. See server output log for more details.
     at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:200)
     at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
     at weblogic.nodemanager.server.Handler.handleStart(Handler.java:604)
     at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
     at weblogic.nodemanager.server.Handler.run(Handler.java:71)
     at java.lang.Thread.run(Thread.java:662)
This is what i found in nodemanager log file
Regards,
Nag.

How to start managed server on Weblogic 9.1 Admin console with jRockit

I configured a new 9.1 domain with jRockit as the JVM. Under Server Start, I used -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause in the Argument field. When I tried to start the server, I am getting the following error:
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Starting WebLogic server with command line: C:\bea\jrockit90_150_04\bin\java -Dweblogic.Name=jdevext -Dbea.home=C:\bea -Djava.security.policy=c:\bea\weblogic91\server\lib\weblogic.policy -Dweblogic.management.server=http://144.111.155.145:7001 -Djava.library.path=C:\bea\WEBLOG~1\server\bin;.;C:\WINDOWS\system32;C:\WINDOWS;C:\bea\WEBLOG~1\server\native\win\32;C:\bea\WEBLOG~1\server\bin;C:\bea\JROCKI~1\jre\bin;C:\bea\JROCKI~1\bin;C:\bea\WEBLOG~1\server\native\win\32\oci920_8;C:\oracle\ora92\bin;C:\Program Files\Oracle\jre\1.3.1\bin;C:\Program Files\Oracle\jre\1.1.8\bin;C:\Program Files\ThinkPad\Utilities;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Support Tools\;C:\Program Files\Intel\Wireless\Bin\;C:\Program Files\ThinkPad\ConnectUtilities;C:\Program Files\QuickTime\QTSystem\ -Djava.class.path=C:\bea\weblogic91\server\lib\weblogic.jar;C:\bea\jrockit90_150_04\lib\tools.jar;c:\bea\weblogic91\server\lib\wamapps\commons-logging.jar;c:\bea\weblogic91\server\lib\wamapps\log4j.jar;c:\bea\weblogic91\server\lib\wamapps\xalan.jar;c:\bea\weblogic91\server\lib\wamapps\xercesImpl.jar;c:\bea\weblogic91\server\lib\wamapps\xml-apis.jar -Dweblogic.system.BootIdentityFile=C:\bea\user_projects\domains\jdev\servers\jdevext\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false java -server -Xgcprio:pausetime -Xpausetarget=400ms -Xms:256m -Xmx:384m -Xns:81m -Xgcpause -verbose weblogic.Server >
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Working directory is "C:\bea\user_projects\domains\jdev">
<May 24, 2006 11:16:55 AM> <Info> <NodeManager> <Server output log file is "C:\bea\user_projects\domains\jdev\servers\jdevext\logs\jdevext.out">
Usage: java [-options] class [args...]
(to execute a class)
or java [-options] -jar jarfile [args...]
(to execute a jar file)
where options include:
-jrockit     to select the "jrockit" VM
-client     to select the "client" VM
-server     to select the "server" VM [synonym for the "jrockit" VM]
The default VM is jrockit.
-cp <class search path of directories and zip/jar files>
-classpath <class search path of directories and zip/jar files>
A ; separated list of directories, JAR archives,
and ZIP archives to search for class files.
-D<name>=<value>
set a system property
-verbose[:class|gc|jni]
enable verbose output
-version print product version and exit
-version:<value>
require the specified version to run
-showversion print product version and continue
-jre-restrict-search | -jre-no-restrict-search
include/exclude user private JREs in the version search
-? -help print this help message
-X print help on non-standard options
-ea[:<packagename>...|:<classname>]
-enableassertions[:<packagename>...|:<classname>]
enable assertions
-da[:<packagename>...|:<classname>]
-disableassertions[:<packagename>...|:<classname>]
disable assertions
-esa | -enablesystemassertions
enable system assertions
-dsa | -disablesystemassertions
disable system assertions
-agentlib:<libname>[=<options>]
load native agent library <libname>, e.g. -agentlib:hprof
see also, -agentlib:jdwp=help and -agentlib:hprof=help
-agentpath:<pathname>[=<options>]
load native agent library by full pathname
-javaagent:<jarpath>[=<options>]
load Java programming language agent, see java.lang.instrument
<May 24, 2006 11:16:57 AM> <Info> <NodeManager> <Server failed during startup so will not be restarted>

It looks like your command line is broken. You have:
java <lots of -Dprop=value> java <JRockit flags> weblogic.Server
That second "java" shouldn't be there.
-- Henrik

Can i start managed server from another UNIX BOX ..

          Hello,
          I have created Admin Server on 1 UNIX Box & Managed SErver on 2nd UNIX Box. After
          starting ADMIN server on one UNIX Box, i wanted to start managed server using
          same script.I can manually login to 2nd unix box & start managed server. I am
          wondering if i can start using startup script from 1st UNIX Server.
          Thanks


You have to run the startup script from the machine where you want to start the server
          for now. Also the script has to be different for admin and managed server as the init
          arguments to java commands are different.
          We have plans in future to start managed servers from admin servers itself.
          Viresh Garg
          Principal Developer Relations Engineer
          BEA Systems
          Wlstech wrote:
          > Hello,
          >
          > I have created Admin Server on 1 UNIX Box & Managed SErver on 2nd UNIX Box. After
          > starting ADMIN server on one UNIX Box, i wanted to start managed server using
          > same script.I can manually login to 2nd unix box & start managed server. I am
          > wondering if i can start using startup script from 1st UNIX Server.
          >
          > Thanks

Can't start Managed Server

Hi,
I'm new to Weblogic. I've installed the admin and managed servers on two different physical servers. Both servers run Solaris OS. For both installations, I install "Administration Server" and "Managed Server, Clusters and Machines" in the "Select Optional Configuration" page. For Admin Server, the ip is 192.168.1.100 and Manager Server (attached under UnixMachine_1) is 192.168.1.101. I run startNodeManager.sh on both servers. On 192.168.101, I run startWebLogic.sh to start the weblogic server. Then, I go to the http://192.168.1.100:7001/console to start the Managed Server, I got an error, "For server ManagedServer1, the Node Manager associated with machine UnixMachine_1 is not reachable. What did I do wrong? Did I miss any step?
Thanks for any help!
Regards,
Johnny

Hi P-H,
Thanks for your response. I telnet the remote server from admin server with port 5556 and was able to connect. May be my setup is not correct. Here is my installation for both servers:
Admin Server:
Domain: MyDomain
IP: 192.168.1.100
Port: 7001
Add Managed Server (point to 192.168.1.101)
Add Unix Machine (point to 192.168.1.101)
Attached Managed Server to Machine
Manager Server:
Domain: MyDomain
IP: 192.168.1.101
Port: 7003
Add Admin Server (point to 192.168.1.100)
Add Managed Server (localhost or 192.168.1.100)
Add Unix Machine (localhost or 192.168.1.100)
Attached Managed Server to Machine
On Admin Server, I run StartNodeManager.sh
On Managed Server, I run StartWebLogic.sh, and StartNodeManager.sh
Last, I go to http://192.168.1.100:7001/console to start the managed server and then it failed.
Is this the typical setup for two servers to communicate with each other? Or may be I'm missing something? I'm confuse and have been searching the web for similar configuration or example but didn't find any.
Thanks,
Johnny
Edited by: tanww888 on Feb 22, 2011 11:26 PM
Edited by: tanww888 on Feb 22, 2011 11:31 PM
Edited by: tanww888 on Feb 22, 2011 11:32 PM

Starting managed server's via NodeManager from command line.

In WLS 70 weblogic.Admin utility has been enhanced to start/stop/kill
managed servers via NodeManager.
Here's the syntax
java weblogic.Admin -url {admin server url} -username {admin user}
-password {admin password} START {managed server instance name for e.g. S1}
Pls make sure that the admin server & Nodemanager have started prior to
executing the above command.
Similary you can issue "SHUTDOWN S1" command which will shutdown the
managed server.
See weblogic.Admin for more info. With this interface you don't need to
go to admin console to remotely start/stop managed servers.
Hope it helps
Kumar

Solved: attention must be paid to the casing of the attribute name. The first character of the attribute name must be uppercase.
So the property must be set as following:
set JAVA_OPTIONS=-Dweblogic.ssl.ServerPrivateKeyPassPhrase=<the_password> %JAVA_OPTIONS%
Edited by: javawarrior2003 on 24-nov-2011 18.19
Edited by: javawarrior2003 on 24-nov-2011 18.20

Can't start managed server in Oracle Service Bus 10gR3

Using Windows 2003 Enterprise.
Standard install of OSB 10gR3 - only changes from standard are that I also installed the samples, otherwise, it's default install the whole way.
My windows machine name is the same as a name entry in the HOSTS file, as follows
127.0.0.1 localhost
xxx.xxx.xxx.xxx osb-strat
yyy.yyy.yyy.yyy osb-other
I eventually want to setup a domain across 2 machines with 2 servers, one on each, hence the two entries.
For the life of me, I cannot start a managed server for OSB, I keep seeing
####<Feb 27, 2009 10:54:11 PM CST> <Critical> <WebLogicServer> <osb-strat> <Strategic> <Main Thread> <<WLS Kernel>> <> <> <1235737451969> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source)
     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source)
     at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source)
     at weblogic.security.SecurityService.start(SecurityService.java:141)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
I did manage it once, but then I had problems seeing the second machines Node Manager - I have figured that out, but during my screwing around, I lost how to get the primary machines service to boot - I have not even attempted to boot the server on the second, remote machine!
I have tried creating the domain using the Config wizard and creating the server/machine using the config wizard.
I have tried creating an empty domain using the Config wizard then using the Admin Console to create the machine and server.
I have tried editing the boot.properties in C:\bea\user_projects\domains\TheDomain\servers\Strategic\data\nodemanager
I have tried setting the listening address to the Hostname of the server, blank, to the IP address.
I have tried configuring the service to not do host name validation.
I do see, in the startup logs, that it notes that the hostname resolves to both the external IP and 127.0.0.1
I have tried re-installing (multiple times) hoping to have a fresh start.
I have even setup a Snapshot, post installation so I can re-start configuration from the very start.
I am at my wits end.
Surely, it can't be that hard to setup a vanilla server and boot it?
Any suggestions, maybe even a step by step creation of a single server (other than the admin server for the domain), that boots, starting immediately after installation?
Any assistance would be greatly appreciated.
...Lyall

We also use a boot.properties in ${domain.home}, which may only be for Admin server, but worth checking anyway. Also, I often receive the boot.properties message you're seeing when there's other problems upstream, and I've found the message to be quite misleading at times. For example, if I have a problem with an LDAPAuthenticator or any other security mechanism I'll often see the boot.properties message eventhough the problem has nothing to do with that file.

OSB 10gR3 - Starting Managed server on remote machine

I have 2 Windows 2003 Enterprise machines.
I have OSB 10gR3 installed on both with Node Manager running on default port, on both.
I create the servicebustutorial domain and start the admin server on the first machine.
On the second machine, I use the WLST to
<ul><li>connect('weblogic','password','t3://xxx.xxx.xxx.xxx:7001') # connect to admin server on first machine
</li>
<li>nmEnroll('c:/bea/wlserver_10.3/common/nodemanager') # make node manager visible
</li>
<li>nmEnroll('c:/bea/user_projects/domains/servicebustutorial') # enroll in the servicebustutorial</li>
</ul>
Now, I don't know if this is the correct thing to do.
Back on the first machine, I create a new machine to represent the second Windows box.
I can see the node manager on the second machine using the machine monitoring page.
I then create a new server that is assigned to the new machine.
I can attempt to start the new server on the second machine.
The Server directory appears in the servers directory on the second windows box.
Log files appear on the second box but the config.xml is not there, and thus, the server fails to start.
I would have thought that the server config would have propogated from the admin server, is this a wrong assumption?
What am I doing wrong?
Thanks, in advance.
...Lyall

Thanks for replying.
I login as a local administrator on the machine that WebLogic runs. All operations are performed using that login (starting admin server, starting node manager).
I changed permissions on C:\BEA, all the way down, localadmin group has full control, everywhere.
I tried changing nodemanager C:\bea\wlserver_10.3\common\nodemanager\nodemanager.properties LogLevel to DEBUG but then NodeManager refuses to start, so I returned it back to INFO.
I set debug on the Managed Server I am trying to setup, as you suggested.
I even updated the NodeManager and Server boot.properties files to be cleartext and Deleted the LDAP directory within the Managed Server (as I assume it's re-created if it does not exist)
Wow, heaps comes out, but the following may be relevant.
In particular, this single line, causes concern.
bq. ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE \\ ExecuteThread: '0' for queue: 'weblogic.kernel.Default \\ (self-tuning)'> <<WLS Kernel>> <> <> \\ <1236334820297> <BEA-000000> <[Security:090295 |http://forums.oracle.com//]caught unexpected exception>
It's an unexpected exception but it's not an Error and only reported as a Debug! I could be climbing up the wrong tree, but the following log output is what immediately precedes the login failure.
bq. ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.wrap ClassLoader=java.net.URLClassLoader@1f0e58> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.wrap ControlFlag=LoginModuleControlFlag: required> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.JAASLoginServiceImpl.login created LoginContext> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820219> <BEA-000000> <com.bea.common.security.internal.service.JAASLoginServiceImpl.login ThreadContext ClassLoader Current=sun.misc.Launcher$AppClassLoader@124dfc> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize LoginModuleClassName=weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize ClassLoader=java.net.URLClassLoader@1f0e58> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize created delegate login module> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <LDAP ATN LoginModule initialized> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.initialize delegated> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820234> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.login> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <LDAP Atn Login> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will be delegated> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[0] will use NameCallback to retrieve name> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle callbcacks[1] will be delegated> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle will delegate all callbacks> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle delegated callbacks> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <com.bea.common.security.internal.service.CallbackHandlerWrapper.handle got username from callbacks[0], UserName=weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820250> <BEA-000000> <LDAP Atn Login username: weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820281> <BEA-000000> <new LDAP connection to host 134.251.218.157 port 7001 use local connection is true> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820281> <BEA-000000> <created new LDAP connection LDAPConnection { ldapVersion:2 bindDN:""}> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <connection succeeded> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <getConnection return conn:LDAPConnection { ldapVersion:2 bindDN:""}> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <authenticate user:weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <getDNForUser search("ou=people,ou=myrealm,dc=Tester", "(&(uid=weblogic)(objectclass=person))", base DN & below)> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <[Security:090295|http://forums.oracle.com/forums/]caught unexpected exception> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <LDAP Atn Abort> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <com.bea.common.security.internal.service.LoginModuleWrapper.commit delegated, returning false> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityAtn> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <weblogic.security.service.internal.WLSJAASLoginServiceImpl$ServiceImpl.authenticate authenticate failed for user weblogic> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.isLocked(weblogic)> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820297> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic)> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) UserLockout Login failure for user in realm myrealm> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.getInvaliLoginUsersHighCount()> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) User weblogic has 1 failures in realm myrealm> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImplUserLockout InvalidLogin Record GC not needed> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImpl.logFailure(weblogic) UserLockout About to multicast login failure for user SecurityMessage realm:myrealm record:SecurityMulticastRecord: origin: Strategic realmName: myrealm seqnum: 1 timestamp: Mar 6, 2009 8:50:20 PM username: weblogic nextSeqNo:1> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Debug> <SecurityUserLockout> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-000000> <weblogic.security.service.internal.UserLockoutServiceImpl$ServiceImplUserLockout Can't create multicastSession because ClusterServices are unavailable> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Critical> <Security> <osb-strat> <Strategic> <ACTIVE ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1236334820312> <BEA-090402> <Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted.> \\ ####<Mar 6, 2009 8:50:20 PM CST> <Critical> <WebLogicServer> <osb-strat> <Strategic> <Main Thread> <<WLS Kernel>> <> <> <1236334820312> <BEA-000386> <Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. \\ weblogic.security.SecurityInitializationException: Authentication denied: Boot identity not valid; The user name and/or password from the boot identity file (boot.properties) is not valid. The boot identity may have been changed since the boot identity file was created. Please edit and update the boot identity file with the proper values of username and password. The first time the updated boot identity file is used to start the server, these new values are encrypted. \\ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(Unknown Source) \\ at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(Unknown Source) \\ at weblogic.security.service.SecurityServiceManager.initialize(Unknown Source) \\ at weblogic.security.SecurityService.start(SecurityService.java:141) \\ at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64) \\ at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) \\ at weblogic.work.ExecuteThread.run(ExecuteThread.java:173) \\ >

Start managed server in multihomed machine with cluster?

Hi,
          I have problems with starting a remote managed server.
          I have a cluster configured with 2 managed servers in the same machine. I added a new managed server but assigned to other machine.
          MachineA:
          -AdminServer:7001,
          -ManagedServerA1: 7004, ManagedServerA2:7006
          -Cluster
          MachineB:
          -ManagedServerB: 7003
          I tried to start ManagedServerB in Machine A but I have got this error:
          startManagedWeblogic.cmd ManagedServerB http://MachineA:7001
          <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address â€œIP of MachineB that I am usingâ€ might be incorrect or another process is using port 7003: java.net.BindException: Cannot assign requested address: JVM_Bind.>
          <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
          But the port is not used by any other process or server.
          Other question: is it necessary to start all managed servers, local and remote in the server where my application is deployed?
          Is it the correct way for using a cluster in multihomed machine?
          Is there any documentation for configuring a cluster specifically for this case?
          By the way, I am using Weblogic 91.
          Regards,
          Hicyo

Hi,
          I am also having the same problem below.Can someone suggest a solution to my problem?
          I have a cluster configured with 2 managed servers in the same machine. I added a new managed server but assigned to other machine.
          MachineA:
          -AdminServer:7001,
          -ManagedServerA1: 7004, ManagedServerA2:7006
          -Cluster
          MachineB:
          -ManagedServerB: 7003
          I tried to start ManagedServerB in Machine A but I have got this error:
          startManagedWeblogic.cmd ManagedServerB http://MachineA:7001
          <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address â€œIP of MachineB that I am usingâ€ might be incorrect or another process is using port 7003: java.net.BindException: Cannot assign requested address: JVM_Bind.>
          <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
          But the port is not used by any other process or server.

Can't start managed server - Authentication for user denied

Greetings,
I have a WebLogic 10.3.6 based domain. The admin server works correctly. Using the admin console, I created a managed server. It is not associated to any machine and I don't use node manager. The managed server listens on localhost:7101 while the admin listens on localhost:7001. Starting the managed server asks for an user/password authentication. Using the same as the one used for the admin console says:
<7 dÚc. 2012 13 h 55 CET> <Critical> <Security> <BEA-090403> <Authentication for
user nicolas denied>
<7 dÚc. 2012 13 h 55 CET> <Critical> <WebLogicServer> <BEA-000386> <Server subsy
stem failed. Reason: weblogic.security.SecurityInitializationException: Authenti
cation for user nicolas denied
weblogic.security.SecurityInitializationException: Authentication for user nicol
as denied
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.do
BootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:966)
at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.in
itialize(CommonSecurityServiceManagerDelegateImpl.java:1054)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
erviceManager.java:873)
at weblogic.security.SecurityService.start(SecurityService.java:141)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
Truncated. see log file for complete stacktrace
Caused By: javax.security.auth.login.FailedLoginException: [Security:090303]Auth
entication Failed: User nicolas weblogic.security.providers.authentication.LDAPA
tnDelegateException: [Security:090295]caught unexpected exception
at weblogic.security.providers.authentication.LDAPAtnLoginModuleImpl.log
in(LDAPAtnLoginModuleImpl.java:251)
at com.bea.common.security.internal.service.LoginModuleWrapper$1.run(Log
inModuleWrapper.java:110)
at java.security.AccessController.doPrivileged(Native Method)
at com.bea.common.security.internal.service.LoginModuleWrapper.login(Log
inModuleWrapper.java:106)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Truncated. see log file for complete stacktrace
>
<7 dÚc. 2012 13 h 55 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to FAILED>
<7 dÚc. 2012 13 h 55 CET> <Error> <WebLogicServer> <BEA-000383> <A critical serv
ice failed. The server will shut itself down>
<7 dÚc. 2012 13 h 55 CET> <Notice> <WebLogicServer> <BEA-000365> <Server state c
hanged to FORCE_SHUTTING_DOWN>
I googled a while and found a post saying that the realm is probably altered or in an incorrect status. I reset the the admin's credentials using weblogic.security.utils.AdminAccount but this disn't change anything. Of course, upon the managed server creation, I initialized the fierlds user and password in the server starting tab of the admin console.
Many thanks for any help.
Nicolas

Hi,
Have you configured LDAP Authenticator on the server?
If yes, afther the change did you restart both the servers - admin and managed?

Can not start managed server

Hi All,
I am trying to start one of the managed server which are in cluster but i am getting below error:
Please suggest the issue and resolution if anyone has come across the same situation.
<Oct 14, 2011 7:56:16 AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.BasicServerRef@274, implementation: 'weblogic.jms.dispatcher.DispatcherImpl@4f6fa0b6', oid: '628', implementationClassName: 'weblogic.jms.dispatcher.DispatcherImpl'
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers].
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:833)
at weblogic.security.service.SecurityServiceManager.getSealedSubjectFromWire(SecurityServiceManager.java:522)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:349)
at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:953)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:351)
Truncated. see log file for complete stacktrace
>
<Oct 14, 2011 7:56:16 AM EDT> <Warning> <RMI> <BEA-080003> <RuntimeException thrown by rmi server: weblogic.rmi.internal.BasicServerRef@274, implementation: 'weblogic.jms.dispatcher.DispatcherImpl@4f6fa0b6', oid: '628', implementationClassName: 'weblogic.jms.dispatcher.DispatcherImpl'
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers].
java.lang.SecurityException: [Security:090398]Invalid Subject: principals=[weblogic, Administrators, IntegrationAdministrators, AdminChannelUsers]
at weblogic.security.service.SecurityServiceManager.seal(SecurityServiceManager.java:833)
at weblogic.security.service.SecurityServiceManager.getSealedSubjectFromWire(SecurityServiceManager.java:522)
at weblogic.rjvm.MsgAbbrevInputStream.getSubject(MsgAbbrevInputStream.java:349)
at weblogic.rmi.internal.BasicServerRef.acceptRequest(BasicServerRef.java:953)
at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:351)
Truncated. see log file for complete stacktrace
>
<Oct 14, 2011 8:12:03 AM EDT> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
<Oct 14, 2011 8:12:06 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to SUSPENDING>
[JCABindingManager] : This operation is not supported for JCA based MDB
<Oct 14, 2011 8:12:07 AM EDT> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>
<Oct 14, 2011 8:12:08 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to ADMIN>
<Oct 14, 2011 8:12:08 AM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to SHUTTING_DOWN>
<Oct 14, 2011 8:12:08 AM EDT> <Notice> <Server> <BEA-002607> <Channel "Default" listening on 10.172.108.9:26362 was shutdown.>

From the managed server folder like servers/yourManagedServer rename the fodler named "data". Then restart the server. Basically this "data" folder will have ldap information and all groups, policies etc. It will create this folder again and get a copy of full data folder from admin server. Give this a shot.
Thanks
Ravi Jegga

Can't start Managed Server ( Clusters )

I have an error while trying start managed serverin cluster:
<Mar 21, 2013 11:33:02 AM ICT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
<Mar 21, 2013 11:33:02 AM ICT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
<Mar 21, 2013 11:33:03 AM ICT> <Notice> <Log Management> <BEA-170019> <The server log file /root/Oracle/Middleware/user_projects/domains/clus_domain/servers/managed_server_local/logs/managed_server_local.log is opened. All server side log events will be written to this file.>
<Mar 21, 2013 11:34:46 AM ICT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
<Mar 21, 2013 11:34:47 AM ICT> <Critical> <WebLogicServer> <BEA-000386> <Server subsystem failed. Reason: java.lang.NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory
java.lang.NoClassDefFoundError: weblogic/sip/tools/SipToolsFactory
at weblogic.sip.plugin.SipPlugin.startService(SipPlugin.java:25)
at weblogic.server.ServiceActivator.start(ServiceActivator.java:96)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
<Mar 21, 2013 11:34:47 AM ICT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
Thanks any advance.
Edited by: user9069915 on Mar 20, 2013 8:56 PM

Hi,
I think this issue could be in relationship with this article:*" Weblogic Server Startup issues after extending a domain with installation of Basic SIP template [ID 1500712.1]"* published on Oracle Support.
Best regards,
Raúl
Edited by: 829518 on 01-abr-2013 13:21

I can not start management server

Dear Oracle collegues,
why I can not start service OracleHomeNameManagementServer?
message is something about conntacting sys admin (I have german version of Win 2000, and english version of Oracle 8i Enterprise Edition), probably some lack of rights (I am ORA DBA on local system).
Please help!

I think, sys admin means a superuser for the Enterprise manager.
Try sysadm/oem_temp

Can we get directory structue of other machine from JFileChooser?

I want to display the directory structure of the other
machine, in the network where my RMI client is running.
Is this possible using JFileChooser.

No. Your RMI server would have to have something that returned that information to the client, and even if it did, you could not use a JFileChooser to work with it.

Manage Server Health Goes Blank in Admin Console

Hello Team,
I am continously facing issue with OSB manage server. It is running fine but health is blank in Admin Console.
Due to which it is not responding to any user request.
Kindly guide me to troubleshoot this issue.

Hi,
It is due to the problem with the JMX communication between and Admin and your OSB managed servers. Did you observed any messages related to it?
Is it a SSL communication, then try to make sure that certificates are valid.
As a general practice, make sure you have listen address configured for your servers. If left it blank(default), then it would be listening on the all the available host and communication would get messy in these situations.
If still facing problem, i would suggest you enable the below debugs and raise a support case
1. Apply the below three debug logs from console(for admin as well as Managed Server)
   weblogic->management->JMXCore
   weblogic->management->JMXDomain
   weblogic->management->JMXRuntime
2. Restart all the servers
If the issue, occurs, provide the debug along with the thread dump(take 5 thread dump at an interval of 5seconds) for the Managed Server(which is unknown state) and for the admin server.
Regards
Rosario

Can't start manager server on other machine from admin console

Similar Messages

Maybe you are looking for