Start managed servers via admin console

Hello,
I have installed weblogic server, created a domain, added a managed server. All working fine. Now I want to be able to start managed server through admin console.
According to this documentation (http://docs.oracle.com/cd/E13222_01/wls/docs81/adminguide/confignodemgr.html), it should all be pre-configured for development environment. But when i try start the managed server in admin console, it says "server does not have a machine associated with it." I added a machine and assigned that machine to the managed server, now it says "the Node Manager associated with machine m1 is not reachable.".
Can someone point to instructions on how to setup this on dev environment. In one of the instructions, it is suggested to change nodemanager.properties in common\nodemanager folder. But this file doesn't exist in my environment.
All i want is to start all admin and managed server with one script or with start the admin server and able to start the managed servers via console.
Thanks,

Hi,
Check from the console whether your node manager is reachable or not.
Console Path:
Machines -> <YOUR_MACHINE_NAME> -> Monitoring (tab) -> Node Manager Status (sub-tab) -> Status: Reachable
You Can follow the below link for "Node manager not reachable"
http://middlewaremagic.com/weblogic/?p=5205
Once done,check the status of the node manager.
Still even after this if the node manager is not reachable
Check the node manager logs,whether you get any exceptions
location $weblogic_home\wlserver_10.3\common\nodemanager\nodemanger.log
You can take help of the below link for trouble shooting the basic node manager exceptions.
http://middlewaremagic.com/weblogic/?p=2887
Or You can even paste the error's on this post itself,we will guide you .
Regards
FAbian

Similar Messages

  • Unable to start Managed servers from admin console

    Hello!
    We have a problem to start Managed Servers throw Node manager.
    We get an error:
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Boot identity properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/boot.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Startup configuration properties saved to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/data/nodemanager/startup.properties"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh >
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Starting WebLogic server with command line: /software/psoft/pt851/webserv/peoplesoft/bin/startManagedWebLogic.sh
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Working directory is '/software/psoft/pt851/webserv/peoplesoft'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Working directory is '/software/psoft/pt851/webserv/peoplesoft'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001">
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Rotated server output log to "/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out00001"
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server error log also redirected to server log>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.LogFileRotationUtil log
    INFO: Server error log also redirected to server log
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'
    <Jan 26, 2012 2:17:54 PM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 26, 2012 2:17:54 PM> <WARNING> <Exception while starting server 'PIA1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Jan 26, 2012 2:17:54 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Additional information:
    weblogic 10.3.3
    PT8.51.11
    Linux x86_64 RH5
    When we starting Manged servers manualy, it's works fine.
    Thank you.

    Hello!
    The problem is found.
    We tried to startup managed server by running startManagedServer.sh script, but this script expecting to get parameters.
    The NodeManager unable to send parameters to script that appears in nodemanager.properties file (StartScriptName).
    So, I created a new script startPIA.sh, that calls to startManagedServer.sh and sends it 2 parameters:
    ./startManagedWebLogic.sh $SERVER_NAME $ADMIN_URL
    Now, we can start and stop managed servers from admin console, BUT we still have an error in NodeManager:
    <Jan 29, 2012 11:15:39 AM> <INFO> <peoplesoft> <PIA1> <Server failed during startup so will not be restarted>
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    <Jan 29, 2012 11:15:39 AM> <WARNING> <Exception while starting server 'PIA1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    Jan 29, 2012 11:15:39 AM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'PIA1'
    java.io.IOException: Server failed to start up. See server output log for more details.
    at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:331)
    at weblogic.nodemanager.server.Handler.handleStart(Handler.java:567)
    at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:118)
    at weblogic.nodemanager.server.Handler.run(Handler.java:70)
    at java.lang.Thread.run(Thread.java:662)
    There are no errors in managed servers logs.
    PIA1.out:
    <Jan 29, 2012 11:15:38 AM> <INFO> <NodeManager> <Server output log file is '/software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1.out'>
    Attempting to start WebLogic Server PIA1
    No activity will be logged to this window.
    Server activity will be logged to /software/psoft/pt851/webserv/peoplesoft/servers/PIA1/logs/PIA1_*
    PID for WebLogic Server PIA1 is: 27018
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <Waiting for the process to die: 26847>
    <Jan 29, 2012 11:15:39 AM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jan 29, 2012 11:15:39 AM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    The status of managed server in admin console is RUNNING, but "Status of Last Action" is FAILED.
    What can be the reason?
    Thank you.

  • Unable to start managed servers from Admin Console "FAILED_NOT_RESTARTABLE"

    I recently installed WebLogic 10.3.5, JRockit, and ECM 11.1.1.5. I'm to the point where I am trying to get Nodemanager configured so I can stop/start managed servers through the admin console. I have the following listed in Environment > Servers:
    AdminConsole - running
    IBR_server1 - FAILED_NOT_RESTARTABLE
    managedServer1 - FAILED_NOT_RESTARTABLE
    UCM_server1 - FAILED_NOT_RESTARTABLE
    I followed the tutorial at http://blogs.oracle.com/jamesbayer/entry/weblogic_nodemanager_quick_sta to get to the point where the AdminServer starts when the server reboots, so I think Nodemanager is working there. If I view Machines > Monitoring, it says Nodemanager "Reachable." However, when I go to restart IBR_server1, managedServer1, or UCM_server1, I get the FAILED_NOT_RESTARTABLE status. I am using the weblogic server's IP for the machine name/host because our DNS is still screwed up. Would that have any affect on this?
    I'm completely unsure what to do now. The Nodemanager log shows:
    INFO - <Loading domains file: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
    WARNING - <Domains file not found: E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.domains>
    INFO - <Loading identity key store: FileName=E:/oracle/MIDDLE~1/WLSERV~1.3/server\lib\DemoIdentity.jks, Type=jks, PassPhraseUsed=true>
    WARNING - <Node manager configuration properties file 'E:\oracle\MIDDLE~1\WLSERV~1.3\common\nodemanager\nodemanager.properties' not found. Using default settings.>
    So I'm confused why it's saying the properties file and domains file are not found... I've checked and they exist at
    E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.properties
    and
    E:\oracle\middleware\wlserver_10.3\common\nodemanager\nodemanager.domains
    The domains file contains
    base_domain=e\:\\oracle\\middleware\\user_projects\\domains\\base_domain
    Which is correct.
    Any idea what I'm missing here? I can provide more detail if needed. Thank you.
    EDIT: I should add that I can start the UCM and IBR managed servers using the start up scripts on the server, but that's not what I'm after. I want everything controlled through the AdminConsole and want to be sure that when the server reboots, all the managed servers come back up correctly.
    Edited by: user5824683 on Oct 5, 2011 5:04 PM
    Edited by: user5824683 on Oct 5, 2011 5:09 PM

    I did a bit of digging, and it seems I have an issue with -Xnohup... I've verified this arugment exists in all of my managed servers properties files, yet it still bombs when I try to restart from the webLogic console. I should note that if I start fresh from the server, I can start all my manager servers using WLST nmStart().
    starting weblogic with Java version:
    java version "1.6.0_24"
    Java(TM) SE Runtime Environment (build 1.6.0_24-b07)
    Oracle JRockit(R) (build R28.1.3-11-141760-1.6.0_24-20110301-1430-windows-x86_64, compiled mode)
    Starting WLS with line:
    E:\java\JROCKI~1.1\bin\java -jrockit -Xms256m -Xmx512m -Dweblogic.Name=IBR_server1 -Djava.security.policy=E:\oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=E:\oracle\middleware\user_projects\domains\base_domain\servers\IBR_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xnohup -Xverify:none -da -Dplatform.home=E:\oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=E:\oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=E:\oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1 -Djrockit.optfile=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\servers\IBR_server1 -Doracle.domain.config.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\carml -Digf.arisidstack.home=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=e:\oracle\MIDDLE~1\USER_P~1\domains\BASE_D~1\servers\IBR_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,E:\oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol -Dweblogic.jdbc.remoteEnabled=false -Ducm.oracle.home=E:\oracle\MIDDLE~1\ORACLE~2 -Dem.oracle.home=E:\oracle\middleware\oracle_common -Djava.awt.headless=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://138.126.180.177:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=e:\oracle\MIDDLE~1\patch_wls1035\profiles\default\sysext_manifest_classpath weblogic.Server
    Exception in thread "Main Thread" java.lang.NoClassDefFoundError: –Xnohup
    Caused by: java.lang.ClassNotFoundException: –Xnohup
         at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
         at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:305)
         at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308)
         at java.lang.ClassLoader.loadClass(ClassLoader.java:246)
    Could not find the main class: –Xnohup. Program will exit.
    <Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4252>
    <Oct 6, 2011 12:38:13 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Oct 6, 2011 12:38:13 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>

  • Starting managed servers from admin console vs. command line

    Will the arguments I enter in the "Arguments" section of the "Server start" admin console page also be used if I start the managed server from the command line using startManagedWeblogic.sh?
    And conversely, will changes I make to the scripts take effect when I start the server from the admin console?

    No,
    the arguments that you set thru Console GUI are effective when Node manager start your server.
    Ammar Sajdi

  • Unable to start Managed server from admin console using nodemanager

    I changed the ip address and hostname of the server on which Weblogic Server 10.3.5 is running. After that I am unable to start the managed servers using Admin console. Is there any changes in the nodemanager configuration files which need to be done to start the managed servers from admin console.

    Hi there,
    Can you check the following configuration in Weblogic admin console ?
    1- Check which listen address mentioned under the Machine configuration ( Environment > Machines > select appropriate nodemanager machine >Configuration > Node Manager ). If it is pointing to old host name, change it to new one.
    2- Once you done with Step 1. Check whether the machine is reachable or not. ( Machine > [Your Machine] > Monitoring > status.
    3- If still isuse persists.. Check the managed server startup log files ( for eg:- managedserver1.out under the path $DOMAIN_HOME\Servers\managedserver1\logs directory.
    Thanks
    Lakshman

  • Problem while starting Managed Servers from Admin Server console

    I am facing a problem while trying to start the managed servers in wlp8.1 portal from the admin server console.
    <Dec 7, 2004 4:52:14 PM IST> <Info> <NodeManager@*.*:5555> <Starting Server orbitPortalDomain::orbit_ManagedServer1 ...>
    <Dec 7, 2004 4:52:16 PM IST> <Info> <NodeManager@*.*:5555> <Server orbitPortalDomain::orbit_ManagedServer1 started, process id = 1,832>
    <Dec 7, 2004 4:52:17 PM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Client VM Version 1.4.2_04-b05 from Sun Microsystems Inc.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://10.6.0.212:7001 to check if there exists a running admin server at this URL.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973
    WebLogic XMLX Module 8.1 SP3 Tue Jun 29 23:11:19 PDT 2004 404973 >
    <Dec 7, 2004 4:52:18 PM IST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://10.6.0.212:7001 to retrieve the initial configuration.>
    <Dec 7, 2004 4:52:21 PM IST> <Notice> <Log Management> <BEA-170019> <The server log file D:\bea_turner\weblogic81\common\nodemanager\orbit_ManagedServer1\orbit_ManagedServer1.log is opened. All server side log events will be written to this file.>
    The WebLogic Server did not start up properly.
    java.lang.NoClassDefFoundError: com/bea/wsrp/util/debug/Debug
    at com.bea.wsrp.security.WSRPIdentityAsserterProviderImpl.<clinit>(WSRPIdentityAsserterProviderImpl.java:45)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
    at java.lang.Class.newInstance0(Class.java:308)
    at java.lang.Class.newInstance(Class.java:261)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.createSecurityProvider(SecurityServiceManagerDelegateImpl.java:232)
    at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:939)
    at weblogic.security.service.PrincipalAuthenticator.initialize(PrincipalAuthenticator.java:151)
    at weblogic.security.service.PrincipalAuthenticator.<init>(PrincipalAuthenticator.java:257)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(SecurityServiceManagerDelegateImpl.java:581)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegateImpl.java:420)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.java:698)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelegateImpl.java:731)
    at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl.java:874)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:717)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:822)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:670)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:344)
    at weblogic.Server.main(Server.java:32)
    Reason: com/bea/wsrp/util/debug/Debug
    pls advice
    Thanks
    Sasanka

    Hello,
    There is a lot of stuff on this thread:
    http://forum.java.sun.com/thread.jspa?threadID=567363&messageID=2801617
    these guys are trying to run weblogic with JBuilder.
    Looks like your classpath is incorrect, can you go to your admin console-->server-->remote start
    copy the classpath and post it here.
    Check for spaces in your classpath, missing jars or directories and miss spelt paths.
    Has this problem been occuring as soon as you installed WLP or not?
    Cheers,
    Hoos

  • Error start managed server from admin console in SSL mode

    I have configured Admin server, managed servers and node manager on the same physical server and commonly using a single SSL sertificate.
    There is no problem to start node manager, admin server and managed server individually. But if I try to start managed server from the admin console then I am getting the following errors.
    <Feb 22, 2005 11:02:26 AM CST> <Info> <[email protected]:6666> <Starting Server peoplesoft::PIA1 ...>
    <Feb 22, 2005 11:02:26 AM CST> <Info> <NodeManager@xxxxxxxxxx:6666> <BaseProcessControl: saving process id of Weblogic Managed server 'PIA1', pid: 285390>
    <Feb 22, 2005 11:02:35 AM CST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Classic VM Version 1.4.1 from IBM Corporation>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://xxxxxxxx:admin_server_portnumber to check if there exists a running admin server at this URL.>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
    <Feb 22, 2005 11:02:36 AM CST> <Info> <Management> <BEA-141107> <Version: WebLogic Temporary Patch 8 CR174605 for PeopleSoft 09/09/2004 18:11:35
    WebLogic Server 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284
    WebLogic XMLX Module 8.1 SP2 Fri Dec 5 15:01:51 PST 2003 316284 >
    <Feb 22, 2005 11:02:37 AM CST> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://xxxxxxxxx.org:Admin_server_portnumber to retrieve the initial configuration.>
    <Feb 22, 2005 11:02:45 AM CST> <Notice> <Log Management> <BEA-170019> <The server log file /home/xxxx/webserv/peoplesoft/PIA1/PIA1.log is opened. All server side log events will be written to this file.>
    <Feb 22, 2005 11:03:01 AM CST> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>
    <Feb 22, 2005 11:03:01 AM CST> <Warning> <Security> <BEA-090066> <Problem handling boot identity. The following exception was generated: java.lang.NullPointerException>
    <Feb 22, 2005 11:03:10 AM CST> <Critical> <Security> <BEA-090174> <The trust keystore configuration specified on the command line or in boot.properties does not match the trust keystore configuration specified in config.xml.>
    <Feb 22, 2005 11:03:10 AM CST> <Warning> <NodeManager> <BEA-300038> <The node manager is unable to monitor this server. Could not create an SSL connection to the node manager. Reason : null>
    <Feb 22, 2005 11:03:10 AM CST> <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.>
    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.
    I am running everything on IBM UNIX server.
    I appriciate your help.
    Thanks & regards,
    Laxman.

    Hi
    From the admin console ... Are you able to check the status of Node Manager ?
    If yes ... please check the SSL configuration of managed servers ...
    Check the domain administration port also.
    Jin

  • Error starting managed server through admin console

    Hey,
    I am trying to start the managed server through the admin console, but it gives fails and give errors in the log, below mention is the log file details:
    ####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909> <ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    com.bea.common.engine.ServiceInitializationException: weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.security.spi.ProviderInitializationException: [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
         at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
         at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
         at java.lang.Thread.run(Thread.java:595)
         at weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
         at weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
         at com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
         at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
         at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
         at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909> <ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException: [Security:090399]Security Services Unavailable
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:898)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
         at weblogic.security.SecurityService.start(SecurityService.java:141)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am using weblogic server 9.2 on windows. Node manager is working fine. i have tried installing weblogic server several times but it gives the same error each time i start a managed server. Kindly help.
    Regards,
    Alka

    Can you start a managed server from the command line?
    <Alka Parveen> wrote in message news:[email protected]...
    Hey,
    I am trying to start the managed server through the admin console, but it
    gives fails and give errors in the log, below mention is the log file
    details:
    ####<2007-dec-18 kl 14:05 CET> <Error> <Security> <SESO-ODX251909>
    <ManagedServer_1> <[ACTIVE] ExecuteThread: '0' for queue:
    'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <>
    <1197983149062> <BEA-090870> <The realm "myrealm" failed to be loaded:
    weblogic.security.service.SecurityServiceException:
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    weblogic.security.service.SecurityServiceException:
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:469)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    com.bea.common.engine.ServiceInitializationException:
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:342)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    weblogic.security.spi.ProviderInitializationException:
    [Security:090730]Failed to verify credential mapper LDAP hierarchy
    netscape.ldap.LDAPException: Server or network error (81)
    at netscape.ldap.LDAPConnThread.networkError(LDAPConnThread.java:768)
    at netscape.ldap.LDAPConnThread.run(LDAPConnThread.java:555)
    at java.lang.Thread.run(Thread.java:595)
    at
    weblogic.security.providers.credentials.DefaultCredentialMapperLDAPHelper.getInstance(DefaultCredentialMapperLDAPHelper.java:115)
    at
    weblogic.security.providers.credentials.DefaultCredentialMapperProviderImpl.initialize(DefaultCredentialMapperProviderImpl.java:93)
    at
    com.bea.common.security.internal.legacy.service.SecurityProviderImpl.init(SecurityProviderImpl.java:53)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:340)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:292)
    at
    com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:263)
    at
    com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:71)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:461)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:822)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:851)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1007)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    >
    ####<2007-dec-18 kl 14:05 CET> <Critical> <WebLogicServer> <SESO-ODX251909>
    <ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1197983149109>
    <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.security.service.SecurityServiceRuntimeException:
    [Security:090399]Security Services Unavailable
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.doBootAuthorization(CommonSecurityServiceManagerDelegateImpl.java:898)
    at
    weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1029)
    at
    weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:854)
    at weblogic.security.SecurityService.start(SecurityService.java:141)
    at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
    at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
    at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
    I am using weblogic server 9.2 on windows. Node manager is working fine. i
    have tried installing weblogic server several times but it gives the same
    error each time i start a managed server. Kindly help.
    Regards,
    Alka

  • Problems starting managed server from admin console WL70 portal

    I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
              

    I get the following exception when I try to start the managed server from admin server console. Both Admin server and managed server are on the same machine.
              

  • Starting managed server from admin console

              Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
              I did the same way as you said here but still getting following error.....Could you
              address me where I did a mistake
              Starting WebLogic Server ....
              Connecting to http://localhost:7001...
              <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic Managed
              Server "MyServer1" for domain "mydomain">
              <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize the server:
              'Fatal initialization exception
              Throwable: java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              Start server side stack trace:
              java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              ***************************************************************************Start
              server side stack trace:
              java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              at weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              at weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.java:164)
              at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              <<no stack trace available>>
              '>
              The WebLogic Server did not start up properly.
              Exception raised: weblogic.management.configuration.ConfigurationException: connecting
              to http://localhost:7001/wl_management_internal2/Bootstrap - with nested exception:
              [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
              HTTP to server: 'localhost', port: '7001']
              java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP
              to server: 'localhost', port: '7001'
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
              at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
              at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
              at weblogic.net.http.HttpClient.New(HttpClient.java:149)
              at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
              at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:279)
              at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
              at weblogic.management.Admin.initialize(Admin.java:320)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              at weblogic.Server.main(Server.java:35)
              --------------- nested within: ------------------
              weblogic.management.configuration.ConfigurationException: connecting to http://localhost:7001/wl_management_internal2/Bootstrap
              - with nested exception:
              [java.net.ConnectException: Tried all: '1' addresses, but could not connect over
              HTTP to server: 'localhost', port: '7001']
              at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
              at weblogic.management.Admin.initialize(Admin.java:320)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              at weblogic.Server.main(Server.java:35)
              Reason: Fatal initialization exception
              t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              End server side stack trace
              <<no stack trace available>>
              Reason: Fatal initialization exception
              <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555> <WindowsProcessControl:
              online successfully invoked on server 'MyServer1', pid: 1892>
              

    Change the "Listen Address" attribute of the admin server to be its machine
              name or IP address. I think you currently have it set to "localhost".
              Hopefully this should fix atleast one of the exceptions below.
              -- Anand
              "Janavi" <[email protected]> wrote in message
              news:[email protected]...
              >
              > Hi Anand Byrappagiri(Bea guy, I saw him on this group but can't remember),
              >
              > I did the same way as you said here but still getting following
              error.....Could you
              > address me where I did a mistake
              >
              >
              > __________________________________________
              > Starting WebLogic Server ....
              > Connecting to http://localhost:7001...
              >
              > <Mar 4, 2002 5:19:17 PM EST> <Notice> <WebLogicServer> <Starting WebLogic
              Managed
              > Server "MyServer1" for domain "mydomain">
              > <Mar 4, 2002 5:19:20 PM EST> <Emergency> <Server> <Unable to initialize
              the server:
              > 'Fatal initialization exception
              > Throwable: java.lang.ClassCastException:
              weblogic.security.acl.DefaultUserInfoImpl
              >
              >
              > Start server side stack trace:
              > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              > at
              weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              > at
              weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
              a:164)
              >
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              > at
              weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > End server side stack trace
              >
              > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              >
              >
              ***************************************************************************S
              tart
              > server side stack trace:
              > java.lang.ClassCastException: weblogic.security.acl.DefaultUserInfoImpl
              > at
              weblogic.kernel.BootServicesImpl.authenticate(BootServicesImpl.java:189)
              > at weblogic.kernel.BootServicesImpl.invoke(BootServicesImpl.java:145)
              > at weblogic.rjvm.RJVMImpl.dispatchRequest(RJVMImpl.java:620)
              > at weblogic.rjvm.RJVMImpl.dispatch(RJVMImpl.java:581)
              > at
              weblogic.rjvm.ConnectionManagerServer.handleRJVM(ConnectionManagerServer.jav
              a:164)
              >
              > at weblogic.rjvm.ConnectionManager.dispatch(ConnectionManager.java:640)
              > at weblogic.rjvm.t3.T3JVMConnection.dispatch(T3JVMConnection.java:454)
              > at weblogic.socket.NTSocketMuxer.processSockets(NTSocketMuxer.java:643)
              > at
              weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:24)
              > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
              > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > End server side stack trace
              >
              > <<no stack trace available>>
              > '>
              >
              > The WebLogic Server did not start up properly.
              > Exception raised:
              weblogic.management.configuration.ConfigurationException: connecting
              > to http://localhost:7001/wl_management_internal2/Bootstrap - with nested
              exception:
              >
              > [java.net.ConnectException: Tried all: '1' addresses, but could not
              connect over
              > HTTP to server: 'localhost', port: '7001']
              > java.net.ConnectException: Tried all: '1' addresses, but could not connect
              over HTTP
              > to server: 'localhost', port: '7001'
              > at weblogic.net.http.HttpClient.openServer(HttpClient.java:203)
              > at weblogic.net.http.HttpClient.openServer(HttpClient.java:254)
              > at weblogic.net.http.HttpClient.<init>(HttpClient.java:117)
              > at weblogic.net.http.HttpClient.New(HttpClient.java:149)
              > at weblogic.net.http.HttpURLConnection.connect(HttpURLConnection.java:109)
              > at
              weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:27
              9)
              >
              > at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:990)
              > at weblogic.management.Admin.initialize(Admin.java:320)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              > at weblogic.Server.main(Server.java:35)
              > --------------- nested within: ------------------
              > weblogic.management.configuration.ConfigurationException: connecting to
              http://localhost:7001/wl_management_internal2/Bootstrap
              > - with nested exception:
              > [java.net.ConnectException: Tried all: '1' addresses, but could not
              connect over
              > HTTP to server: 'localhost', port: '7001']
              > at weblogic.management.Admin.getBootstrapLocalServer(Admin.java:1081)
              > at weblogic.management.Admin.initialize(Admin.java:320)
              > at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:359)
              > at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
              > at weblogic.Server.main(Server.java:35)
              > Reason: Fatal initialization exception
              >
              > t weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
              > End server side stack trace
              >
              > <<no stack trace available>>
              > Reason: Fatal initialization exception
              >
              > <Mar 4, 2002 5:37:12 PM EST> <Info> <[email protected]:5555>
              <WindowsProcessControl:
              > online successfully invoked on server 'MyServer1', pid: 1892>
              > _______________________________________
              >
              

  • Starting Managed Servers without admin Server

    dear All
    i have a Weblogic Server contains the following
    Admin Server
    LoadBalancer Server
    Cluster Contains Server1 & Server2
    and every thing is fine, but i have the following problem : while starting any Node from Cluster or LoadBalancer Server using startManagedWebLogic.cmd without starting up admin server, i am getting the following error in my log
    Caused By: oracle.security.jps.service.idstore.IdentityStoreException: JPS-00056: Failed to create identity store service instance idstore.ldap.provider:idstore.ldap. Reason: weblogic.security.service.SecurityServiceRuntimeException: Invalid host or port for admin server..     at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getIdStoreConfig(LdapIdentityStoreProvider.java:195)
         at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.access$300(LdapIdentityStoreProvider.java:70)
         at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance(LdapIdentityStoreProvider.java:242)
         at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:114)
         at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance(LdapIdentityStoreProvider.java:70)
         at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance(ContextFactoryImpl.java:139)
         at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:170)
         at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext(ContextFactoryImpl.java:191)
         at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:132)
         at oracle.security.jps.internal.core.runtime.JpsContextFactoryImpl.getContext(JpsContextFactoryImpl.java:127)
         at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:798)
         at oracle.security.jps.internal.policystore.PolicyUtil$1.run(PolicyUtil.java:792)
         at oracle.security.jps.internal.policystore.PolicyUtil.getDefaultPolicyStore(PolicyUtil.java:792)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:289)
         at oracle.security.jps.internal.policystore.PolicyDelegationController.<init>(PolicyDelegationController.java:283)
         at oracle.security.jps.internal.policystore.JavaPolicyProvider.<init>(JavaPolicyProvider.java:261)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
         at java.lang.Class.newInstance0(Class.java:355)
         at java.lang.Class.newInstance(Class.java:308)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadOPSSPolicy(CommonSecurityServiceManagerDelegateImpl.java:1339)
         at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1020)
         at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:879)
         at weblogic.security.SecurityService.start(SecurityService.java:142)
         at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:207)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:176)

    Isn't this exactly what the admin service is used for?
    I think you need to start the admin server before starting the other servers.
    Timo

  • Starting managed Servers under WLS 8.1 using Operator Role

    Hi,
    we've configured a user who is acting in the default 'Operator' role.
    He can shutdown a managed server using the admin console, but when
    trying to restart that managed server via node manager he fails with an exception.
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
    principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
    According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
    this role should be allowed to start managed servers.
    -- What are we doing wrong ? --
    Cheers,
    Robert

    I believe this is a known problem, please contact BEA support for a patch.
    Thanks,
    -satya
    Robert Akolk wrote:
    Hi,
    we've configured a user who is acting in the default 'Operator' role.
    He can shutdown a managed server using the admin console, but when
    trying to restart that managed server via node manager he fails with an exception.
    weblogic.management.NoAccessRuntimeException: Access not allowed for subject:
    principals=[oper, Operators], on ResourceType: Server Action: write, Target: ExpectedToRun
    According to the documentation http://edocs.bea.com/wls/docs81/secwlres/secroles.html
    this role should be allowed to start managed servers.
    -- What are we doing wrong ? --
    Cheers,
    Robert

  • 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

  • I am unable to start Managed Servers through Weblogic AdminConsole

    Hi,
    We are using Weblogic 10.3.1.0 version.
    Totaly 4 Managed Severs
    1 Admin Server
    with Nodemanger.
    In Admin Console When ever we going to Stop the Manged Servers.
    1. Environment ----- > Servers ---- > Control ----------- > Mananged Server 1 -----------> Force shutdown
    2. Then click refresh button ---- showing "FAILED_NOT_RESTARTABLE"
    3. after that when ever we going to start the Managed Server in Admin console
    First its Showing ----- Starting
    and next its showing ----- FAILED_NOT_RESTARTABLE
    4. its not coming to Running State.
    In Logs
    Domain log
    -----------> <1273141345460> <BEA-000450> <Socket 8 internal data record unavailable (probable closure due idle timeout), event received 17>
    ####<06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280738> <BEA-000396> <Server shutdown has been requested by weblogic>
    ####<06-May-2010 11:54:40 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280771> <BEA-000365> <Server state changed to FORCE_SUSPENDING>
    ####<06-May-2010 11:54:40 o'clock BST> <Notice> <Cluster> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143280844> <BEA-000163> <Stopping "async" replication service>
    ####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281061> <BEA-000365> <Server state changed to ADMIN>
    ####<06-May-2010 11:54:41 o'clock BST> <Notice> <WebLogicServer> <ukirt156> <twpserver1> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <weblogic> <> <> <1273143281064> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    ####<06-May-2010 11:54:41 o'clock BST> <Notice> <Server> <ukirt156> <twpserver1> <DynamicListenThread[Default]> <<WLS Kernel>> <> <> <1273143281113> <BEA-002607> <Channel "Default" listening on 172.21.149.168:7003 was shutdown.>
    ####<06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <ukirt156> <AdminServer> <[ACTIVE] ExecuteThread: '45' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1273143390016> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
    AdminServer log
    <06-May-2010 11:56:30 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
    <06-May-2010 11:57:33 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
    <06-May-2010 12:07:02 o'clock BST> <Error> <NodeManager> <BEA-300048> <Unable to start the server twpserver1 : Exception while starting server 'twpserver1': java.io.IOException: Server failed to start up. See server output log for more details.>
    ManagedServer Log
    <06-May-2010 11:54:40 o'clock BST> <Alert> <WebLogicServer> <BEA-000396> <Server shutdown has been requested by weblogic>
    06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
    INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutting down.
    06-May-2010 11:54:41 org.quartz.core.QuartzScheduler pause
    INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED paused.
    06-May-2010 11:54:41 org.quartz.core.QuartzScheduler shutdown
    INFO: Scheduler DefaultQuartzScheduler_$_NON_CLUSTERED shutdown complete.
    <06-May-2010 11:54:54> <Debug> <NodeManager> <Waiting for the process to die: 19316>
    <06-May-2010 11:54:54> <Info> <NodeManager> <Server was shut down normally>
    <06-May-2010 11:54:54> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    NodeManager Log
    <06-May-2010 11:54:54> <Info> <twp_domain> <twpserver1> <Server was shut down normally>
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Boot identity properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties">
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Startup configuration properties saved to "/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/startup.properties">
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00020">
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Starting WebLogic server with command line: /appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/bin/java -Dweblogic.Name=twpserver1 -Djava.security.policy=/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.management.server=http://ukirt156:7001 -Djava.library.path="/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386/jrockit:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/lib/i386:/appl/weblogic/oracle/middleware/jrockit_160_05_R27.6.2-20/jre/../lib/i386::/appl/nsm/CA/UnicenterNSM/lib:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386/client:/appl/nsm/CA/SharedComponents/JRE/1.4.2_09/lib/i386:/appl/nsm/CA/SharedComponents/ccs/dia/dna/lib:/appl/nsm/CA/SharedComponents/ccs/dia/lib:/usr/lib:/opt/CA/CAlib:/appl/nsm/CA/SharedComponents/lib:/appl/nsm/CA/SharedComponents/Csam/SockAdapter/lib:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686:/appl/weblogic/oracle/middleware/wlserver_10.3/server/native/linux/i686/oci920_8" -Djava.class.path=/data/share/package/twp/WEB-INF/lib/ojdbc14.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic_sp.jar:/appl/weblogic/oracle/middleware/wlserver_10.3/server/lib/weblogic.jar -Dweblogic.system.BootIdentityFile=/appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xmanagement:port=7091,ssl=false,authenticate=false -Xms=1200m -Xmx=1200m -Xverbose:gc,gcpause -Dreflexis.scheduler=true -Dreflexis.server=twpserver1 -Djava.awt.headless=true -Dclient.encoding.override=UTF-8 -Doracle.jdbc.V8Compatible=true weblogic.Server >
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Working directory is "/appl/weblogic/scripts">
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Rotated server output log to "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out00021">
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server error log also redirected to server log>
    <06-May-2010 11:56:21> <Info> <twp_domain> <twpserver1> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
    <06-May-2010 11:56:29> <Info> <twp_domain> <twpserver1> <Server failed during startup so will not be restarted>
    <06-May-2010 11:56:29> <Warning> <Exception while starting server 'twpserver1': 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:332)
    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)
    Server logs
    <06-May-2010 12:06:57> <Info> <NodeManager> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
    [JRockit] Management server started on port 7091, ssl=false, authenticate=false.
    <06-May-2010 12:06:59 o'clock BST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.2-20_o-108500-1.6.0_05-20090120-1115-linux-ia32 from BEA Systems, Inc.>
    <06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the username attribute value of {AES}xvFgPysVi5b89pYwaAppoqPXQ5wFVW13yoFhzhKmuQo= from the file /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties. If you have copied an encrypted attribute from boot.properties from another domain into /appl/weblogic/scripts/servers/twpserver1/data/nodemanager/boot.properties, change the encrypted attribute to its cleartext value then reboot the server. The attribute will be re-encrypted. Otherwise, change all encrypted attributes to their cleartext values, then reboot the server. All encryptable attributes will be re-encrypted. The decryption failed with the exception <06-May-2010 12:07:01 o'clock BST> <Info> <Management> <BEA-141223> <The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the
    <06-May-2010 12:07:01 o'clock BST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
    There are 1 nested errors:
    weblogic.management.ManagementException: [Management:141223]The server name twpserver1 specified with -Dweblogic.Name does not exist. The configuration includes the following servers {AdminServer}.
    at weblogic.management.provider.internal.RuntimeAccessImpl.<init>(RuntimeAccessImpl.java:149)
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:41)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:749)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:488)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:446)
    at weblogic.Server.main(Server.java:67)
    >
    <06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
    <06-May-2010 12:07:01 o'clock BST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
    <06-May-2010 12:07:01 o'clock BST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
    <06-May-2010 12:07:02> <Debug> <NodeManager> <Waiting for the process to die: 19443>
    <06-May-2010 12:07:02> <Info> <NodeManager> <Server failed during startup so will not be restarted>
    <06-May-2010 12:07:02> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Note: if i start the manged servers through WLST script its working fine.
    [twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
    nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
    nmStart('twpserver1')
    Please provide the solution, how to solve this issue.
    Thanks
    SRK

    Just at first glance, it seems as though you have one or more configuration issues, perhaps inconsistencies between the node manager server configuration files and the domain's config.xml
    nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
    nmStart('twpserver1')
    implies that tmp_domain is configured in /appl/weblogic/oracle/middleware/user_projects/domains, (which is the default from the configuration wizard). However, the node manager and server output logs make it seem like it's trying to use a domain in the directory /appl/weblogic/scripts. Not sure how that happened, perhaps you had two domains? Perhaps copied or moved the domain files? Something else?
    In any case, start by checking out your nodemanager.domains file and ensure that it reflects your intended domain directory.

  • Starting managed servers

    Hi,
    Environment: WebLogic 6.1 SP2, JDK1.3.1, Solaris 8
    1. How to start the managed servers using NodeManager from the command line? Already
    NodeManager configured and able to start managed servers from the Admin Console.
    So from the console start/stop/kill managed servers is fine. From the command
    line, if I use `weblogic.Server` to start managed server it's not using the node
    manager.
    2. In the `java weblogic.nodemanager.NodeManager help`, option `starttemplate`
    defaults to `nodemanager.sh`. Any details on this please ?
    3. Each time we start managed server with Node Manager, it writes the output to
    the new file `OutputFile=./config/NodeManagerlogs/<server>/startserver-<XXXX.log`.
    From the documentation it looks like we can set logs directory
    `-Dweblogic.nodemanager.savedLogsDirectory=path`, however is it possible to specify
    the log file name also?
    4. Where is the location of the java applications `System.out`, if the managed
    server is started with NodeManager. If the managed server is started with `weblogic.Server`
    the `System.out` are printed to the console. So this enables us to redirect to
    a file.
    thanks
    Sarva Meduri

    I think you can configure the NodeMgr to start ManagedServers instead of having the
    Windows Service start the servers. Basically you configure NodeMgr as a Windows Service
    and then let NM take care of starting other servers. I believe you have to set
    ManagedServer's HostsMigratableServices attribute to false to enable NM start the server.
    By default it is true.
    prasen
    Gerardo Rojas wrote:
    Hi:
    I have been trying to configure my WebLogic environment to start the managed servers
    in a domain automatically when the machine is rebooted. I have done some testing
    with Node Manager but, as I understood, Node Manager only restarts a server if
    it was started using Node Manager and the server crashes or fails. On the other
    hand, if the server is installed as a Windows service, it will be started at reboot
    time, but not when the server (not the machine) crashes or fails. So, both solutions
    seems to be uncompatible. Is it right?? Is it possible to have both benefits,
    that is, to get the managed servers started at boot time (as done by Windows services)
    and restarted each time they fail (as done by Node Manager)?
    Thanks,
    Gerardo

Maybe you are looking for

  • Outlook 2010 when deleting meeting attendees, not prompting to send to added/deleted attendees

    Hello, We have been having this issue for quite some time and I have endlessly searched the internet for answers as well as this forum but it doesn't seem like anyone has been able to help.  We are using Outlook 2010 and I have two employees who need

  • Alternatives to Spotify

    This latest desktop update is the straw that broke the camels back for many paying customers. So I ask: What alternatives to Spotify have you tried, and would you recommend? List pros and cons.

  • How can i verify that this is a legitimate seller of apple products.

    Sales in large bulk, older apple products.  See link http://www.aakash.com.sg/index.php?option=com_virtuemart

  • Why is MAX crashing my computer?

    when I run the resource monitor in MAX my computer is locking up at the "configuring mainframe 1" stage.  The set up is a pci-mxi-2 to vme-mxi-2.  Do you have any idea what could be causing the computer to hang up like this?

  • Refresh JTabbedPane when tab is pushed?

    My JtabbedPane is working fine, but the problem is that my last JFrame in my JtabbedPane called arkiv has to get updated everytime its tab is pushed and i cant get to work .I tried repaint() ,removeAll() but cant get it to work... Can anyone help me