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.

Similar Messages

  • 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

  • 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

  • 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

  • Error starting managed server with JRockit VM

    I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
    option on. The OS is NT. Any clues , please ?
    exception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    D:\i252\services>runtxnserver
    JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
    Garbage Collector, started.
    [JRockit] Starting Management Server on port 7090
    Starting WebLogic Server ....
    Connecting to http://ocncat2:7991...
    <May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on fd:
    4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
    java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
    35c4a
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    >
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
    tected attempting to connect to admin server at http://ocncat2:7991 during i
    alization of managed server ( null:7551 ). The reported error was: < java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) > This condition generally results when the managed and
    n servers are using the same listen address and port.>
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize th
    rver: 'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    '>
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException:
    .io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace

    I found the solution . The reason for this is that JRockit's High Performance Thread
    System uses asynchrounous I/O "under the hood". Weblogic's Native I/O is also asynchronous.
    The two asynchronous I/O systems clash and the result is the error you see.
    There are two ways around this problem. Either disable JRockit's High Performance
    Thread System (or thinthreads) by using the -Xnativethreads command line flag, or
    disable Weblogic's Native I/O.
    For Weblogic 6.0 and higher, edit the config.xml file. Find the line saying NativeIOEnabled="true"
    and change this to NativeIOEnabled="false".
    For Weblogic 5.1 you edit the file weblogic.properties and change the line weblogic.system.nativeIO.enable=true
    to
    weblogic.system.nativeIO.enable=false
    "Manoj jayadevan" <[email protected]> wrote:
    >
    I getting this error when i start the server with Jrockit VM 3.1 with -Xthinthreads
    option on. The OS is NT. Any clues , please ?
    exception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    D:\i252\services>runtxnserver
    JRockit build 3.1.4-CROSIS-20020429-1505, Thin Threads, Generational Concurr
    Garbage Collector, started.
    [JRockit] Starting Management Server on port 7090
    Starting WebLogic Server ....
    Connecting to http://ocncat2:7991...
    <May 10, 2002 11:50:59 AM PDT> <Error> <NT Performance Pack> <Problem on
    fd:
    4', socket: 'weblogic.rjvm.t3.T3JVMConnection@111'
    java.io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.registerSockInIoPort(Native Method)
    35c4a
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    >
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Configuration Management> <Error
    tected attempting to connect to admin server at http://ocncat2:7991 during
    i
    alization of managed server ( null:7551 ). The reported error was: < java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) > This condition generally results when the managed
    and
    n servers are using the same listen address and port.>
    <May 10, 2002 11:51:00 AM PDT> <Emergency> <Server> <Unable to initialize
    th
    rver: 'Fatal initialization exception
    Throwable: weblogic.management.configuration.ConfigurationException: java.io
    xception: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    '>
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException:
    .io.IOException: couldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort:
    parameter is incorrect.
    (error 87, fd 824)
    at weblogic.socket.NTSocketMuxer.register(Compiled Code)@23e34e90
    at weblogic.rjvm.t3.T3JVMConnection.createConnection(Compiled Code)@
    2410
    at weblogic.rjvm.Protocol.createConnection(Compiled Code)@23e321b0
    at weblogic.rjvm.ConnectionManager.findOrCreateConnection(Compiled
    C
    @23e31b90
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e315b0
    at weblogic.rjvm.ConnectionManager.bootstrap(Compiled Code)@23e30d00
    at weblogic.rjvm.RJVMManager.findOrCreateRemoteInternal(Compiled
    Cod
    3e30810
    at weblogic.rjvm.RJVMManager.findOrCreate(Compiled Code)@23e307b0
    at weblogic.rjvm.RJVMFinder.findOrCreateRemoteServer(Compiled Code)@
    0660
    at weblogic.rjvm.RJVMFinder.findOrCreate(Compiled Code)@23e3001c
    at weblogic.rjvm.ServerURL.findOrCreateRJVM(Compiled Code)@23d7fa00
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(C
    led Code)@23d7ec10
    at weblogic.jndi.Environment.getContext(Compiled Code)@23d7e600
    at weblogic.jndi.Environment.getInitialContext(Compiled Code)@23d7e5
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace
    --------------- nested within: ------------------
    weblogic.management.configuration.ConfigurationException: java.io.IOExceptio
    ouldn't initialize IOPort: The parameter is incorrect.
    (error 87, fd 824) - with nested exception:
    [java.lang.RuntimeException: java.io.IOException: couldn't initialize IOPort
    e parameter is incorrect.
    (error 87, fd 824)]
    at weblogic.management.Admin.initializeRemoteAdminHome(Compiled
    Code
    d7db70
    at weblogic.management.Admin.start(Compiled Code)@23d7c060
    at weblogic.t3.srvr.T3Srvr.initialize(Compiled Code)@23590d00
    at weblogic.t3.srvr.T3Srvr.run(Compiled Code)@23590240
    at weblogic.Server.main(Compiled Code)@23590050
    --- End of stack trace

  • InvalidClassException when starting managed server

    Hi,
    I just created a new managed server from the admin console, but it won't start. Regardless whether I try to start it via the admin console (using NodeManager) or a start script (startManagedWebLogic.sh), it fails with a complaint about an InvalidClassException. For example:
    <24.05.2006 15:07:57 CEST> <Info> <NodeManager@localhost:5555> <Starting Server mydomain::VemaQuickServer ...>
    <24.05.2006 15:07:57 CEST> <Info> <NodeManager@localhost:5555> <BaseProcessControl: saving process id of WebLogic Managed server 'VemaQuickServer', pid: 21452>
    <24.05.2006 15.08 Uhr CEST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Server VM Version 1.5.0_06-b05 from Sun Microsystems Inc.>
    <24.05.2006 15.08 Uhr CEST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://192.168.1.202:9001 to check if there exists a running admin server at this URL.>
    <24.05.2006 15.08 Uhr CEST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <24.05.2006 15.08 Uhr CEST> <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 >
    <24.05.2006 15.08 Uhr CEST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://192.168.1.202:9001 to retrieve the initial configuration.>
    <24.05.2006 15.08 Uhr CEST> <Error> <Configuration Management> <BEA-150001> <An error occurred while connecting to the admin server to bootstrap through URL: http://192.168.1.202:9001/wl_management_internal2/Bootstrap, user: system
    java.io.InvalidClassException: javax.management.ObjectName; local class incompatible: stream classdesc serialVersionUID = -5467795090068647408, local class serialVersionUID = 1081892073854801359
    at java.io.ObjectStreamClass.initNonProxy(ObjectStreamClass.java:519)>
    Any ideas what is going on ?
    Regards
    Heiko

    WLS 8.1 does not support JDK 5.
    You will need to upgrade to WLS 9.x to use JDK 5.
    -- Rob
    WLS Blog http://dev2dev.bea.com/blog/rwoollen/

  • Start managed server with the node manager???

    Hello,
    I have one admin server and one managed server for my domain. Can i Start the amdin and managed server from the node manager and not just the admin server. Currently with the install of node manager only the admin server starts and not the managed server. I need to log in to the admin server to start my managed server which is very cumbersome.
    Edited by: user9021545 on Mar 11, 2011 1:58 PM

    hi,
    In order to start Managed server from the console itself,then u have to enroll your node manager.
    Step1). Start the AdminServer...using startScript "startWebLogic.sh/cmd"
    step2)start ur node manager using stat node manager scripts,
    step3)Login to adminConsole and then see the NodeManager is Reachable or not
    If reachanble
    then run "setWLSEnv.sh/cmd".
    Then run wlst.sh file
    Step3)connect('weblogic','weblogic','t3://localhost:7001')
    Step4)nmEnroll('C:/bea103/user_projects/domains/7001_Domain','C:/bea103/wlserver_10.3/common/nodemanager')
    After this u will be able to start and stop managed server from console itself
    Note:even after dis your managed server doesnt starts then please check under <DOMAIN_ROOT>\servers\<SERVER_NAME> whether you have a folder name as security and inside it whether you have file called as boot.properties
    if no then follow these below steps
    Please create a directory "security" inside your
    <DOMAIN_ROOT>\servers\<SERVER_NAME>
    inside "<DOMAIN_ROOT>\servers\<SERVER_NAME>\security" ( Example Location:
    WLS103/user_projects/domains/Test_Domain/servers/AdminServer/security )
    directory create a file with exactly same name as "boot.properties" and with
    following 2 lines inside it:
    username=weblogic
    password=weblogic
    NOTE: Here "weblogic" is the Administrator username & password...
    if you want dont want to run Admin server from foreground then try runnin it as a background process
    This link wi; b helpful for that
    http://middlewareforum.com/weblogic/?cat=23
    any further help in this den do let me know
    Regards
    Fabian

  • Fatal initialization exception occurs when starting Managed Server

    Hi all,
    First I configured a Adminisistration server and started it. After that I added
    a another server as ManagedServer.These two points to the same Weblogic server.
    When I try to start Managed server by running the script, it gave me following
    error. _______________________________
    <Jun 25, 2001 5:25:11 PM GMT+06:00> <Emergency> <Server> <Unable to initialize
    the server: 'Fatal initialization exception Throwable: java.lang.IllegalAccessError:
    java.security.acl.NotOwnerException java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    at weblogic.security.acl.Realm.getRealm(Realm.java:91) at weblogic.security.acl.Realm.getRealm(Realm.java:36)
    at weblogic.security.acl.Realm.authenticate(Realm.java:183) at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:116) at
    weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:444)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:287)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:259)
    at weblogic.jndi.Environment.getContext(Environment.java:135) at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
    at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:891) at weblogic.management.Admin.start(Admin.java:305)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331) at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35) ______________________________________________
    I suspect reason for this might be weblogic.policy file. There you need to edit
    some lines replacing the location of the directory in which you installed WebLogic
    Server. I did this but still error occurs.
    Do u have any idea why above error occurs and if it is due to the weblogic.policy
    file entry please tell me how it correctly done.
    I am using WL60(sp2)in Win NT,
    My installed dir: E:\bea\wlserver6.0\
    Thanks Nalika

    Hi
    (It was me and Berit that sent the original question).
    After some experimentation we saw that the managed server did get
    some configuration from the admin server, so the problem was in
    there somewhere.
    I had added an (empty) cluster and machine to the admin server, just
    to test adding. When I removed them everything worked fine afterward.
    So it was some kind of configuration error from our side, but we never
    did find out what it was.
    I guess the lesson is to only define things when you really need them :-)
    Regards
    Mikael
    Timothy Fry wrote:
    We're getting the same problem, but on Solaris 2.7.
    Did you get a solution from bea yet?
    Tim
    "Berit Bylund" <[email protected]> wrote in message
    news:[email protected]..
    Hello
    We are trying to start a managed server (under the examples
    domain, NT 4.0, WLS 6.0 Beta 2)
    We start the managed server with the parameter
    -Dweblogic.management.server=http://127.0.0.1:7001

  • Start all managed server with nodemanager wls 8.1

    Hi,
    I've configured nodemanager in my environment, now I'd like to restart all managed servers at boot time. I've created a script that start the nodemanager process at boot time but I didn't found any properties to automatically restart all managed servers.
    How can I do it ?
    Thank you.
    Fanelli Massimiliano
    [email protected]

    Great!
    I had the same error: when starting UCM on WL Console, it starts and says Running. But when accessing it on the browser receive the error 404. In the other hand, when starting with Commands, it force shutdowns.
    I have set the StartScriptEnabled property to true, now I can start UCM only on the command Line, to start it on WL Console, I have to manually start the node manager.
    Is there a way/script to start the node manager automatically?
    Regards,

  • 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

  • Server start arguments ignored when starting managed server

    Hi
    We have configured a bunch of arguments for the managed server through the Admin Console in the Server->Start Arguments
    However those arguments are not picked up when we are starting the managed server.
    We are using a shell script to start the managed server using the weblogic.Admin class functionality.
    If the arguments are set in the JAVA_OPTIONS of setDomainEnv.sh, then they are picked up when starting the managed server.
    The nodemanager is configured with startScriptEnabled=true and startscript set to startWeblogic.sh.
    This is the scenario in Weblogic 10.0.0.
    Can anybody please explain why the arguments are not picked up?
    We tried the same arguments in Weblogic 10.2 and the arguments are picked up even if they are not configured in setDomainEnv.sh
    Is the difference in behavior because of the difference in versions?
    Edited by: user1030647 on Aug 29, 2010 12:26 AM

    Thanks Jay for the immediate responses.
    The thing I am worried about is it seems the behavior in Weblogic 10.0.2 seems to be in consistent with the behavior in Weblogic 10.0.0.
    In Weblogic 10.0.2, even if the JAVA_OPTIONS in setDomainEnv.sh do not include the paramaters that are set in "Server Start->Arguments", when starting the managed servers, they are picked up as can be seen from the managed server log files.
    However, in Weblogic 10.0.0, it seems that these options are not picked up when they are configured in "Server Start->Arguments". Only when they are configured in setDomainEnv.sh are they picked up.
    Do you have any info which points to this discrepancy?

  • Error when starting managed server Message Too Long

              Hi,
              I'm trying to setup clustering with WLS6.1sp2.
              I use the jdk include with wls
              2 servers in the cluster OS=AIX
              1 Adminserver running on Solaris 8
              When I start a managed server on one of the clustered machines
              I see the following error.
              Starting Cluster Service ....
              <Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread listening
              on port 7001, ip address 10.160.3.74>
              <Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast message:
              java.io.IOException: Message too long
              java.io.IOException: Message too long
              at java.net.PlainDatagramSocketImpl.send(Native Method)
              at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
              at java.net.DatagramSocket.send(DatagramSocket.java:341)
              at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
              at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
              at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
              Code))
              at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
              at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
              at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
              at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
              at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
              at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
              at weblogic.Server.main(Server.java:35)
              >
              <Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast messages
              (cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
              <Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic Managed
              Server "s01ap007" for domain "axa" running in Production Mode>
              Also deploying doesn't seem to succeed could this be coused by this error
              I hope someone can help me.
              Best regards,
              Peter Van der Goten
              

              Because I found the answer via Mr. yunyee who also had this problem on an AIX machine
              I will post this also here.
              The problem was that the upd_sendspace variable was set on
              a mutch to low value (9126) or something in this range
              It had to be set on 32769.
              this was done with no -o udp_sendspace=32769
              Best regards,
              Peter
              "Peter Van der Goten" <[email protected]> wrote:
              >
              >Hi,
              >I'm trying to setup clustering with WLS6.1sp2.
              >I use the jdk include with wls
              >2 servers in the cluster OS=AIX
              >1 Adminserver running on Solaris 8
              >
              >When I start a managed server on one of the clustered machines
              >I see the following error.
              >Starting Cluster Service ....
              ><Mar 20, 2002 10:38:38 AM CET> <Notice> <WebLogicServer> <ListenThread
              >listening
              >on port 7001, ip address 10.160.3.74>
              ><Mar 20, 2002 10:38:39 AM CET> <Error> <Cluster> <Error sending multicast
              >message:
              >java.io.IOException: Message too long
              >java.io.IOException: Message too long
              > at java.net.PlainDatagramSocketImpl.send(Native Method)
              > at java.net.PlainDatagramSocketImpl.send(PlainDatagramSocketImpl.java:77)
              > at java.net.DatagramSocket.send(DatagramSocket.java:341)
              > at weblogic.cluster.FragmentSocket.sendThrottled(FragmentSocket.java:133)
              > at weblogic.cluster.FragmentSocket.send(FragmentSocket.java:91)
              > at weblogic.cluster.MulticastSender.fragmentAndSend(MulticastSender.java(Compiled
              >Code))
              > at weblogic.cluster.MulticastSender.send(MulticastSender.java:149)
              > at weblogic.cluster.AnnouncementManager.sendAnnouncement(AnnouncementManager.java:140)
              > at weblogic.cluster.AnnouncementManager.startX(AnnouncementManager.java:91)
              > at weblogic.cluster.AnnouncementManager.start(AnnouncementManager.java:51)
              > at weblogic.cluster.ClusterService.startCommunication(ClusterService.java:192)
              > at weblogic.t3.srvr.T3Srvr.start(T3Srvr.java:540)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:203)
              > at weblogic.Server.main(Server.java:35)
              >>
              ><Mar 20, 2002 10:38:39 AM CET> <Notice> <Cluster> <Listening for multicast
              >messages
              >(cluster wlsHomebankingCluster) on port 7001 at address 237.200.200.1>
              ><Mar 20, 2002 10:38:39 AM CET> <Notice> <WebLogicServer> <Started WebLogic
              >Managed
              >Server "s01ap007" for domain "axa" running in Production Mode>
              >
              >Also deploying doesn't seem to succeed could this be coused by this error
              >
              >I hope someone can help me.
              >Best regards,
              >Peter Van der Goten
              >
              

  • Error when starting managed server

    Hi,
    I have a setup with a admin-server and a managed server. Everything
    worked fine, until one day, an exception started occurring in the logs
    when starting the managed server.
    The setup is:
    - WLS6.1SP2
    - Solaris 8, SPARC
    The exception is:
    javax.naming.NameNotFoundException: Unable to resolve
    weblogic.transaction.resources.atserver1. Resolved:
    'weblogic.transaction.resources'
    Unresolved:'atserver1' ; remaining name ''
    I've taken a look in the admin-servers JNDI-tree, and it is correct,
    it only has "weblogic.transaction.resources", and is missing the
    unresolved "atserver1" part.
    Why is it suddenly referencing this, and what can/should I do about
    it.
    The server seems to be running even with this exception.
    Full stack trace at managed server log:
    <10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
    rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
    52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
    oid: '9', implementation: 'weblogic.jndi.interna
    l.RootNamingNode@6fb3d6''
    javax.naming.NameNotFoundException: Unable to resolve
    weblogic.transaction.resources.atserver1. Resolved:
    'weblogic.transaction.resources'
    Unresolved:'atserver1' ; remaining name ''
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
    at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
    at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy6.list(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
    at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
    at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
    at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Full server stack trace in admin server log:
    <10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
    rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
    70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
    oid: '267', implementation: 'weblogic.management.inte
    rnal.AdminMBeanHomeImpl@46cc9c''
    javax.management.InstanceNotFoundException:
    atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Any help appreciated!
    Regards, Per

    Hi Per
    I have problems in creating managed server in the default mydomain .Do i need
    to configure a new machine if the managed server and admin server are going to be
    in the same machine.
    I created a new machine that has the following parameters
    listen address :localhost
    Listen port :7001
    As the next step i created a server with the machine name pointing to new one, when
    i tried to start this as a managed server it gives an Error
    The WebLogic Server did not start up properly.
    Exception raised: weblogic.management.configuration.ConfigurationException: java
    .security.acl.NotOwnerException - with nested exception:
    [java.lang.IllegalAccessError: java.security.acl.NotOwnerException]
    java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    at weblogic.security.acl.Realm.getRealm(Realm.java:91)
    at weblogic.security.acl.Realm.getRealm(Realm.java:36)
    at weblogic.security.acl.Realm.authenticate(Realm.java:183)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:12
    5)
    could you please help me on creating a managed server
    thanks in advance
    karthik
    [email protected] (Per Olesen) wrote:
    Hi,
    I have a setup with a admin-server and a managed server. Everything
    worked fine, until one day, an exception started occurring in the logs
    when starting the managed server.
    The setup is:
    - WLS6.1SP2
    - Solaris 8, SPARC
    The exception is:
    javax.naming.NameNotFoundException: Unable to resolve
    weblogic.transaction.resources.atserver1. Resolved:
    'weblogic.transaction.resources'
    Unresolved:'atserver1' ; remaining name ''
    I've taken a look in the admin-servers JNDI-tree, and it is correct,
    it only has "weblogic.transaction.resources", and is missing the
    unresolved "atserver1" part.
    Why is it suddenly referencing this, and what can/should I do about
    it.
    The server seems to be running even with this exception.
    Full stack trace at managed server log:
    <10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
    rmi server: 'weblogic.rmi.cluster.ReplicaAwareServerRef@9 - jvmid: '81
    52308822087678327S:192.168.26.196:[7551,7551,7552,7552,7551,7552,-1]:atdomain:atserver1',
    oid: '9', implementation: 'weblogic.jndi.interna
    l.RootNamingNode@6fb3d6''
    javax.naming.NameNotFoundException: Unable to resolve
    weblogic.transaction.resources.atserver1. Resolved:
    'weblogic.transaction.resources'
    Unresolved:'atserver1' ; remaining name ''
    at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:887)
    at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:219)
    at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:129)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:558)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
    at weblogic.jndi.internal.BasicNamingNode.list(BasicNamingNode.java:562)
    at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:93)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicServerRef.dispatch(BasicServerRef.java:166)
    at weblogic.rmi.internal.ServerRequest.sendOneWayRaw(ServerRequest.java:92)
    at weblogic.rmi.internal.ServerRequest.sendReceive(ServerRequest.java:112)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:262)
    at weblogic.rmi.cluster.ReplicaAwareRemoteRef.invoke(ReplicaAwareRemoteRef.java:229)
    at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:35)
    at $Proxy6.list(Unknown Source)
    at weblogic.jndi.internal.WLContextImpl.list(WLContextImpl.java:153)
    at weblogic.transaction.internal.ServerCoordinatorDescriptor.refreshServer(ServerCoordinatorDescriptor.java:1008)
    at weblogic.transaction.internal.ServerCoordinatorDescriptor.access$1(ServerCoordinatorDescriptor.java:944)
    at weblogic.transaction.internal.ServerCoordinatorDescriptor$2.execute(ServerCoordinatorDescriptor.java:936)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Full server stack trace in admin server log:
    <10-06-2002 10:05:54 CEST> <Info> <Dispatcher> <Exception thrown by
    rmi server: 'weblogic.rmi.internal.BasicServerRef@10b - jvmid: '-60698
    70668923812357S:192.168.26.196:[7441,7441,7442,7442,7441,7442,-1]:atdomain:atadmin',
    oid: '267', implementation: 'weblogic.management.inte
    rnal.AdminMBeanHomeImpl@46cc9c''
    javax.management.InstanceNotFoundException:
    atdomain:Location=atserver1,Name=atserver1,Type=ServerRuntime
    at weblogic.management.internal.AdminMBeanHomeImpl.getMBean(AdminMBeanHomeImpl.java:116)
    at weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(Unknown
    Source)
    at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
    at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:267)
    at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:22)
    at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
    at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
    Any help appreciated!
    Regards, Per

  • 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>

  • Acl.NotOwnerException when starting managed server

    I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
    applications
    using the administration server.
    I created a new server with the WL console, and then tried to start it as a managed
    server,
    but I get a java.security.acl.notOwnerException. I start the admin server and
    the managed
    server using the same user account. When prompted for the boot password, I use
    the same
    password to start each server.
    Is there anything I can change in my setup to get around this problem?
    This is the trace of the error:
    startManagedWebLogic.sh myserver2 http://localhost:7501
    p1= myserver2
    p2= http://localhost:7501
    LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
    <Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
    Enter password to boot WebLogic server:systempswd
    Starting WebLogic Server ....
    Connecting to http://localhost:7501...
    log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
    <Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
    "Error" or worse will be displayed in this window. This can be changed at Admin
    Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
    <Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
    'Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    at weblogic.security.acl.Realm.getRealm(Realm.java:91)
    at weblogic.security.acl.Realm.getRealm(Realm.java:36)
    at weblogic.security.acl.Realm.authenticate(Realm.java:183)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:135)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
    at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
    at weblogic.management.Admin.start(Admin.java:303)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    at weblogic.security.acl.Realm.getRealm(Realm.java:91)
    at weblogic.security.acl.Realm.getRealm(Realm.java:36)
    at weblogic.security.acl.Realm.authenticate(Realm.java:183)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:135)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
    at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
    at weblogic.management.Admin.start(Admin.java:303)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Thanks in advance for any help.
    Joan

    Hi Joan
    Go to the Managedserver Confiuration and give the Correct listen Port and SSL.I hope this will help you.
    Nagesh Rao
    Joan Silverman wrote:
    I have installed the evaluation version of WL 6.0 and sp1 on Solaris and can run
    applications
    using the administration server.
    I created a new server with the WL console, and then tried to start it as a managed
    server,
    but I get a java.security.acl.notOwnerException. I start the admin server and
    the managed
    server using the same user account. When prompted for the boot password, I use
    the same
    password to start each server.
    Is there anything I can change in my setup to get around this problem?
    This is the trace of the error:
    startManagedWebLogic.sh myserver2 http://localhost:7501
    p1= myserver2
    p2= http://localhost:7501
    LD_LIBRARY_PATH=/private/weblogic/weblogic6.0/wlserver6.0/lib/solaris
    <Mar 29, 2001 2:31:16 PM PST> <Info> <Security> <Getting boot password from user.>
    Enter password to boot WebLogic server:systempswd
    Starting WebLogic Server ....
    Connecting to http://localhost:7501...
    log file: /private/weblogic/weblogic6.0/wlserver6.0/./myserver2.log
    <Mar 29, 2001 2:31:26 PM PST> <Info> <Logging> <Only log messages of severity
    "Error" or worse will be displayed in this window. This can be changed at Admin
    Console> mydomain> Servers> myserver2> Logging> General> Stdout severity threshold>
    <Mar 29, 2001 2:31:26 PM PST> <Emergency> <Server> <Unable to initialize the server:
    'Fatal initialization exception
    Throwable: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    at weblogic.security.acl.Realm.getRealm(Realm.java:91)
    at weblogic.security.acl.Realm.getRealm(Realm.java:36)
    at weblogic.security.acl.Realm.authenticate(Realm.java:183)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:135)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
    at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
    at weblogic.management.Admin.start(Admin.java:303)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    '>
    The WebLogic Server did not start up properly.
    Exception raised: java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    java.lang.IllegalAccessError: java.security.acl.NotOwnerException
    at weblogic.security.acl.Realm.getRealm(Realm.java:91)
    at weblogic.security.acl.Realm.getRealm(Realm.java:36)
    at weblogic.security.acl.Realm.authenticate(Realm.java:183)
    at weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
    at weblogic.security.acl.internal.Security.authenticate(Security.java:116)
    at weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFactoryDelegate.java:429)
    at weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:272)
    at weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:244)
    at weblogic.jndi.Environment.getContext(Environment.java:135)
    at weblogic.jndi.Environment.getInitialContext(Environment.java:118)
    at weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
    at weblogic.management.Admin.start(Admin.java:303)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    Thanks in advance for any help.
    Joan

