Can't start vanilla 8.1.4 platform managed server via NodeManager

I cannot get a managed server to start via the NodeManager if I create a WL Platform domain. I CAN get it to work just fine if I create a regular WLS domain. I was wondering if anyone else has seen this behavior.
Steps to Reproduce
===================
1) Use the configuration wizard to create a WebLogic Platform domain. Name the domain "Test". Use all defaults.
2) Once the domain is created, go into the domain directory and run the create_db.cmd script to build out the necessary tables to support the platform domain
3) Start the node manager. On my machine I use the following command:
C:\bea\weblogic81\server\bin\startnodemanager 127.0.0.1 5555
4) Start the admin server via the startWebLogic.cmd file
5) Open the console for the admin server. Create a Machine "MyMachine" (name is really unimportant). Use the default NodeManager port of 5555
6) Create a managed server. Call it "test1". Set the port to 8000 and be sure to assign it to the machine you just created.
7)Set the remote start properties. On my machine I just set the classpath to "c:\bea\weblogic81\server\lib\weblogic.jar;C:\bea\weblogic81\workshop\lib\wsrp-common.jar;C:\bea\weblogic81\server\lib\xbean.jar" and I also set the Java Home to point to the default JRocket JVM that ships with 8.1.4
8) Be sure to save your changes by hitting the "Apply" button. Then using the "Control" tab for the "test1" managed server, click the "Start this Server" link.
9) Wait about 30 - 40 seconds, then click on the server log for that server. On my machine I get the following exception in the log:
<Mar 22, 2005 6:04:46 PM PST> <Info> <[email protected]:5555> <Starting Server test::test1 ...>
<Mar 22, 2005 6:04:47 PM PST> <Info> <[email protected]:5555> <Server test::test1 started, process id = 5,504>
<Mar 22, 2005 6:04:48 PM PST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
<Mar 22, 2005 6:04:49 PM PST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://169.254.40.11:7001 to check if there exists a running admin server at this URL.>
<Mar 22, 2005 6:04:49 PM PST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Mar 22, 2005 6:04:49 PM PST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Mar 22, 2005 6:04:49 PM PST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://169.254.40.11:7001 to retrieve the initial configuration.>
<Mar 22, 2005 6:04:50 PM PST> <Notice> <Log Management> <BEA-170019> <The server log file C:\bea\weblogic81\common\nodemanager\test1\test1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:205)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
<Mar 22, 2005 6:04:53 PM PST> <Critical> <WebLogicServer> <BEA-000364> <Server failed during initialization. Exception:weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:205)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
>
<Mar 22, 2005 6:04:53 PM PST> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Authentication Provider java.lang.IllegalStateException: This query is too complex to be processed.>
I am baffled by this error. Can anyone help shed some light on this issue? I'm sure there is some bit I left un-flipped somewhere, but I don't know where to look. Many thanks in advance!
- Jeff

Please help me over this error: (Weblogic clustered setup, two managed servers and one admin server, siteminder security providers configured)
bash-2.05$ ./startManagedWebLogic.sh managedServer5 http://sunert1.ad.infosys.com:7007
./startManagedWebLogic.sh: -Dsmasa.home=/export/home/ngtyasqa/bea/asa: not found
CLASSPATH=/export/home/ngtyasqa/bea/asa/conf:/export/home/ngtyasqa/bea/asa/lib/smjavaagentapi.jar:/e
xport/home/ngtyasqa/bea/asa/lib/log4j.jar:/export/home/ngtyasqa/bea/asa/lib/sm_jsafe.jar:/export/hom
e/ngtyasqa/bea/asa/lib/smclientclasses.jar:/export/home/ngtyasqa/bea/asa/lib/smjavasdk2.jar:/export/
home/ngtyasqa/bea/asa/lib/imsapi.jar/export/home/ngtyasqa/bea_kunal/jdk142_04/lib/tools.jar:/export/
home/ngtyasqa/bea/weblogic81/server/lib/weblogic_sp.jar:/export/home/ngtyasqa/bea/weblogic81/server/
lib/weblogic.jar::/export/home/ngtyasqa/bea/weblogic81/common/eval/pointbase/lib/pbserver44.jar:/exp
ort/home/ngtyasqa/bea/weblogic81/common/eval/pointbase/lib/pbclient44.jar:/export/home/ngtyasqa/bea_
kunal/jdk142_04/jre/lib/rt.jar:/export/home/ngtyasqa/bea/weblogic81/server/lib/webservices.jar:
PATH=/export/home/ngtyasqa/bea/weblogic81/server/bin:/export/home/ngtyasqa/bea_kunal/jdk142_04/jre/b
in:/export/home/ngtyasqa/bea_kunal/jdk142_04/bin:/export/home/ngtyasqa/bea_kunal/jdk142_04/bin:/usr/
bin
* To start WebLogic Server, use a username and *
* password assigned to an admin-level user. For *
* server administration, use the WebLogic Server *
* console at http://<hostname>:<port>/console *
<Mar 21, 2006 5:25:48 PM GMT+05:30> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server w
ith Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
<Mar 21, 2006 5:25:49 PM GMT+05:30> <Info> <Management> <BEA-141140> <The managed server is going to
contact the admin server at http://sunert1.ad.infosys.com:7007 to check if there exists a running a
dmin server at this URL.>
<Mar 21, 2006 5:25:49 PM GMT+05:30> <Info> <Configuration Management> <BEA-150017> <This server is b
eing started as a dependent managed server.>
<Mar 21, 2006 5:25:49 PM GMT+05:30> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 S
P5 Mon Sep 19 23:06:54 PDT 2005 641358
WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 >
<Mar 21, 2006 5:25:50 PM GMT+05:30> <Info> <Configuration Management> <BEA-150015> <Connecting to th
e administration server http://sunert1.ad.infosys.com:7007 to retrieve the initial configuration.>
<Mar 21, 2006 5:25:54 PM GMT+05:30> <Notice> <Log Management> <BEA-170019> <The server log file /exp
ort/home/ngtyasqa/bea/user_projects/domains/mydomain/managedServer5/managedServer5.log is opened. Al
l server side log events will be written to this file.>
<Mar 21, 2006 5:26:03 PM GMT+05:30> <Critical> <WebLogicServer> <BEA-000364> <Server failed during i
nitialization. Exception:weblogic.security.service.SecurityServiceRuntimeException: [Security:090371
]Problem instantiating Authentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexp
ected Exception - with nested exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
        java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Au
thentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with ne
sted exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
        java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:2
25)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:283)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManager
DelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServ
iceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceMan
agerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecuritySer
viceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceMa
nagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:7
34)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:821)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
at weblogic.Server.main(Server.java:32)
>
<Mar 21, 2006 5:26:03 PM GMT+05:30> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize
the server: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem inst
antiating Authentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Excepti
on - with nested exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
        java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]>
The WebLogic Server did not start up properly.
weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instantiating Au
thentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception - with ne
sted exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
        java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:2
25)
at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:283)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManager
DelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServ
iceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceMan
agerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecuritySer
viceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceMa
nagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:7
34)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:821)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
at weblogic.Server.main(Server.java:32)
Reason: weblogic.security.service.SecurityServiceRuntimeException: [Security:090371]Problem instanti
ating Authentication Provider weblogic.rmi.extensions.RemoteRuntimeException: Unexpected Exception -
with nested exception:
[java.rmi.MarshalException: failed to marshal invoke(Ljavax.management.ObjectName;Ljava.lang.String;
[Ljava.lang.Object;[Ljava.lang.String;); nested exception is:
        java.io.NotSerializableException: com.netegrity.siteminder.weblogic.sspi.auth.a9]
Thanks and Regards,
Shefali

Similar Messages

  • HANDSHAKE_FAILURE problem when starting managed server via NOdeManager

    hi all, i am trying to start a managed server using nodeManager, but i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command start for
    server managedServer via the Node Manager - reason: [CommandInvoker: Failed to
    send command: 'online to server 'managedServer' to NodeManager at host: 'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler was unable
    to negotiate an acceptable set of security parameters.. Please ensure that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76) at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try to start
    the managed server via adminserver console, i got the exception mentioned in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver, and
    nodemanager is supposed to run at localhost:5555 (and indeed it does, because
    ihave started it successfully).
    thanx in advance and regards marco

    Marco.
    Sorry, this is not a solution to your problem but i am trying to solve the same
    problem for a week now.
    I have wl7.0 sp2, 1 admin server, 2 managed servers on the same box. I get the
    same error. I know that the default certificate installed provides a hostname
    verification of weblogic.com. I turned the hostname verification off, i put in
    the Dweblogic.nodemanager.sslHostNameVerificationEnabled=false, i get the same
    error when starting the managed server. I went ahead and created my own certificate
    for machine called mallik, created my own passphrase, created a new keystore,
    made the admin server view the keystore, used the same certificate for both the
    admin server and the node manager. It still fails with the same error. I went
    ahead and added the machine 'mallik' to nodeManager.hosts file. It fails. I am
    totally confused now what needs to be done.
    My nodeManger.hosts looks like this:
    mallik 10.100.10.130
    managedServer1 10.100.10.130
    managedServer2 10.100.10.13
    Below is the startNodeManager.cmd.
    @echo off
    @rem *************************************************************************
    @rem This script can be used to start the WebLogic NodeManager
    @rem
    @rem This script sets the following variables before starting the NodeManager:
    @rem
    @rem WL_HOME - The root directory of your WebLogic installation.
    @rem NODEMGR_HOME - The home directory for this NodeManager instance.
    @rem JAVA_HOME - Location of the version of Java used to start WebLogic
    @rem Server. This variable must point to the root directory of
    @rem a JDK installation and will be set for you by the
    @rem          installer. See the WebLogic platform support page
    @rem (http://e-docs.bea.com/wls/platforms/index.html) for an up-to-date
    list of
    @rem supported JVMs on Windows NT.
    @rem PATH - Adds the JDK and WebLogic directories to the system path.
    @rem CLASSPATH - Adds the JDK and WebLogic jars to the classpath.
    @rem JAVA_OPTIONS - Java command-line options for running the server. (These
    @rem will be tagged on to the end of the JAVA_VM and MEM_ARGS)
    @rem JAVA_VM - The java arg specifying the VM to run. (i.e. -server,
    @rem -client, etc.)
    @rem MEM_ARGS - The variable to override the standard memory arguments
    @rem passed to java
    @rem
    @rem *************************************************************************
    SETLOCAL
    set WL_HOME=C:\bea7.0\weblogic700
    set NODEMGR_HOME=%WL_HOME%\common\nodemanager
    set JAVA_HOME=C:\bea7.0\jdk131_06
    Call %WL_HOME%\common\bin\commEnv.cmd
    @rem If NODEMGR_HOME does not exist, create it
    :checkNodeManagerHome
    if exist %NODEMGR_HOME% goto checkJava
    echo.
    echo NODEMGR_HOME %NODEMGR_HOME% does not exist, creating it..
    mkdir %NODEMGR_HOME%
    @rem Check that java is where we expect it to be
    :checkJava
    if exist %JAVA_HOME%\bin\java.exe goto runNodeManager
    echo The JDK wasn't found in directory %JAVA_HOME%.
    echo Please edit this script so that the JAVA_HOME
    echo variable points to the location of your JDK.
    goto finish
    :runNodeManager
    if not "%JAVA_VM%" == "" goto noResetJavaVM
    rem set JAVA_VM=-hotspot
    set JAVA_VM=%COMM_VM%
    :noResetJavaVM
    if not "%MEM_ARGS%" == "" goto noResetMemArgs
    set MEM_ARGS=-Xms32m -Xmx200m
    :noResetMemArgs
    @echo on
    set CLASSPATH=.;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar;%CLASSPATH%
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    cd %NODEMGR_HOME%
    #"%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.reverseDnsEnabled=true"
    "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%" weblogic.nodemanager.NodeManager
    "%JAVA_HOME%\bin\java.exe" %JAVA_VM% %MEM_ARGS% %JAVA_OPTIONS% -classpath "%CLASSPATH%"
    "-Dbea.home=C:\bea7.0" "-Dweblogic.security.SSL.trustedCAKeyStore=%WL_HOME%\server\lib\cacerts"
    "-Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy" "-Dweblogic.nodemanager.certificateFile=C:\bea7.0\user_projects\myDomain\mallikcert.pem"
    "-Dweblogic.nodemanager.sslHostNameVerificationEnabled=false" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.ListenAddress=mallik" "-Dweblogic.nodemanager.nativeVersionEnabled=true"
    "-Dweblogic.nodemanager.reverseDnsEnabled=true" "-Dweblogic.nodemanager.javaHome=%JAVA_HOME%"
    "-Dweblogic.nodemanager.trustedHosts=%WL_HOME%\common\nodemanager\config\nodemanager.hosts"
    "-Dweblogic.management.pkpassword=weblogic" weblogic.nodemanager.NodeManager
    goto finish
    :finish
    ENDLOCAL
    I would appreciate if anybody can help me.
    Mallik.
    "Marco" <[email protected]> wrote:
    >
    hi all, i am trying to start a managed server using nodeManager, but
    i keep on
    getting following exception:
    weblogic.nodemanager.NodeManagerException: [Could not execute command
    start for
    server managedServer via the Node Manager - reason: [CommandInvoker:
    Failed to
    send command: 'online to server 'managedServer' to NodeManager at host:
    'localhost:5555'
    with exception FATAL Alert:HANDSHAKE_FAILURE - The handshake handler
    was unable
    to negotiate an acceptable set of security parameters.. Please ensure
    that the
    NodeManager is active on the target machine].] at weblogic.nodemanager.NodeManagerRuntime.executeCommand(NodeManagerRuntime.java:472)
    at weblogic.nodemanager.NodeManagerRuntime.start(NodeManagerRuntime.java:76)
    at
    java.lang.reflect.Method.invoke(Native Method) at
    here is my script for starting nodemanager
    set JAVA_HOME=c:\bea\jdk131
    set WL_HOME=c:\bea\weblogic700
    set PATH=%WL_HOME%\server\bin;%JAVA_HOME%\bin;%PATH%
    set CLASSPATH=.;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar
    java -hotspot -ms16m -mx16m -classpath %CLASSPATH% -Dbea.home=C:\bea\weblogic700
    -Djava.security.policy=C:\bea\weblogic700\server\lib\weblogic.policy
    -Dweblogic.nodemanager.weblogicHome=C:\bea\weblogic700
    -Dweblogic.nodemanager.listenAddress=172.21.73.94 -Dweblogic.nodemanager.listenPort=5555
    -Dweblogic.nodemanager.trustedHosts=C:\bea\weblogic700\common\nodemanager\config\nodemanager.hosts
    -Dweblogic.nodemanager.certificateFile=C:\bea\weblogic700\common\nodemanager\config\demo.crt
    weblogic.nodemanager.NodeManager
    i have created an admin server, called adminserver
    then i have created in the same domain a server called managedserver
    both servers run on the same machine,at different port number.
    i have created a machine, and associated managedserver to it.
    in the machine/configuration/nodemanager i have set listenaddress localhost
    and
    listenport 5555.
    my nodemanager starts automatically at htat port. however, when i try
    to start
    the managed server via adminserver console, i got the exception mentioned
    in
    the subject.
    can anyone help?
    regards
    marco
    can anyone point me to the right direction for solving this problem?
    in the adminserver console i have defined a machine for teh managedserver,
    and
    nodemanager is supposed to run at localhost:5555 (and indeed it does,
    because
    ihave started it successfully).
    thanx in advance and regards marco

  • Problems starting managed server via nodemanager

    Hello,
    I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
    One hosts the admin server and the seconds hosts a managed server.
    I installed the nodemanager on both maschines. They seems to run
    normally.
    I configured the "Remot Start" for the managed server as mentioned in
    the manual. I didn't specified any values in that panel because the
    nodemanager uses the same environment as the WLS so these values should
    fit the managed WLS too.
    But as I try to start the managed server I got the following error
    message:
    Starting WebLogic Server ....
    Child exited
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    So I specified some basic values on the "Remote Start" panel:
    BEA_HOME: /www/apps/bea/
    ROOT_DIR: /www/apps/bea/wlserver6.1
    CLASSPATH:
    /www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
    No I got this message:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Child exited
    What did I wrong?
    Has anybody experiences on this problem?
    Thanks !
    Falko Zurell - Webmaster
    Pixelpark AG
    Germany

    nodemanager must be using the old jvm (1.2.2 or whatever comes by
    default with 2.8). set up the environment or modify
    startNodeManager.sh so that it uses java 1.3.1 that ships with WLS6.1
    o.
    Falko Zurell <[email protected]> wrote in message news:<[email protected]>...
    Hello,
    I have a WebLogic 6.1 SP2 installation on two Solaris 8 maschines.
    One hosts the admin server and the seconds hosts a managed server.
    I installed the nodemanager on both maschines. They seems to run
    normally.
    I configured the "Remot Start" for the managed server as mentioned in
    the manual. I didn't specified any values in that panel because the
    nodemanager uses the same environment as the WLS so these values should
    fit the managed WLS too.
    But as I try to start the managed server I got the following error
    message:
    Starting WebLogic Server ....
    Child exited
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    So I specified some basic values on the "Remote Start" panel:
    BEA_HOME: /www/apps/bea/
    ROOT_DIR: /www/apps/bea/wlserver6.1
    CLASSPATH:
    /www/apps/bea/wlserver6.1/lib/weblogic_sp.jar:/www/apps/bea/wlserver6.1/lib/weblogic.jar
    No I got this message:
    Starting WebLogic Server ....
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.NoClassDefFoundError: java/lang/reflect/InvocationHandler
    at weblogic.management.Admin.initialize(Admin.java:279)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:362)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Child exited
    What did I wrong?
    Has anybody experiences on this problem?
    Thanks !

  • Can Photoshop Starter Editor 3.0 run as a server application

    Can Photoshop Starter Editor 3.0 run as a server application and be accessed by more then one computer simultaniously? If this is in breach of the license agreement, where can I find more information on this ?
    If this program cant perform as a server app. is Adobe Photoshop Album 2.0 able to operate as a server app. ?

    Okay Tom...
    Now these may be things that people have already discussed in the forum, so
    you'll have to pardon me if you already know this.
    You CAN use the database on the server and put the application on the client
    computer. PSE prevents multiple accesses to the same database so that will
    avoid any conflict issues, however you would still need to contact Adobe
    about licencing. Further with PSE 4.0 out now... you are looking at another
    application.
    I'll see what Picassa can do, but I would NOT hold my breath... and while it
    is a handy little app, for me it is FAR too limited for anything more than a
    quick search and some very basic tools.
    I'll see what I can do in the next 20 minutes or so and get back to you.
    Cheers

  • Facing error in starting managed server from nodemanager

    Hi All,
    I have installed WebLogic server 10.3.4 and installed OSB 11.1.1.4.0. I created domain with one admin server and one managed server for osb. When I started managed server with the startManagedWebLogic command it got started successfully but when I am trying tp start the managed server from nodemanager I am getting the following error
    starting weblogic with Java version:
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    Starting WLS with line:
    D:\JDK\JROCKI~1.0\bin\java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms256m -Xmx512m -Dweblogic.Name=osb_server1 -Djava.security.policy=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=D:\Oracle_OSB\Middleware\user_projects\domains\osb_domain\servers\osb_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3 -Dwls.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=D:\ORACLE~1\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=D:\ORACLE~1\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1 -Djrockit.optfile=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\servers\osb_server1 -Doracle.domain.config.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=D:\ORACLE~1\MIDDLE~1\USER_P~1\domains\OSB_DO~1\servers\osb_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,D:\ORACLE~1\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Dem.oracle.home=D:\Oracle_OSB\Middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://soaspt-app01.scotwat.net:7010 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=D:\ORACLE~1\MIDDLE~1\patch_wls1034\profiles\default\sysext_manifest_classpath;D:\ORACLE~1\MIDDLE~1\patch_ocp360\profiles\default\sysext_manifest_classpath weblogic.Server
    [WARN ] Use of -Djrockit.optfile is deprecated and discouraged.
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    [ERROR] aborted
    JRockit aborted: Unknown error (50)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <Waiting for the process to die: 5916>
    <11-Mar-2013 13:22:17> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <11-Mar-2013 13:22:17> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    My nodemanager is started and reachable. The error above says "Address already in use" but I am able to start my managed server through startManagedWebLogic.cmd command.
    Can anyone please tell me what could be the issue. It is really urgent. Please help!!

    Hi Roshni,
    It is likely that a configuration is missing or not set properly in the Node Manager properties file (nodemanager.properties) since the managed server can be started up using startManagedWebLogic.cmd but not with Node Manager. I would complete the following steps to fix the problem:
    1. Go to %WLS_HOME%\common\nodemanager and open up nodemanager.properties (Make a backup of the file first). NOTE: WLS_HOME is your WebLogic Server home.
    2. Look for the parameters "StartScriptEnabled" and "StopScriptEnabled". They should be set to true. If not, please set them to true.
    3. Save and close the file.
    4. Restart the Node Manager
    If you are still unable to start the manager server using Node Manager, you may need to update the DEBUG_PORT parameter in setDomainEnv.cmd located in %MIDDLEWARE_HOME%\user_projects\domains\%DOMAIN_HOME%\bin (always make a backup before changing a configuration file). You may refer to Oracle Support note 1272642.1 for more information about the nodemanager.properties file and how to configure the DEBUG_PORT parameter in setDomainEnv.cmd if needed.
    Thanks,
    Scott (PITSS)
    http://pitss.com/us

  • The system can be contact, but there is no Central Management Server

    Please help me, I have an error in SAP BusinessObjects XI 3.1 in Linux. I changed by web in CMC the ports of CentralManagementConsole, InputFileRepository and OutputFileRepository in order to assign an specific port, after that I restarted the servers and now I have this error.
    Couldn't logon to CMS STU00152
    The system can be contact, but there is no Central Management Server running at port 6400
    I donu2019t know where I should change that by commands in Linux because I cannot enter to CMC and change like before. Please help me.
    Regards,
    Paulina Villacis

    Thanks Ashwini,
    I have used this command but it does not work
    initialli I found this command line like that
    Local CMS
    Name:      Q_SIA_1.CentralManagementServer
         Port: 6400
         Auto-Start: yes
         Command Line: -loggingPath /swbobj/bobje/logging/ -defaultlocale en -port 6400
    I think this command line is incorrect because the port is repeated
    -loggingPath /swbobj/bobje/logging/ -defaultlocale en -port 6400
    I changed the command line to  
    u2013loggingPath /swobj/bobje/logging/ -defaultlocale en   
    but I donu2019t know why after I safe it, it  is the same with u2013port 6400, I think this is the issue. Do you know where also I must to change in order to fix the CMS to port 6400.
    Regards,
    Paulina Villacis

  • Failes to start Managed server using Nodemanager from admin console

    Hi
    I have created the cluster using Weblogic version 9.2 MP3 with
    Machine 1 --> Admin (AS) + Managed server (MS1)
    Machine 2 --> Managed server(MS2)
    All the servers(AS,MS1,MS2) are SSL configured to run in production mode.
    Machine is associated with each managed server and node manager is up and running.
    I have made Host name verification as "None"
    When i start the MS 1 from admin console it comes up in running.However MS2 is not coming in running mode.
    The server logs states that "Could not connect to admin server"
    Cannot decrypt the password ,username and TrustKeyStorePrivatepassphrase.
    Even when i write the clear text password and username in Server_Name/data/nodemanager/boot.properties,then also it throws the same error.
    Node manager is not configured to SSL.
    Any Clue what i am missing????

    Is your Machine #2 shown as "Reachable" in the admin console ( Machines -> Machine2 -> Monitoring )?
    Does your managed server #2 have the same userid and password on its Server -> Configuration -> Server Start page ( UserName & Password fields ) as managed server #1?
    Your boot.properties only needs 2 lines, like:
    password=your plain text password
    username=your plain text username

  • Error while starting the managed server using nodemanager

    HI ,
    I am getting the below error while starting the managed server from the Admin console. All the serverstart and the node manager proeprties looks fine.
    Below is the error in the managed server log,
    startWebLogic.sh: grep: not found
    startWebLogic.sh: uname: not found
    startWebLogic.sh: test: argument expected
    can you help me to solve the problem please. i am using weblogic 10.3.3
    thanks
    Arun

    I think you've changed and added some lines into your startWebLogic.sh script. Can you put your script here?

  • I can not startup Managed server via admin server

    Admin server ip:172.16.219.25
    Admin server name:nstwssadm1.webex.com
    Managed server ip:172.16.219.189
    Managed server name:nstwss001.webex.com.
    I can start Managed server in comand line like 'startManagedWebLogic.sh nstwss001-s1 t3s://nstwssadm1.webex.com:9002'
    But, I can not startup Managed server in console, it appears following log:
    =========
    <Jun 29, 2006 8:56:16 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server nst1::nstwss001-s1 ...>
    <Jun 29, 2006 8:56:16 AM EDT> <Info> <NodeManager@*.*:5555> <BaseProcessControl: saving process id of WebLogic Managed server 'nstwss001-s1', pid: 11072>
    <Jun 29, 2006 8:56:19 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_08 JVM R24.5.0-61 Version ari-49095-20050826-1856-linux-ia32 from BEA Systems, Inc.>
    <Jun 29, 2006 8:56:19 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at https://172.16.219.25:9002 to check if there exists a running admin server at this URL.>
    <Jun 29, 2006 8:56:20 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:20 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:21 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Jun 29, 2006 8:56:21 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358
    WebLogic XMLX Module 8.1 SP5 Mon Sep 19 23:06:54 PDT 2005 641358 >
    <Jun 29, 2006 8:56:21 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server https://172.16.219.25:9002 to retrieve the initial configuration.>
    <Jun 29, 2006 8:56:22 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/bea/weblogic81/common/nodemanager/nstwss001-s1/nstwss001-s1.log is opened. All server side log events will be written to this file.>
    <Jun 29, 2006 8:56:23 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:23 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:26 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:26 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdentity from the jks keystore file /opt/bea/weblogic81/server/lib/DemoIdentity.jks.>
    The WebLogic Server did not start up properly.
    Exception raised: 'weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.'
    Reason: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias DemoIdentity from the jks keystore file /opt/bea/weblogic81/server/lib/DemoIdentity.jks.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/weblogic81/server/lib/DemoTrust.jks.>
    <Jun 29, 2006 8:56:28 AM EDT> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file /opt/bea/jrockit81sp5_142_08/jre/lib/security/cacerts.>
    <Jun 29, 2006 8:56:28 AM EDT> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : localhost>
    <Jun 29, 2006 8:56:28 AM EDT> <Emergency> <WebLogicServer> <BEA-000342> <Unable to initialize the server: weblogic.management.configuration.ConfigurationException: Due to faulty SSL configuration, this server is unable to establish a connection to the node manager.>
    ===============================
    Who can help me on it?
    Thanks.

    your error says:
    'his server is unable to establish a connection to the <b>node manager</b>'
    check that your node manager is running when you try to start de manage server.

  • ClassNotFoundException When Starting Managed Server with NodeManager

    Hi Experts,
    ENV:
    Weblogic Server 10.3.3
    Webcenter 11.1.1.3
    My managed server can be brought up correctly by stopManagedWebLogic.sh <ManagedServerName>. But when trying to start them up, app on that server can not run correctly, and node manager log complained that below classes are not found:
    oracle.jrf.wls.JRFStartup
    oracle.security.jps.wls.JpsWlsStartupClass
    oracle.core.ojdl.weblogic.ODLConfiguration
    oracle.jrf.AppContextStartup
    oracle.ias.cache.Startup
    oracle.dms.wls.DMSStartup
    My Nodemanager is setup following instructions in OBE.Administering Managed Servers by Using the Node Manager(http://www.oracle.com/technology/obe/fusion_middleware/wls103/installconfig/admin_mngd_srvr/admin_ms_using_nm.htm#t4). Output javaclaspath of setWLSEnv.sh has been copy&pasted to admin console->server->..->Server start->classpath
    Thanks,
    Todd

    Trying setting the property StartScriptEnabled=true instead of false.
    You can change this in the nodemanager.properties file (usually located in the directory <middleware-home>/wlserver_10.3/common/nodemanager)
    The classes are set in the startscripts, such as setDomainEnv, which is called by startWebLogic.
    The latter script is set by default in the nodemanager.properties file, through the property StartScriptName=startWebLogic.cmd.

  • Problem while starting managed server using nodemanager

    Hi everyone,
    I am using WLST of Weblogic server 10.3, to automate the creation of domain, managed servers,JDBC,JMS resources etc.. and trying to start the managed servers using node manager. I have an environment which contains few domains. All the domains are using machine named "X".
    Now, i am creating the same machine in my domain WLSTDomain. I have the following doubts.
    Is there a way to check whether the nodemanager(of X) is already running.
    If there is a way to check that, how can we start the managed servers in WLSTDomain using that existing nodemanager.

    1. yes you can check if the nodemanage is running using the following ways.
    For linux env:-
    a. Check if the JAVA process for nodemanager is running ps -ef | grep java and see the nodemanager process else /usr/sbin/lsof -i:$port (port of nodemanager).
    b. Login to Admin Console --> Environment --> Machines --> Click on Machines --> Nodemanager --> Monitoring will give you nodemanager status from Admin console.
    c. use nm() command with WLST
    Example:
    wls:/mydomain/serverConfig> nm()
    Currently connected to Node Manager that is monitoring the domain "mydomain"
    wls:/mydomain/serverConfig> nm()
    Not connected to any Node Manager
    wls:/mydomain/serverConfig>
    To see if WLST connects to nodemanager or not?
    help('nmLog') --> to check the nm logs
    2. To start the nodemanager using WLST here are the commands
    Example:
    For single managed Server
    wls:/mydomain/serverConfig> start('myserver', 'Server', block='false')
    Starting server 'myserver' ...
    The server 'myserver' started successfully.
    wls:/mydomain/serverConfig>
    For Cluster
    wls:/mydomain/serverConfig> start('mycluster', 'Cluster')
    Starting the following servers in Cluster, mycluster: MS1, MS2, MS3...
    All servers in the cluster mycluster are started successfully.
    wls:/mydomain/serverConfig>

  • Cannot start managed server via WLST - 'Overriding the ListenPort ...'

    Hello everyone
    I've created a development domain that has two machine, each of them has two weblogic server instances. On machine-2, I've started NodeManager already.
    I started WLST tool, connect to AdminServer and invoke 'start' command to start managed server on machine-2:
    start('MS-02','Server','t3://dvc.danang.vn:7003')
    but I get fail message like that
    wls:/dnict_domain/serverConfig> start('MS-02','Server','t3://dvc.danang.vn:7003')
    Overriding the ListenPort or ListenAddress is not supported.
    WLST will use the ListenPort and ListenAddress that are configured on the ServerMBean
    Starting server MS-02 ....Permission denied (publickey,password).
    Traceback (innermost last):
      File "<console>", line 1, in ?
      File "<iostream>", line 1280, in start
      File "<iostream>", line 1744, in raiseWLSTException
    WLSTException: Error occured while performing start : Error starting the server : Error occured while performing start : Server with name MS-02 failed to be started 
    Use dumpStack() to view the full stacktrace
    wls:/dnict_domain/serverConfig> dumpStack()
    This Exception occurred at Sun Oct 09 18:46:16 ICT 2011.
    weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be started
         at weblogic.management.scripting.ExceptionHandler.handleException(ExceptionHandler.java:48)
         at weblogic.management.scripting.LifeCycleHandler.startServer(LifeCycleHandler.java:501)
         at weblogic.management.scripting.WLScriptContext.start(WLScriptContext.java:477)
         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 org.python.core.PyReflectedFunction.__call__(Unknown Source)
         at org.python.core.PyMethod.__call__(Unknown Source)
         at org.python.core.PyObject.__call__(Unknown Source)
         at org.python.core.PyObject.invoke(Unknown Source)
         at org.python.pycode._pyx21.start$80(<iostream>:1270)
         at org.python.pycode._pyx21.call_function(<iostream>)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyFunction.__call__(Unknown Source)
         at org.python.pycode._pyx28.f$0(<console>:1)
         at org.python.pycode._pyx28.call_function(<console>)
         at org.python.core.PyTableCode.call(Unknown Source)
         at org.python.core.PyCode.call(Unknown Source)
         at org.python.core.Py.runCode(Unknown Source)
         at org.python.core.Py.exec(Unknown Source)
         at org.python.util.PythonInterpreter.exec(Unknown Source)
         at org.python.util.InteractiveInterpreter.runcode(Unknown Source)
         at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
         at org.python.util.InteractiveInterpreter.runsource(Unknown Source)
         at weblogic.management.scripting.WLST.main(WLST.java:180)
         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.WLST.main(WLST.java:29)
    weblogic.management.scripting.ScriptException: Error occured while performing start : Server with name MS-02 failed to be startedI'm wondering about "Permission denied (publickey,password)" error. Can you show me how to fix this issue?
    Any suggestion is appreciated
    Regards
    Cuong Pham

    Try removing the 't3://dvc.danang.vn:7003' argument. If this information is configured in the managed server, its unnecessary.
    Also, is the NodeManager registered with the AdminServer? You can use the command "nmEnroll([domainDir], [nmHome])" while connected to the AdminServer to if its not.

  • Can we have seperate startup script for each managed server?

    Hi,
    Can we have a seperate startup script (startManagedWebLogic.sh) to start each
    Managed Server? for example startManagedWebLogic.sh for ms1 and startManagedWebLogic.sh
    in ms2 in another directory?
    Any help would be appreciated.
    Thanks
    Siraj

    startManagedWebLogic.sh internally calls startWebLogic.sh with few added parameters, that's all it does. You are free to modify the startup script, the way you want.
    Madan
    >
    Hi,
    Can we have a seperate startup script
    (startManagedWebLogic.sh) to start each
    Managed Server? for example startManagedWebLogic.sh
    for ms1 and startManagedWebLogic.sh
    in ms2 in another directory?
    Any help would be appreciated.
    Thanks
    Siraj

  • Starting managed server with nodemanager

    Hi there,
    Please help me with the weblogic server installation, i've studk with failed to start managed server with node manager. My scenario as below:
    (1) set up the main server and able to run the server successfully.
    (2) set up one managed server, set up one machine on same server as main server.
    (3) assign machine to created managed server.
    (4) after that i've tried to run that managed server and error giving as below:
    Error from main server terminal
    ===================
    <NodeManager> <BEA-300048> <Unable to start the server 'ManagedServer1': Exception while starting server 'ManagedServer1': java.io.IOException: Server failed to start up. See server output log for more details.>
    Error from Node Manager Termal
    ====================
    <Info> <MainServer> <'ManagedServer1'> <Server failed during startup so will not be restarted>
    <Dec 7, 2009 7:04:45 PM> <Warning> <Exception while starting server ''ManagedServer1'': java.io.IOException: Server failed to start up. See server output log for more details.>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:303)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:542)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:119)
    at weblogic.nodemanager.server.Handler.run(Handler.java:66)
    at java.lang.Thread.run(Thread.java:619)
    Thanks in advance,
    Tim

    Sorry , i forgot to mention that the OS i am using is Solaris.
    Thx

  • Can not start instance SAP - ABAP Database is not available via R3trans

    Dear all !
    My OS : Linux RHEL 4U7 32bit
    Oracle 10G R2 32bit 10.2.0.2
    when system running but  power off suddenly
    and when power on ->
    i am having problem as below when i start instance SAP (Databse Oracle Started)
    Step 1 : I login user (ora<sid>) of Oracel to start up database
    Database startup -> OK
    then i tried to shutdown database -> OK too
    and start up again -> OK
    Query -> OK
    I think Database do not problem
    Step 2: start listener -> OK
    Step 3: i login user (<sid>adm) and startup instance SAP (command : startsap r3) with error:
    Checking SED Database
    ABAP Database is not available via R3trans
    Starting SAP-Collector Daemon
    11:11:48 10.02.2010   LOG: Effective User Id is root
    This is Saposcol Version COLL 20.90 700 - Intel x86 with Linux, PL:75, Aug 29 2006
    Usage:  saposcol -l: Start OS Collector
            saposcol -k: Stop  OS Collector
            saposcol -d: OS Collector Dialog Mode
            saposcol -s: OS Collector Status
    The OS Collector (PID 6870) is already running .....
    saposcol already running
    ABAP Database SED must be started first
    Please help me to resolve this problem
    Thanks for your advice

    Dear all !
    1. output of tnsping SED :
    TNS Ping Utility for Linux: Version 10.2.0.2.0 - Production on 11-FEB-2010 13:51:24
    Copyright (c) 1997, 2005, Oracle.  All rights reserved.
    Used parameter files:
    /oracle/SED/102_32/network/admin/sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (COMMUNITY = SAP.WORLD)(PROTOCOL = TCP)(HOST = sapsed)(PORT = 1527))) (CONNECT_DATA = (SID = SED) (GLOBAL_NAME = SED.WORLD)))
    OK (0 msec)
    2. output startsap_.log
    Checking SED Database
    ABAP Database is not available via R3trans
    Starting SAP-Collector Daemon
    saposcol already running
    ABAP Database SED must be started first
    ---> output above repeats many
    3. output trans.log
    4 ETW000 R3trans version 6.14 (release 700 - 18.09.06 - 09:35:00).
    4 ETW000 unicode enabled version
    4 ETW000 ===============================================
    4 ETW000
    4 ETW000 date&time   : 11.02.2010 - 13:49:36
    4 ETW000 control file: <no ctrlfile>
    4 ETW000 R3trans was called as follows: R3trans -d
    4 ETW000  trace at level 2 opened for a given file pointer
    4 ETW000  [dev trc     ,00000]  Thu Feb 11 13:49:36 2010                             159  0.000159
    4 ETW000  [dev trc     ,00000]  db_con_init called                                    27  0.000186
    4 ETW000  [dev trc     ,00000]  create_con (con_name=R/3)                             55  0.000241
    4 ETW000  [dev trc     ,00000]  Loading DB library '/usr/sap/SED/SYS/exe/run/dboraslib.so' ...
    4 ETW000                                                                              63  0.000304
    4 ETW000  [dev trc     ,00000]  load shared library (/usr/sap/SED/SYS/exe/run/dboraslib.so), hdl 0
    4 ETW000                                                                           16430  0.016734
    4 ETW000  [dev trc     ,00000]  Library '/usr/sap/SED/SYS/exe/run/dboraslib.so' loaded
    4 ETW000                                                                              56  0.016790
    4 ETW000  [dev trc     ,00000]  function DbSlExpFuns loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
    4 ETW000                                                                              41  0.016831
    4 ETW000  [dev trc     ,00000]  Version of '/usr/sap/SED/SYS/exe/run/dboraslib.so' is "700.08", patchlevel (0.73)
    4 ETW000                                                                              94  0.016925
    4 ETW000  [dev trc     ,00000]  function dsql_db_init loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
    4 ETW000                                                                              38  0.016963
    4 ETW000  [dev trc     ,00000]  function dbdd_exp_funs loaded from library /usr/sap/SED/SYS/exe/run/dboraslib.so
    4 ETW000                                                                              68  0.017031
    4 ETW000  [dev trc     ,00000]  New connection 0 created                              44  0.017075
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              46  0.017121
    4 ETW000  [dev trc     ,00000]  db_con_connect (con_name=R/3)                         38  0.017159
    4 ETW000  [dev trc     ,00000]  find_con_by_name found the following connection for reuse:
    4 ETW000                                                                              37  0.017196
    4 ETW000  [dev trc     ,00000]  0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
    4 ETW000                                                                              39  0.017235
    4 ETW000  [dev trc     ,00000]  Oracle Client Version: '10.2.0.2.0'                  480  0.017715
    4 ETW000  [dev trc     ,00000]  -->oci_initialize (con_hdl=0)                         42  0.017757
    4 ETW000  [dev trc     ,00000]  Client NLS settings: AMERICAN_AMERICA.UTF8          3789  0.021546
    4 ETW000  [dev trc     ,00000]  Logon as OPS$-user to get SAPSR3's password           48  0.021594
    4 ETW000  [dev trc     ,00000]  Connecting as /@SED on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
    4 ETW000                                                                              51  0.021645
    4 ETW000  [dev trc     ,00000]  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    4 ETW000                                                                              43  0.021688
    4 ETW000  [dev trc     ,00000]    0 UTF8                                                      1  0x9511ea0  0x951750c  0x9516d94
    4 ETW000                                                                              40  0.021728
    4 ETW000  [dev trc     ,00000]  Allocating service context handle for con_hdl=0       40  0.021768
    4 ETW000  [dev trc     ,00000]  Allocating server context handle                      52  0.021820
    4 ETW000  [dev trc     ,00000]  Attaching to DB Server SED (con_hdl=0,svchp=0x9516d20,svrhp=0x9528504)
    4 ETW000                                                                              88  0.021908
    4 ETW000  [dboci.c     ,00000]  *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12505
    4 ETW000                                                                            4712  0.026620
    4 ETW000  [dbsloci.    ,00000]  *** ERROR => CONNECT failed with sql error '12505'
    4 ETW000                                                                              49  0.026669
    4 ETW000  [dev trc     ,00000]  Try to connect with default password                  62  0.026731
    4 ETW000  [dev trc     ,00000]  Connecting as SAPSR3/<pwd>@SED on connection 0 (nls_hdl 0) ... (dbsl 700 110706)
    4 ETW000                                                                              39  0.026770
    4 ETW000  [dev trc     ,00000]  Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
    4 ETW000                                                                              56  0.026826
    4 ETW000  [dev trc     ,00000]    0 UTF8                                                      1  0x9511ea0  0x951750c  0x9516d94
    4 ETW000                                                                              47  0.026873
    4 ETW000  [dev trc     ,00000]  server_detach(con_hdl=0,stale=0,svrhp=0x9528504)
    4 ETW000                                                                              37  0.026910
    4 ETW000  [dev trc     ,00000]  Detaching from DB Server (con_hdl=0,svchp=0x9516d20,srvhp=0x9528504)
    4 ETW000                                                                              37  0.026947
    4 ETW000  [dev trc     ,00000]  Deallocating server context handle 0x9528504          45  0.026992
    4 ETW000  [dev trc     ,00000]  Allocating server context handle                      48  0.027040
    4 ETW000  [dev trc     ,00000]  Attaching to DB Server SED (con_hdl=0,svchp=0x9516d20,svrhp=0x9528504)
    4 ETW000                                                                              60  0.027100
    4 ETW000  [dboci.c     ,00000]  *** ERROR => OCI-call 'OCIServerAttach' failed: rc = 12505
    4 ETW000                                                                            1538  0.028638
    4 ETW000  [dbsloci.    ,00000]  *** ERROR => CONNECT failed with sql error '12505'
    4 ETW000                                                                              41  0.028679
    4 ETW000  [dblink      ,00431]  ***LOG BY2=>sql error 12505  performing CON [dblink#3 @ 431]
    4 ETW000                                                                             131  0.028810
    4 ETW000  [dblink      ,00431]  ***LOG BY0=>ORA-12505: TNS:listener does not currently know of SID given in connect descriptor [dblink#3 @ 431]
    4 ETW000                                                                              39  0.028849
    2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'SED'"
    thansk for your help
    Edited by: myfriend280985 on Feb 11, 2010 7:53 AM

Maybe you are looking for