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.

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

  • A lot of problem for an error: Cannot start Managed Server through NM

    Hi, all. Thank for coming here.
    My main problem is cannot start Manager server through Node Manager. I've configured with the same way on my friend's network and It's works but It's wrong with mine.
    my weblogic domain:
    Machine 1: Administration Server + 1 Managed server
    Machine 2: 1 Managed server
    all of these servers communicate through SSL protocol. When I try to start Managed Server on remote machine:
    output from console which was invoked startWebLogic.sh
    +<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    +<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
    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:541)
    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:619)
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    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:541)
    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:619)
    And this is MS01 log:
    starting weblogic with Java version:
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    +JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
    The application has requested the JVM to exit with an fatal error from JNI. Error message:
    JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    Starting WLS with line:
    +/opt/Oracle/Middleware/jrockit_160_14_R27.6.5-32/bin/java -jrockit -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx512m -Dweblogic.Name=MS01 -Djava.security.policy=/opt/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.system.BootIdentityFile=/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/data/nodemanager/boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=true -Dweblogic.ReverseDNSAllowed=false -Xrs -Xverify:none -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=/opt/Oracle/Middleware/wlserver_10.3 -Dwls.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/opt/Oracle/Middleware/wlserver_10.3/server -Dweblogic.wsee.bind.suppressDeployErrorMessage=true -Dweblogic.wsee.skip.async.response=true -Dweblogic.management.discover=false -Dweblogic.management.server=http://192.168.1.35:7001 -Dwlw.iterativeDev=true -Dwlw.testConsole=true -Dwlw.logErrorsToConsole=true -Dweblogic.ext.dirs=/opt/Oracle/Middleware/patch_wls1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/patch_wlp1032/profiles/default/sysext_manifest_classpath:/opt/Oracle/Middleware/wlportal_10.3/p13n/lib/system:/opt/Oracle/Middleware/wlportal_10.3/light-portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/portal/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/lib/system:/opt/Oracle/Middleware/wlportal_10.3/analytics/lib/system:/opt/Oracle/Middleware/wlportal_10.3/apps/lib/system:/opt/Oracle/Middleware/wlportal_10.3/info-mgmt/deprecated/lib/system:/opt/Oracle/Middleware/wlportal_10.3/content-mgmt/lib/system -Dweblogic.alternateTypesDirectory=/opt/Oracle/Middleware/wlportal_10.3/portal/lib/security weblogic.Server+
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    +JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]+
    The application has requested the JVM to exit with an fatal error from JNI. Error message:
    JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    Stopping PointBase server...
    PointBase server stopped.
    And this is output from console which node manager runs on:
    +<Sep 9, 2010 12:09:53 PM> <INFO> <devdomain> <MS01> <Server failed during startup so will not be restarted>+
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.ServerManager log
    INFO: Server failed during startup so will not be restarted
    +<Sep 9, 2010 12:09:53 PM> <WARNING> <Exception while starting server 'MS01'>+
    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:541)
    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:619)
    Sep 9, 2010 12:09:53 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    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:541)
    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:619)
    I tried to start Managed server some times again, but I face up to strange issue, this is output from console which Admin Server runs on (these exception messages throws continuously):
    +<Sep 9, 2010 12:42:53 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "cgDataSource-nonXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "p13nDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSource": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    +<Sep 9, 2010 12:42:58 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceAlwaysXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>+
    I can ensure that all of these connection pool has configured to run on 9093 port already. Then I view the DOMAIN_NAME/pointbase.log, it said:
    Unable to start the server. start server error: java.net.BindException: Address already in use
    I cannot understand what's run on pointbase address ?
    All of these error make me angry, because I've configured with the same way on other system and It's work. I've spent all of week to fix these bug, but I'm having nothing :((
    Please help me.

    Thank Jay SenSharma.
    I've looked for these JAVA_OPTION values you said, but I cant found them. That value is content of JAVA_DEBUG option, not JAVA_OPTION. In my situation, JAVA_DEBUG=" " (it's not set by default).
    Please re-view my error log:
    Node Manager output:
    +<Sep 9, 2010 11:32:44 PM> <WARNING> <Exception while starting server 'MS01'>+
    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:541)
    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:619)
    Sep 9, 2010 11:32:44 PM weblogic.nodemanager.server.Handler handleStart
    WARNING: Exception while starting server 'MS01'
    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:541)
    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:619)
    Managed server MS01's log:
    +<Sep 9, 2010 11:45:05 PM> <INFO> <NodeManager> <Server output log file is '/opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.out'>+
    +<Sep 9, 2010 11:45:07 PM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA JRockit(R) Version R27.6.5-32_o-121899-1.6.0_14-20091001-2113-linux-ia32 from BEA Systems, Inc.>+
    +<Sep 9, 2010 11:45:09 PM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server Temporary Patch for 9216172 Tue Jan 12 02:07:27 PST 2010+
    WebLogic Server 10.3.2.0  Tue Oct 20 12:16:15 PDT 2009 1267925 >
    +<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - Invalid xsi:type qname: 'wsrp:wsrp-identity-asserterType' in element realm@http://xmlns.oracle.com/weblogic/domain>+
    +<Sep 9, 2010 11:45:13 PM EDT> <Error> <Management> <BEA-141244> <Schema validation errors while parsing /opt/Oracle/Middleware/user_projects/domains/devdomain/config/config.xml - /opt/Oracle/Middleware/user_projects/domains/devdomain/<unknown>:11:9: error: failed to load java type corresponding to t=wsrp-identity-asserterType@http://www.bea.com/ns/wlp/90/security/wsrp>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320400> <The log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log will be rotated. Reopen the log file if tailing has stopped. This can happen on some platforms like Windows.>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <LoggingService> <BEA-320401> <The log file has been rotated to /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log00002. Log messages will continue to be logged in /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log.>+
    +<Sep 9, 2010 11:45:14 PM EDT> <Notice> <Log Management> <BEA-170019> <The server log file /opt/Oracle/Middleware/user_projects/domains/devdomain/servers/MS01/logs/MS01.log is opened. All server side log events will be written to this file.>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Error> <Security> <BEA-090870> <The realm "myrealm" failed to be loaded: weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory". See the nested exception for details..+
    weblogic.security.service.SecurityServiceException: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:342)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: com.bea.common.engine.ServiceInitializationException: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:365)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
    +     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
    +     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal internal error> org.apache.openjpa.util.InternalException: There was an error when invoking the static getInstance method on the named factory class "kodo.jdbc.kernel.KodoJDBCBrokerFactory".  See the nested exception for details.
    +     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:95)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
    +     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
    +     Truncated. see log file for complete stacktrace+
    Caused By: java.lang.RuntimeException: There were errors initializing your configuration: <openjpa-1.1.1-SNAPSHOT-r422266:807362 fatal store error> org.apache.openjpa.util.StoreException: com.pointbase.jdbc.jdbcUniversalDriver
    +     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:123)+
    +     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.createConnectionFactory(JDBCConfigurationImpl.java:776)+
    +     at org.apache.openjpa.jdbc.conf.JDBCConfigurationImpl.getConnectionFactory(JDBCConfigurationImpl.java:683)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:597)+
    +     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:288)+
    +     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
    +     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)+
    +     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)+
    +     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)+
    +     at java.lang.reflect.Method.invoke(Method.java:597)+
    +     at org.apache.openjpa.kernel.Bootstrap.invokeFactory(Bootstrap.java:124)+
    +     at org.apache.openjpa.kernel.Bootstrap.getBrokerFactory(Bootstrap.java:90)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate$StoreSerivceHelper.getPersistenceManagerFactory(StoreServiceDelegate.java:347)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.initJDO(StoreServiceDelegate.java:145)+
    +     at com.bea.common.security.storeservice.util.StoreServiceDelegate.<init>(StoreServiceDelegate.java:98)+
    +     at com.bea.common.security.internal.service.StoreServiceImpl.init(StoreServiceImpl.java:76)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:363)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.findOrStartService(ServiceEngineImpl.java:315)+
    +     at com.bea.common.engine.internal.ServiceEngineImpl.lookupService(ServiceEngineImpl.java:257)+
    +     at com.bea.common.engine.internal.ServicesImpl.getService(ServicesImpl.java:72)+
    +     at weblogic.security.service.internal.WLSIdentityServiceImpl.initialize(WLSIdentityServiceImpl.java:47)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initializeServiceEngine(CSSWLSDelegateImpl.java:300)+
    +     at weblogic.security.service.CSSWLSDelegateImpl.initialize(CSSWLSDelegateImpl.java:221)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.InitializeServiceEngine(CommonSecurityServiceManagerDelegateImpl.java:1783)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealm(CommonSecurityServiceManagerDelegateImpl.java:442)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.loadRealm(CommonSecurityServiceManagerDelegateImpl.java:840)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initializeRealms(CommonSecurityServiceManagerDelegateImpl.java:869)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1028)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:141)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
    Caused by: java.lang.ClassNotFoundException: com.pointbase.jdbc.jdbcUniversalDriver
    +     at java.lang.Class.forName0(Native Method)+
    +     at java.lang.Class.forName(Class.java:169)+
    +     at org.apache.openjpa.jdbc.schema.DataSourceFactory.newDataSource(DataSourceFactory.java:85)+
    +     ... 38 more+
    +     at org.apache.openjpa.lib.conf.ConfigurationImpl.instantiateAll(ConfigurationImpl.java:302)+
    +     at org.apache.openjpa.conf.OpenJPAConfigurationImpl.instantiateAll(OpenJPAConfigurationImpl.java:1409)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.makeReadOnly(AbstractBrokerFactory.java:646)+
    +     at org.apache.openjpa.kernel.AbstractBrokerFactory.pool(AbstractBrokerFactory.java:131)+
    +     at kodo.jdbc.kernel.KodoJDBCBrokerFactory.getInstance(KodoJDBCBrokerFactory.java:43)+
    +     Truncated. see log file for complete stacktrace+
    +>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <Security> <BEA-090082> <Security initializing using security realm myrealm.>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Critical> <WebLogicServer> <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:916)+
    +     at weblogic.security.service.CommonSecurityServiceManagerDelegateImpl.initialize(CommonSecurityServiceManagerDelegateImpl.java:1050)+
    +     at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:875)+
    +     at weblogic.security.SecurityService.start(SecurityService.java:141)+
    +     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)+
    +     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)+
    +     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)+
    +>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>+
    +<Sep 9, 2010 11:45:17 PM EDT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>+
    +<Sep 9, 2010 11:45:17 PM> <FINEST> <NodeManager> <Waiting for the process to die: 16443>+
    +<Sep 9, 2010 11:45:17 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>+
    +<Sep 9, 2010 11:45:18 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>+
    ps:
    I've come your weblog and found alot of tips for debugging WebLogic Server exceptions. It's really helpful. Thanks.
    Edited by: Doubt_Man on Sep 10, 2010 10:49 AM
    Edited by: Doubt_Man on Sep 10, 2010 3:54 PM

  • 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

  • Problem in starting Managed Servers

    I am getting probelm in starting managed servers in WL 6.0,i tried with giving
    password while starting
    [wlerror.txt]

    I think your port number are conflicting.
    Check your port number for both the server
    "Shridhar" <[email protected]> wrote:
    >
    >
    >
    I am getting probelm in starting managed servers in WL 6.0,i tried with
    giving
    password while starting

  • 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

  • Multicast Error When Starting Managed Servers

    Environment: HP-UX 11i, Weblogic 8.1 SP1.
              We're getting the following error when we start managed servers in our clustered environment:
              <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
              37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
              java.net.SocketException: Can't assign requested address
              at java.net.PlainDatagramSocketImpl.join(Native Method)
              at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
              at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
              at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
              at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
              at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
              at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
              at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
              at weblogic.Server.main(Server.java:32)
              >
              We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
              1) Different multicast addresses/ports;
              2) The util.multicastTest app.
              3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
              Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
              Thanks in advance for any help...
              Brian
              

    Environment: HP-UX 11i, Weblogic 8.1 SP1.
              We're getting the following error when we start managed servers in our clustered environment:
              <Feb 24, 2004 6:33:12 PM CST> <Error> <Cluster> <BEA-000116> <Failed to join cluster PDICluster at address 2
              37.0.0.1 due to: java.net.SocketException: Can't assign requested address.
              java.net.SocketException: Can't assign requested address
              at java.net.PlainDatagramSocketImpl.join(Native Method)
              at java.net.PlainDatagramSocketImpl.join(PlainDatagramSocketImpl.java:134)
              at java.net.MulticastSocket.joinGroup(MulticastSocket.java:274)
              at weblogic.cluster.FragmentSocket.initializeMulticastSocket(FragmentSocket.java:92)
              at weblogic.cluster.FragmentSocket.start(FragmentSocket.java:109)
              at weblogic.cluster.MulticastManager.startListening(MulticastManager.java:164)
              at weblogic.cluster.ClusterCommunicationService.initialize(ClusterCommunicationService.java:52)
              at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:922)
              at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
              at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
              at weblogic.Server.main(Server.java:32)
              >
              We also get the same error when we try the util.multicastTest application. So far, we've done the following things to troubleshoot this:
              1) Different multicast addresses/ports;
              2) The util.multicastTest app.
              3) We're researching whether or machine or network may be causing this, but since the admin. server and managed servers are running on the same server, I don't see how the network could be causing this.
              Can anyone give me any ideas as to what might be going wrong? We've set this up on other machines before with the same OS and same version of Weblogic. So I'm at a loss at the moment as to what might be going wrong.
              Thanks in advance for any help...
              Brian
              

  • Adding patch jar file while starting Managed Server through Node Manager

    Hi,
    I am using Weblogic Express 10.0 on Linux env, Jrockit JVM.
    I have a patch jar file from BEA, I added it to Weblogic start script, when I start the Managed server by using startManagedWeblogic.sh script, I can see that patch jar file is added to classpath when I grep for Java process.(ps -ef | grep -i java).
    But when I start the Managed server through NodeManager and grep for java process, I dont see the patch jar file added to classpath of Managed server process which is started.
    Can someone let me know if I have to add the patch jar file somewhere else along with Weblogic start script if starting Managed server through Node Manager?
    Weblogic Consultant

    Thanks for your response.
    I found another way to do this.
    Edit nodemanager.properties file and set StartScriptEnabled=true (By default it is false), and then restart the Node Manager process.
    Enabling this setting to true will enable the NodeManager process to use startManagedWeblogic.sh script while starting the managed server, all the added jar files, memory settings will be taken from start script of Weblogic
    Weblogic Consultant

  • 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

  • Node Manager starting managed servers under different users

    Hi all,
    I have multiple domains running on the same server.
    Is it possible to get node manager to start managed servers from different domains under different users?
    Default is the user under which node manager was started originally.
    Thanks
    Arnaud

    Oracle documentation is still in confussion state for Unix platform nodemanager.
    NodeManager Admin Guide had chapter 3 for General configuration of nodemanger. Chapter 5 is for script based nodemanager.
    In chapter 5 there is clear way defined for " Starting a node manger for Unix machine".
    chapter 3 is mess there is clear-cut direction to reach the remote startup of servers.
    Why we have so many types of nodemanager for connect. howbout start them?
    Can someone expert in Oracle WebLogic please respond to this.
    *Nodemanagers are NOT meant for multiuser development env.
    They are defined for production env and for HA, FailOver.*
    Edited by: PavanBhavanishekhar on Jan 6, 2010 9:10 PM

  • Unable to start SOA server through Node Manager

    Hi All,
    I am trying to install AIA 11.1.1.6.0 on the top of SOA Suite 11.1.1.6.0.
    I was able to install successfully the weblogic server, rcu, soa and osb servers. Now, before installing the AIA, the document i am following it says, make sure to start the soa server through the node manager.
    Now i start the admin server, then the node manager, to make sure i have checked that the node manager is up, i logged in to the weblogic console, went to Machines, and i can see that it is up and reachable.
    Now using the WLST commands, first i connected to the node manager using command nmConnect(), then i am trying to start the soa server through node manager using the command start('soa_server1') command.
    I am getting an error while trying to start soa server with nmStart() command, below is the error message...
    "Error starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'"
    I executed the dumpStack() command, and i am getting the output as "No stack trace available"
    If i am able to start the soa server through the node manager, i can go ahead and install the AIA pack but this is not letting me go forward.
    I also tried to start the soa server through the weblogic console., go to servers tab, select the soa_server1 and start, the soa server state is going to "FAILED_NOT_RESTARTABLE".
    I followed some of the blogs like...
    http://neeraj-soa-tips.blogspot.com/2010/06/starting-admin-and-managed-servers.html
    http://www.javamonamour.org/2011/09/nmconnect-nmstart-nmkill.html
    Experts, please give your advice.
    Many Thanks,
    N

    Hi Narsing,
    I'm assuming that you've followed the required Pre-config steps. If it is not working, I'd suggest to start the Admin and SOA server without node manager first. Then start your node manager and see if it is reachable from the WLS console. Then shut down your SOA server from command prompt and restart your SOA server from WLS console.
    Verify the Listen Address of your Node Manager and start your node manager from command prompt by explicitly specifying the same address and port.
    As WLS console internally uses node manager only to start your server, you would not need to use WLST scripts to do the same and only SOA server needs to be started using node manager.
    Regards,
    Neeraj Sehgal
    Hi Neeraj,
    I made sure that in the weblogic console, in the machines tab, local machine-->configuration--->Node Manager, I have given the correct Listen Address (Narsing-PC) and the listen port 5556.
    I have made sure the property StartScriptEnabled= true.
    I have started the admin server through startWebLogic.cmd command, now i start the node manager by going to the C:\Oracle\Middleware\wlserver_10.3\server\bin and running the command startNodeManager.cmd, then i go to the weblogic console--->servers--->control--->soa_server1--->start , it is going to      FAILED_NOT_RESTARTABLE status.
    If i see the log messages in the nodemanager.log, this is the below message...
    <Jun 28, 2012 11:25:09 PM> <INFO> <soa_domain> <soa_server1> <Server output log file is 'C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\logs\soa_server1.out'>
    <Jun 28, 2012 11:25:11 PM> <INFO> <soa_domain> <soa_server1> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <WARNING> <Exception while starting server 'soa_server1'>
    java.io.IOException: Server failed to start up. See server output log for more details.
         at weblogic.nodemanager.server.AbstractServerManager.start(AbstractServerManager.java:196)
         at weblogic.nodemanager.server.ServerManager.start(ServerManager.java:23)
         at weblogic.nodemanager.server.Handler.handleStart(Handler.java:609)
         at weblogic.nodemanager.server.Handler.handleCommand(Handler.java:121)
         at weblogic.nodemanager.server.Handler.run(Handler.java:71)
         at java.lang.Thread.run(Thread.java:662)
    The log message in the soa_server1.out file is as below...
    Starting WLS with line:
    C:\Oracle\MIDDLE~1\JDK160~1\bin\java -client -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=8453,server=y,suspend=n -Djava.compiler=NONE -Xms512m -Xmx1024m -XX:PermSize=128m -XX:MaxPermSize=512m -Dweblogic.Name=soa_server1 -Djava.security.policy=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\weblogic.policy -Dweblogic.system.BootIdentityFile=C:\Oracle\Middleware\user_projects\domains\soa_domain\servers\soa_server1\data\nodemanager\boot.properties -Dweblogic.nodemanager.ServiceEnabled=true -Dweblogic.security.SSL.ignoreHostnameVerification=false -Dweblogic.ReverseDNSAllowed=false -Xverify:none -da:org.apache.xmlbeans... -ea -da:com.bea... -da:javelin... -da:weblogic... -ea:com.bea.wli... -ea:com.bea.broker... -ea:com.bea.sbconsole... -Dplatform.home=C:\Oracle\MIDDLE~1\WLSERV~1.3 -Dwls.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dweblogic.home=C:\Oracle\MIDDLE~1\WLSERV~1.3\server -Dcommon.components.home=C:\Oracle\MIDDLE~1\ORACLE~1 -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Djrockit.optfile=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.jrf_11.1.1\jrocket_optfile.txt -Doracle.server.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\servers\soa_server1 -Doracle.domain.config.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1 -Digf.arisidbeans.carmlloc=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\carml -Digf.arisidstack.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\FMWCON~1\arisidprovider -Doracle.security.jps.config=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\config\fmwconfig\jps-config.xml -Doracle.deployed.app.dir=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1\servers\soa_server1\tmp\_WL_user -Doracle.deployed.app.ext=\- -Dweblogic.alternateTypesDirectory=C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.ossoiap_11.1.1,C:\Oracle\MIDDLE~1\ORACLE~1\modules\oracle.oamprovider_11.1.1 -Djava.protocol.handler.pkgs=oracle.mds.net.protocol"|"oracle.fabric.common.classloaderurl.handler"|"oracle.fabric.common.uddiurl.handler"|"oracle.bpm.io.fs.protocol -Dweblogic.jdbc.remoteEnabled=false -Doracle.security.jps.policy.migration.validate.principal=false -da:org.apache.xmlbeans... -Dbpm.enabled=true -Dsoa.archives.dir=C:\Oracle\Middleware\Oracle_SOA1\soa -Dsoa.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dsoa.instance.home=C:\Oracle\MIDDLE~1\USER_P~1\domains\SOA_DO~1 -Dtangosol.coherence.clusteraddress=227.7.7.9 -Dtangosol.coherence.clusterport=9778 -Dtangosol.coherence.log=jdk -Djavax.xml.soap.MessageFactory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=C:\Oracle\MIDDLE~1\WLSERV~1.3\server\lib\DemoTrust.jks -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true -Dbam.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dums.oracle.home=C:\Oracle\Middleware\Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://localhost:7001 -Dwlw.iterativeDev= -Dwlw.testConsole= -Dwlw.logErrorsToConsole= -Dweblogic.ext.dirs=C:\Oracle\MIDDLE~1\patch_wls1036\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_oepe180\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_ocp371\profiles\default\sysext_manifest_classpath;C:\Oracle\MIDDLE~1\patch_adfr1111\profiles\default\sysext_manifest_classpath weblogic.Server
    FATAL ERROR in native method: JDWP No transports initialized, jvmtiError=AGENT_ERROR_TRANSPORT_INIT(197)
    ERROR: transport error 202: bind failed: Address already in use
    ERROR: JDWP Transport dt_socket failed to initialize, TRANSPORT_INIT(510)
    JDWP exit error AGENT_ERROR_TRANSPORT_INIT(197): No transports initialized [../../../src/share/back/debugInit.c:690]
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <Waiting for the process to die: 4808>
    <Jun 28, 2012 11:25:11 PM> <INFO> <NodeManager> <Server failed during startup so will not be restarted>
    <Jun 28, 2012 11:25:11 PM> <FINEST> <NodeManager> <runMonitor returned, setting finished=true and notifying waiters>
    Someone please help, if i am able to start the soa manged server, i can go ahead and install the AIA Foundation pack...
    Many Thanks.

  • In Admin Console We are unable to start Managed Server.

    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">
    [INFO ][memory ] GC mode: Garbage collection optimized for throughput, initial strategy: Generational Parallel Mark & Sweep
    [INFO ][memory ] heap size: 1228800K, maximal heap size: 1228800K, nursery size: 614400K
    [INFO ][memory ] <s>-<end>: GC <before>K-><after>K (<heap>K), <pause> ms
    [INFO ][memory ] <s/start> - start time of collection (seconds since jvm start)
    [INFO ][memory ] <end> - end time of collection (seconds since jvm start)
    [INFO ][memory ] <before> - memory used by objects before collection (KB)
    [INFO ][memory ] <after> - memory used by objects after collection (KB)
    [INFO ][memory ] <heap> - size of heap after collection (KB)
    [INFO ][memory ] <pause> - total sum of pauses during collection (milliseconds)
    [INFO ][memory ] run with -Xverbose:gcpause to see individual pauses
    [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 weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
    <06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the password attribute value of {AES}WSsjiXk6ppStq4WFajxaXkqCwpcBwaMJni7vk/pqXvk= 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 weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
    Enter username to boot WebLogic server:<06-May-2010 12:07:00 o'clock BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.1.0 Thu Jun 11 00:26:56 EDT 2009 1227385 >
    <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 following servers {AdminServer}.>
    <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 scripts its working fine.
    [twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    wls:/offline> nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
    Connecting to Node Manager ...
    Successfully Connected to Node Manager.
    wls:/nm/twp_domain> nmStart('twpserver1')
    Starting server twpserver1 ...
    Successfully started server twpserver1 ...
    Please provide the solution, how to solve this issue.
    Thanks
    SRK

    In my question some content was strike.... now again i updated...pls see now...
    Server logs
    <06-May-2010 12:06:57> <Info> <NodeManager> <Server output log file is "/appl/weblogic/scripts/servers/twpserver1/logs/twpserver1.out">
    [INFO ][memory ] GC mode: Garbage collection optimized for throughput, initial strategy: Generational Parallel Mark & Sweep
    [INFO ][memory ] heap size: 1228800K, maximal heap size: 1228800K, nursery size: 614400K
    [INFO ][memory ] <s>-<end>: GC <before>K-><after>K (<heap>K), <pause> ms
    [INFO ][memory ] <s/start> - start time of collection (seconds since jvm start)
    [INFO ][memory ] <end> - end time of collection (seconds since jvm start)
    [INFO ][memory ] <before> - memory used by objects before collection (KB)
    [INFO ][memory ] <after> - memory used by objects after collection (KB)
    [INFO ][memory ] <heap> - size of heap after collection (KB)
    [INFO ][memory ] <pause> - total sum of pauses during collection (milliseconds)
    [INFO ][memory ] run with -Xverbose:gcpause to see individual pauses
    [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 weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
    <06-May-2010 12:07:00 o'clock BST> <Critical> <Security> <BEA-090518> <Could not decrypt the password attribute value of {AES}WSsjiXk6ppStq4WFajxaXkqCwpcBwaMJni7vk/pqXvk= 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 weblogic.security.internal.encryption.EncryptionServiceException: com.rsa.jsafe.JSAFE_PaddingException: Could not perform unpadding: invalid pad byte..>
    Enter username to boot WebLogic server:<06-May-2010 12:07:00 o'clock BST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.1.0 Thu Jun 11 00:26:56 EDT 2009 1227385 >
    <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 following servers {AdminServer}.>
    <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 scripts its working fine.
    [twpuser@ukirt156 /appl/weblogic/scripts]$ java weblogic.WLST
    Initializing WebLogic Scripting Tool (WLST) ...
    Welcome to WebLogic Server Administration Scripting Shell
    Type help() for help on available commands
    wls:/offline> nmConnect('weblogic', 'w3bl0g1c', 'ukirt156', '5556', 'twp_domain', '/appl/weblogic/oracle/middleware/user_projects/domains/twp_domain', 'plain')
    Connecting to Node Manager ...
    Successfully Connected to Node Manager.
    wls:/nm/twp_domain> nmStart('twpserver1')
    Starting server twpserver1 ...
    Successfully started server twpserver1 ...
    Please provide the solution, how to solve this issue.
    Thanks
    SRK

  • Problem Starting Managed Servers

    Hi,
    I am trying to start Managed Server on Sun Solaris. My admin Server and managed Server
    are on the same Machine.
    My admin Server starts up with out any problem. WhenI try to bring up my Managed
    Server its not reading the command line arguments which I supplied through the Console:
    Servers -> serverName -> Remote Start->Arguments. For some reason these command arguments
    are not read and so I am having errors like Unable to load libraries, etc.
    Also when I saw the log file for managed server the class path and the arguments
    are printed in a different way than I have set. I dont know if thats a problem or
    not. I am copying part of that for your reference.
    classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblogic6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
    serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.security.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
    I have checked the config.xml file and what ever I have set in the console is being
    saved properly in the xml file.
    Can any one know why the back slash is printed above even though I havent typed that
    in the console. Has any one have experince with setting the command line arguments
    and class path through console for Managed servers.
    I am stuck up at this point. Any help in this regard will be greatly appreciated.
    Thanks,
    Kiran

    Seems a method signature does not match with the implementation in the
    library either due to namemangling or incompatible versions of libraries.
    You are loading your own custom native libraries for security.
    Best would be use the default startManagedServer -- once the server has
    started, copy and paste the entire value of java.library.path into the
    startup arguments for Remote start.
    For instance in my server log file:
    ####<Apr 10, 2002 6:47:10 PM PDT> <Info> <Management> <mountview> <myserver>
    <main> <system> <> <141034> <Java system property: java.library.path =
    /home/sabha/600sp2only/jdk130/jre/bin/../lib/sparc/hotspot:/home/sabha/600sp
    2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlserver6.0/lib/so
    laris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/usr/lib>
    I would set that as the arguments :
    -Djava.library.path=/home/sabha/600sp2only/jdk130/jre/lib/sparc/hotspot:/hom
    e/sabha/600sp2only/jdk130/jre/bin/../lib/sparc::/home/sabha/600sp2only/wlser
    ver6.0/lib/solaris:/home/sabha/600sp2only/wlserver6.0/lib/solaris/oci816_8:/
    usr/lib
    If this does not work, then java for some reason is not taking library paths
    set as java.library.path and I dont know how to set LD_LIBRARY_PATH as part
    of arguments to java. Another thing is before starting the NodeManager, set
    the LD_LIBRARY_PATH to point the library directories and see if this helps.
    regards,
    Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    >
    Sabha,
    I am trying to start the managed server via remote start. After readingyour reply
    I have cleaned up the argument list for remote start. Now I am gettingaltogether
    a different error.(Surpsisingly I was able to start the managed serversusing srartManagedServer.sh.
    I dont know why I am having trouble to do the same through the remotestart).
    >
    I am getting a unsatisfied link error. In your reply you have asked me toadd -Djava.library.path
    to the argument liist which I did. Below you can find the exact error Ihave got:
    >
    >
    The WebLogic Server did not start up properly.
    Exception raised:
    java.lang.UnsatisfiedLinkError:/export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:
    ld.so.1: /usr/bin/../java/bin/../bin/sparc/native_threads/java: fatal:relocation
    error: file /export/home/spbbprf1/Servers/v25_0/bb/pub/libinterface.so:symbol Opsys_oneWayCryptCmpApi:
    referenced symbol not found
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1382)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1306)
    at java.lang.Runtime.loadLibrary0(Runtime.java:749)
    at java.lang.System.loadLibrary(System.java:820)
    atamdocs.APILink.accesscontrol.sum.EncryptApi.<clinit>(EncryptApi.java:20)
    atamdocs.APILink.accesscontrol.sum.UserJoltBackend.<clinit>(UserJoltBackend.ja
    va:52)
    >
    atamdocs.APILink.accesscontrol.sum.SumManagerImpl.<init>(SumManagerImpl.java:5
    9)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    atamdocs.uamsimpl.server.storage.multi.MultiManagerImpl.<init>(MultiManagerImp
    l.java:208)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    atamdocs.uamsimpl.server.storage.cache.CachingManagerImpl.<init>(CachingManage
    rImpl.java:81)
    >
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at amdocs.uams.UamsSystem.getUamsManager(UamsSystem.java:156)
    atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:61)
    atamdocs.uamsimpl.server.ejb.wl6.WLUamsDelegate.<init>(WLUamsDelegate.java:55)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at amdocs.uamsimpl.server.ejb.wl6.WLUamsRealm.<init>(WLUamsRealm.java:42)
    at java.lang.Class.newInstance0(Native Method)
    at java.lang.Class.newInstance(Class.java:237)
    at weblogic.security.acl.Realm.getRealm(Realm.java:84)
    at weblogic.security.acl.Realm.getRealm(Realm.java:62)
    atweblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
    at weblogic.security.SecurityService.initialize(SecurityService.java:115)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:402)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
    at weblogic.Server.main(Server.java:35)
    Reason: Fatal initialization exception
    >
    >
    Please let me know if you need more description.
    Thanks,
    Kiran
    "Sabha" <[email protected]> wrote:
    Either you are attempting to start a managed server through its
    NodeManager
    for which the remote startup arguments are not correct or something else
    is
    wrong. How are you starting the server? The remote start is only when you
    want to start the server through NodeManager and not for normalinvocation
    of the startManagedServer script.
    Does the server really start? can you paste the startup arguments for the
    remote start of the managed server as saved in the config.xml.
    What is the log generated when the managed server is startedup.
    -Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    Sabha,
    The main problem is:
    What ever I am trying to give in the command line arguments through theConsole:
    Servers -> serverName -> Remote Start->Arguments.
    is not being read during managed server start up.
    I have all the libraries defined defined in java.lib.path. I dont knowwhy
    its not
    being read by managed server during start up. Am I missing something.
    -Kiran
    "Sabha" <[email protected]> wrote:
    If its unable to load the performance packs, try setting
    java.library.path
    to the solaris lib directories. /usr/lib, /home/oracle/lib paths -- oryou
    can just copy what is in the admin weblogic.log file for the
    java.library.path (make sure the paths are correct and applicable forthe
    maanged server box also) and pass that as an argument as
    in -Djava.library.path=/usr/lib:/bea/wlserver6.1/lib/solaris...
    -Sabha
    "Kiran" <[email protected]> wrote in message
    news:[email protected]...
    Hi,
    I am trying to start Managed Server on Sun Solaris. My admin Server
    and
    managed Server
    are on the same Machine.
    My admin Server starts up with out any problem. WhenI try to bring
    up
    my
    Managed
    Server its not reading the command line arguments which I supplied
    through
    the Console:
    Servers -> serverName -> Remote Start->Arguments. For some reason
    these
    command arguments
    are not read and so I am having errors like Unable to load
    libraries,
    etc.
    Also when I saw the log file for managed server the class path and
    the
    arguments
    are printed in a different way than I have set. I dont know if thats
    a
    problem or
    not. I am copying part of that for your reference.
    classpath=/opt/j2sdk1_3_1_01/jre/lib/rt.jar\:/opt/weblogic6.1\:/opt/weblog
    i
    c
    6.1/lib/weblogic_sp.jar\:/opt/weblogic6.1/lib/weblogic.jar\
    serverStartArgs=-Dweblogic.management.server\=sunserver\:7210 -Djava.secur
    i
    t
    y.policy\=\=/opt/weblogic6.1/lib/weblogic.policy
    I have checked the config.xml file and what ever I have set in the
    console
    is being
    saved properly in the xml file.
    Can any one know why the back slash is printed above even though I
    havent
    typed that
    in the console. Has any one have experince with setting the command
    line
    arguments
    and class path through console for Managed servers.
    I am stuck up at this point. Any help in this regard will be greatlyappreciated.
    Thanks,
    Kiran

  • How to start managed servers in parallel?

    Hello everyone,
    I am developing a wlst script that would start all managed servers on a particular machine (machine_name should be provided) from the admin server side. The script works fine. However, since there were some domains that have 25+ managed servers for a single machine, it takes some time to start all of them in sequence. Is there a way to trigger a start command for each of the managed servers that I need to start just like what the node manager does when i start them through admin console? Something like triggering parallel processes running on background. Here is my code snippet:
                    #It focuses only on all managed servers defined within the listen address provided
                    if (server_listenaddress == managed_server) and (server_name != admin_name):
                            if (execute_command == "start"):
                                    print 'About to start',server_name,'on',server_listenaddress,'...'
                                    print
                                    try:
                                            start(server_name)
                                            print
                                            state(server_name,'Server')
                                            print
                                            nmDisconnect()
                                    except WLSTException:
                                            print 'Server instance',server_name,'could not be started. Skipping this server..'
                                            print
                                            state(server_name,'Server')
                            else:
                                    print 'About to stop',server_name,'on',server_listenaddress,'...'
                                    print
                                    try:
                                            shutdown(server_name,force='true')
                                            print
                                            state(server_name,'Server')
                                            print
                                    except WLSTException:
                                            print 'Server instance',server_name,'could not be stopped. Skipping this server..'
                                            print
                                            state(server_name,'Server')
                    elif (server_name == admin_name):
                            #It skips to restart the admin server since this script it only to restart managed servers.
                            print 'Server',server_name,'is the admin server. Skipping...'
                            print
                    else:
                            print 'Managed server',server_name,'is not configured with',managed_server,'listen address. Skipping this server..'
    Thanks in advance for all your help!!
    regards,
    Rustan

    Works perfectly, thanks!!!
    In summary, I just modified this line:
    start(server_name)
    and changed it to:
    start(server_name, block='false')
    In Admin Console, it is set to false but in WLST, it is defaulted to true so we need to explicitly set it to false.
    "Oracle Fusion Middleware Oracle WebLogic Scripting Tool, block is always set to true."

