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.

Similar Messages

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

  • 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

  • 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

  • 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

  • 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

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

  • 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

  • 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 Server from Administration Console

    Hi
    I am new for SOA and fusion. Can anyone share the brief steps that are needed to start/stop a Managed Server from Admin Console.
    I did a fresh install on RHEL5 and configure a domain. i was able to start the services from script which are created when creating a domain.
    But when i assigned a Managed Server to a Node Manager and try starting the Managed server. It does not start and in the log i can see exceptions like below
    Failed to invoke startup class "JPS Startup Class", java.lang.ClassNotFoundException: oracle.security.jps.wls.JpsWlsStartupClass
    java.lang.ClassNotFoundException
    Failed to invoke startup class "ODL-Startup", java.lang.ClassNotFoundException: oracle.core.ojdl.weblogic.ODLConfiguration
    java.lang.ClassNotFoundException
    I start the services in below order
    Weblogic Server
    node Manager
    and
    soa_server
    Thanks
    Hari

    you must set to true the StartScriptEnabled property in nodemanager.properties

  • How to start managed server from admin server both running

    I have an admin server on one machine and created a managed server on different
    machine, I am not able to start managed server from either machine. When I used
    the admin server machine to start the managed server remotely I got this message
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
    ogic Managed Server "managedserver3" for domain "admindomain">
    <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
    create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
    java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
    a
    ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
    to
    bind to any port such that it is not reachable from the console.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception>
    When I tried to connect managed server from its machine to admin server (running
    on separate machine ) I got this error
    Starting WebLogic Server...
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
    ed during initialization. Exception:java.lang.SecurityException: Authentication
    for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
    initialize the server: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Reason: Fatal initialization exception
    Throwable: java.lang.SecurityException: Authentication for user system denied
    java.lang.SecurityException: Authentication for user system denied
    at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    Thanks.

    "fkeita" <[email protected]> wrote in message
    news:[email protected]...
    >
    I have an admin server on one machine and created a managed server ondifferent
    machine, I am not able to start managed server from either machine. When Iused
    the admin server machine to start the managed server remotely I got thismessage
    >
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Securityinitializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328><Starting WebL
    ogic Managed Server "managedserver3" for domain "admindomain">
    <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350><Unable to
    create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port:8002.
    java.net.BindException: Cannot assign requested address: JVM_Bind Perhapsthe
    a
    ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port8002.>
    >
    Try running netstat to see whether another process is actually running at
    the given address/port.
    Also check using ifconfig/ipconfig or directly checking /etc/hosts file of
    the box to see whether the ips addreses are correct.
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Serverfailed
    to
    bind to any port such that it is not reachable from the console.>
    <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342><Unable to
    initialize the server: Fatal initialization exception>
    When I tried to connect managed server from its machine to admin server(running
    on separate machine ) I got this error
    Starting WebLogic Server...
    Connecting to http://fkeita:7001...
    <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Securityinitializi
    ng using realm myrealm.>
    <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364><Server fail
    ed during initialization. Exception:java.lang.SecurityException:Authentication
    for user system denied
    java.lang.SecurityException: Authentication for user system denied
    atweblogic.security.service.SecurityServiceManager.doBootAuthorization(
    SecurityServiceManager.java:978)
    atweblogic.security.service.SecurityServiceManager.initialize(SecurityS
    erviceManager.java:1116)
    at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
    at weblogic.Server.main(Server.java:31)
    >Seems to be some issue with security credentials.
    Try running the manageed server directly (as sort of admin) by not passing
    the admin server url and bringing it just like an admin server.
    See if this works. If it works, then soemthing wrong in the way the admin
    server is receiving the request/security credentials from managed server.
    Also make sure both managed and admin servers are on the same patch/service
    pack level.
    -Sabha

  • How to start managed server from admin server both running on separate machines

              I have an admin server on one machine and created a managed server on different
              machine, I am not able to start managed server from either machine. When I used
              the admin server machine to start the managed server remotely I got this message
              Connecting to http://fkeita:7001...
              <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security initializi
              ng using realm myrealm.>
              <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328> <Starting WebL
              ogic Managed Server "managedserver3" for domain "admindomain">
              <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350> <Unable to
              create a server socket on Channel Default for: BFINKELMAN/90.0.0.25, port: 8002.
              java.net.BindException: Cannot assign requested address: JVM_Bind Perhaps the
              a
              ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using port 8002.>
              <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server failed
              to
              bind to any port such that it is not reachable from the console.>
              <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception>
              When I tried to connect managed server from its machine to admin server (running
              on separate machine ) I got this error
              Starting WebLogic Server...
              Connecting to http://fkeita:7001...
              <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security initializi
              ng using realm myrealm.>
              <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364> <Server fail
              ed during initialization. Exception:java.lang.SecurityException: Authentication
              for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              >
              <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342> <Unable to
              initialize the server: Fatal initialization exception
              Throwable: java.lang.SecurityException: Authentication for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              >
              The WebLogic Server did not start up properly.
              Exception raised:
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              Reason: Fatal initialization exception
              Throwable: java.lang.SecurityException: Authentication for user system denied
              java.lang.SecurityException: Authentication for user system denied
              at weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              SecurityServiceManager.java:978)
              at weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              erviceManager.java:1116)
              at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              at weblogic.Server.main(Server.java:31)
              Thanks.
              

              I used startmanagedweblogic managedserver1 http://fkeita:7001 to try to start managed
              server, but it did not work, and got error messages. Error messages are posted
              on my first posting.
              "pankaj" <[email protected]> wrote:
              >Use the startManagedWeblogic.cmd / .sh script to start your
              >Managed/Clustered servers
              >
              >
              >"fkeita" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> I have an admin server on one machine and created a managed server
              >on
              >different
              >> machine, I am not able to start managed server from either machine.
              >When I
              >used
              >> the admin server machine to start the managed server remotely I got
              >this
              >message
              >>
              >> Connecting to http://fkeita:7001...
              >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <Security> <090082> <Security
              >initializi
              >> ng using realm myrealm.>
              >> <Jul 17, 2002 11:11:06 AM EDT> <Notice> <WebLogicServer> <000328>
              ><Starting WebL
              >> ogic Managed Server "managedserver3" for domain "admindomain">
              >> <Jul 17, 2002 11:11:28 AM EDT> <Emergency> <WebLogicServer> <000350>
              ><Unable to
              >> create a server socket on Channel Default for: BFINKELMAN/90.0.0.25,
              >port:
              >8002.
              >> java.net.BindException: Cannot assign requested address: JVM_Bind
              >Perhaps
              >the
              >> a
              >> ddress BFINKELMAN/90.0.0.25 is incorrect or another process is using
              >port
              >8002.>
              >>
              >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <Security> <090085> <Server
              >failed
              >> to
              >> bind to any port such that it is not reachable from the console.>
              >> <Jul 17, 2002 11:11:29 AM EDT> <Emergency> <WebLogicServer> <000342>
              ><Unable to
              >> initialize the server: Fatal initialization exception>
              >>
              >> When I tried to connect managed server from its machine to admin server
              >(running
              >> on separate machine ) I got this error
              >>
              >> Starting WebLogic Server...
              >> Connecting to http://fkeita:7001...
              >> <Jul 17, 2002 11:15:18 AM EDT> <Notice> <Security> <090082> <Security
              >initializi
              >> ng using realm myrealm.>
              >> <Jul 17, 2002 11:15:18 AM EDT> <Critical> <WebLogicServer> <000364>
              ><Server fail
              >> ed during initialization. Exception:java.lang.SecurityException:
              >Authentication
              >> for user system denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> >
              >> <Jul 17, 2002 11:15:18 AM EDT> <Emergency> <WebLogicServer> <000342>
              ><Unable to
              >> initialize the server: Fatal initialization exception
              >> Throwable: java.lang.SecurityException: Authentication for user system
              >denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> >
              >>
              >***************************************************************************
              >> The WebLogic Server did not start up properly.
              >> Exception raised:
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >> Reason: Fatal initialization exception
              >> Throwable: java.lang.SecurityException: Authentication for user system
              >denied
              >> java.lang.SecurityException: Authentication for user system denied
              >> at
              >weblogic.security.service.SecurityServiceManager.doBootAuthorization(
              >> SecurityServiceManager.java:978)
              >> at
              >weblogic.security.service.SecurityServiceManager.initialize(SecurityS
              >> erviceManager.java:1116)
              >> at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:703)
              >> at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:588)
              >> at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:276)
              >> at weblogic.Server.main(Server.java:31)
              >>
              >> Thanks.
              >
              >
              

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

  • Start Managed Server from Admine clonsole FAILED_NOT_RESTARTABLE

    when trying to start the managed server Managed-Server-01 from the WLS Admin Console the managed server status becomes <FAILED_NOT_RESTARTABLE> and not coming up:
    Managed servers logs:
    /usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-01/logs:
    3/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false>
    <Sep 13, 2011 6:15:46 PM> <Debug> <NodeManager> <Environment: SERVER_NAME=Managed-Server-03>
    <Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
    <Sep 13, 2011 6:15:46 PM> <Info> <NodeManager> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server-03.out">
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: grep: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: uname: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: expr: not found
    /usr/local/bea/user_projects/domains/eShop/bin/startWebLogic.sh: test: argument expected
    <Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <Waiting for the process to die: 1226>
    <Sep 13, 2011 6:15:47 PM> <Info> <NodeManager> <Server failed during startup so will not be restarted>
    <Sep 13, 2011 6:15:47 PM> <Debug> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    --=--
    Node Manager log during Managed-Server-01 start from WLS Admin Console shows:
    15:46 PM> <Info> <eShop> <Managed-Server-03> <Working directory is "/usr/local/bea/user_projects/domains/eShop">
    <Sep 13, 2011 6:15:46 PM> <Info> <eShop> <Managed-Server-03> <Server output log file is "/usr/local/bea/user_projects/domains/eShop/servers/Managed-Server-03/logs/Managed-Server
    -03.out">
    <Sep 13, 2011 6:15:47 PM> <Info> <eShop> <Managed-Server-03> <Server failed during startup so will not be restarted>
    <Sep 13, 2011 6:15:47 PM> <Warning> <Exception while starting server 'Managed-Server-03': 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:6
    Note:
    The installation of WLS done using Root.
    We can start/stop MS using conventional ways.
    Cheers,

    although i am not an expert,
    but i am very confident that any WLS you install,
    it can be configured like i tried it,
    First Environment-----Machine
    Add a machine by giving a name
    Second Environment------Server
    Add a server giving a sever name
    Third Environment----machine
    Add the server to the machine from the tab server
    Fourth Environment-------server
    Add A a SSL Port to the Sever and save
    Click Start Server and every thing goes well
    Thanks
    Edited by: kashif, pakistan on Sep 14, 2011 4:09 AM

  • Browse jms destinations on managed servers (from admin server)

    I need to browse JMS destinations from the admin server (in a WebLogic
    9.2 console extension) that are only deployed on the managed servers.
    I can get destination attributes via the domain runtime server, but
    no JNDI or actually browse the destinations. All destinations in
    which I am interested are queues.
    I know I can change my initial context, but if that is the way to go, is there a way to determine the managed
    servers' URLs at runtime?
    Thank you for any help,
    Seth

    hi
    this worked for me (on 8.1). I suppose there are
    better ways in 9.2
    Context adminCtx = null;
    adminCtx = getInitialContextForAdminServer();
    MBeanHome adminhome = (MBeanHome)
    adminCtx.lookup(MBeanHome.ADMIN_JNDI_NAME);
    // Get the list of running managed
    ning managed servers and iterate over itSet
    Set srSet =
    Set srSet =
    adminhome.getMBeansByType("ServerRuntime");
    Iterator sr_iter = srSet.iterator();
    while (sr_iter.hasNext())
    ServerRuntimeMBean bean =
    timeMBean bean = (ServerRuntimeMBean) sr_iter.next();
    // Get the home for the managed
    for the managed server
    MBeanHome remoteHome = (MBeanHome)
    me = (MBeanHome) adminCtx.lookup(MBeanHome.JNDI_NAME
    + "." + bean.getName());
    // Get the MBeanServer for the
    anServer for the managed server
    MBeanServer rmbs =
    eanServer rmbs = remoteHome.getMBeanServer();
    //invoke it
    ObjectName objectName= new
    objectName= new ObjectName("$mbean");
    rmbs.invoke(objectName,operation,params,types);
    Edited by deepshet at 05/05/2007 10:00 AMThank you for the help.
    MBeanHome is deprecated as of 9.0, so I was unable to directly use your example. You have helped though, thank you.
    As of now I am querying the domain runtime server for:
    ObjectName("com.bea:*,Type=ServerRuntime")
    I am then iterating through the returned Set to get the server URLs and then setting my InitialContext with a PROVIDER_URL of the managed servers. This allows me to Look Up a Destination without JNDI based on step 4 from [url http://edocs.bea.com/wls/docs92/jms/implement.html#wp1313933]here. I can then browse as needed.
    The ugly part is that if I include the Admin URL in my PROVIDER_URL then it does not work, so I am checking for it as I loop through the set of ServerRuntimes and not including it.
    Further though slightly less annoying is that the managed server URLs include "t3://" but if I leave it in there, a malformed URL exception is thrown when setting the PROVIDER_URL. So I also remove all of those and then preppend one on the front for PROVIDER_URL as I actually need.
    It is not pretty, but it is working on the only cluster I have been able to try thus far.
    If anyone was a cleaner suggestion, please share.

Maybe you are looking for

  • Anyone successfully using Btrfs with dm-cache - any howtos

    Hi Does anyone successfully set up dm-cache (or flashcache) on arch? If so is it performing well and stable for you? and how did you set it up (nothing yet on the wiki)? thanks in advance

  • Transferring music to an ipod

    I want to transfer music from my Mac to an ipod that was orginally set up with a PC. I want to be able to transfer the music from my Mac and still be able to transfer music from a PC also. What can I do??? thanks

  • MB1B with mov. type 311 - error message

    hai experts I have deleted AAA storage location (in spro) actually stock is available in that storage location. now again i have created AAA storage location (in spro), now i want to trf. that stock.. while doing MB1B with mov. type 311 at the time o

  • Mac Pro won't connect to Airport but G4 Titanium has no problem

    My Mac Pro has trouble finding the Airport(N) base station, it is connected to my Virgin Media Cable modem. Airport Utility intermittently sees the base station but drops out with the messsage "Airport Utility can't find basestation but the airport i

  • SRS-X7 ClearAudio+

    Where is the clearaudio+ feature on the SRS-X7? The SRS-X5 has a button on top of the unit, but I don't see it in pictures for the SRS-X7. I would like to be able to use this device using bluetooth without needing any aditional software, like I can w