Maybe you are looking for

  • Error encountered while doing on-demand refresh of Power BI report

    When I try to manually refresh a PowerBI excel that has been uploaded on to SharePoint, I get this error. "OnPremise error: Sorry, you don't have permissions to retrieve data for this data connection. Request access from your Power BI admin. An error

  • E-mail disappeared from Apple Mail in Mavericks

    Hello, I think I experienced a bug yesterday in Apple Mail (I am running Mac OS X 10.9): While organizing my e-mails, I made a new folder in my iCloud account in Apple Mail. Let's call it "Apple". Then I used the search function to find the e-mails (

  • Convert CMYK to Spot Color or 2 Color in Adobe Acrobat 9 Standard

    I have a file that is in a CMYK color format. The original document was created is MS Word. The file is currently CMYK but the printer I am sending it to needs either Spot Color or 2 color. Can I conver CMYK to either of these in Acrobat 9 standard?

  • Use of cookies in fixed-layout EPUBs

    I am creating a fixed-layout picture ebook in EPUB2 format to be published on the iBookstore. In order to start some CSS3 animations at the same time on both pages of a page spread, I'd like to use a mechanism to synchronize the start time for the an

  • Canon EOS 50D

    Just announced by Canon, the EOS50D. Relevance to this forum? US pricing in dollars is the same as price in euros, so yet another rip-off for loyal EU customers!