Maybe you are looking for

  • After updates i am unable to open firefox and have to reset comp to earlier date, my comp is new please help?

    i get a prompt to update firefox and i do then when i try to start firefox i am unable to. i have back-up my computer to previous date and the uninstall and re-install firefox to find the same prompt for updates from firefox and i cant ignore it so i

  • What Is, And Why do I need it: ExpressCard/34 Slot?

    In the very near future I will be obtaining a 17" MBP. That's just savvy, except for one minor detail. What is an ExpressCard/34 slot, why do I need one, why would it have been included in this particular size MBP and what can I shove in there?

  • SBS 2011 stops responding

    Two days in a row now one of my clients has come into the office to find that their SBS2011 is no longer responding to requests, and logon times take between 15 and 30 minutes before reaching a usable desktop. The SBS2011 server is a guest VM on a Wi

  • I can't use my scanner in Elements 12

    I am unable to use my scanner with Elements 12.  I moved the Twain plug in from the Optional Plug-in folder to the Plug-in folder but no luck  Not in editor or organizer

  • How to use Vectors ?????????

    Hi guys, i am a newbie in java and about to die due to some stressful assignments. I am not asking u to help in assignment. Just please share some knowledges about vector. How to use it? so that i can use it in my assignment. Thank u . AND IN THIS CO