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

Similar Messages

  • 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

  • Unable to start Managed servers from admin console

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

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

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

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

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

  • 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
              

  • 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

  • Problem while starting Managed Servers from Admin Server console

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

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

  • Problem starting managed server.

    Hi,
    I have my weblogic server running on UNIX server which has 2 users (UserA and UserB). The Admin server has been started with UserA and the nodemanager with UserB. I have 3 clusters with 2 managed servers each configured in my server. When i start my managed servers from my console 2 clusters (i.e. 4 managed servers have started) but only 1 cluster failed to start throwing the following error.
    <Sep 26, 2009 8:41:29 AM GMT> <Error> <Security> <BEA-090033> <Failed to Switch to User UserA java.lang.IllegalArgumentException: Cannot seteuid("UserA"), system error: 'Not owner'
    at weblogic.platform.Unix.setEUser0(Native Method)
    at weblogic.platform.Unix.setEffectiveUser(Unix.java:49)
    at weblogic.t3.srvr.SetUIDManager.switchEffectiveUser(SetUIDManager.java:178)
    at weblogic.t3.srvr.SetUIDManager.makeUnprivileged(SetUIDManager.java:104)
    at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:777)
    at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:669)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:343)
    at weblogic.Server.main(Server.java:32)
    .>
    Kindly help me with this issue. i wonder why only 1 cluster failed?
    Thanks,
    Tom
    Edited by: user11949331 on Sep 28, 2009 4:24 AM

    Manish, Thanks for your response.
    The issue is resolved. The problem seems to be with the privilege.
    Whenever i start the Managed server the owner of the Managed server's directory is "UserB" whereas all other files and directories in the domain dir have "UserA" as owner.
    So i changed the owner of all the files and dir in the domain directory to "UserA" and tried starting the managed server from command line and it worked.
    Thanks,
    Tom.

  • While starting managed servers asks for password of localhost

    We have a clustered environment and we are using Virtual IPs for the Managed servers. The managed servers in the forst node is not starting.
    The problem I have narrowed down is that there are startup.properties file for the managed servers.
    It has argument like -Dtangosol.coherence.localhost\=xgsoapd5v1.ea.com (for SOA1)
    While SOA1 it is asking for password for the above host and the managed server is not starting.
    Now SOA2 has the similar argument -Dtangosol.coherence.localhost\=xgsoapd5v2.ea.com (for SOA2), but it is not asking for any password and so the SOA2 managed server is sta! rting.
    Similarly the while starting BAM1 it is asking for a password , but for BAM2 it is not asking for password and it is starting.
    I could not yet figure out why it is behaving differently in the first node.
    This is a copy of production with a chnage in the network. That means only the IP addresses are changed. xgsoapd5v1.ea.com and xgsoapd5v2.ea.com are the hostnames
    It works perfectly in production environment.

    Hi
    Under your domain root folder say in the main machine where you have the AdminServer, you should have a folder structure something like this:
    ../user_projects/domains/yourBPMDomain1/servers. Under the servers folder you can see list of each server. On the main machine you will see one AdminServer folder. Under this there should be a sub-folder named security with one file named boot.properties. This boot.properties file will have encrypted username and password for the weblogic domain.
    If this security/boot.properties exist under the each server folder, then when you start the managed server, it will NOT prompt for the username/password. If it DO NOT exist, it will ask for the credentials.
    Solution is go to each Machine where you the ManagedServers (SOA Server or BAM Server does not matter). Go to each server and under that create a folder named security and create a file named boot.properties and in this file enter plain text username and password something like this and save the file. Now restart all those servers.
    username=domainadminusername
    password=doaminadminpassword
    When you start the servers, server should start taking the above information. AND server will automatically ENCRYPT the above plain text data into hash codes.
    In a nut shell, go to each Server folder across all the remote machines and under that particular managed server create a folder security with one file boot.properties.
    Exmaple locations:
    On Machine1 - user_projects/domains/bpmDomain1/servers/soa_server1/security/boot.properties
    On Machine2 - user_projects/domains/bpmDomain1/servers/bam_server1/security/boot.properties
    You DO NEED the admin username and password in plain text for one time to put in boot.properties. Later on it will get encrypted, so there is no threat for any security loop holes.
    Thanks
    Ravi Jegga

  • How to start managed servers simultaneously using WLST?

    Hi folks,
    I am trying to write a simple script to provide a simple way to bounce my env, I am pretty much done. However, my script now starts (and stops) the managed servers sequentially which is not what I wanted.
    I am wondering if there is a way to start (and stop) the managed servers within a domain in parallel as I can definitely do that using Admin Console.
    I do have an idea in mind:
    Write a simple python script to start/stop a single managed server, then use another shell script to trigger the python script in background mode.
    But I think this approach is really ugly, and am wondering if there is a native way to do that in WLST.
    Thanks for your repose in advance.

    This does not solve my problem, what I am trying to do is to being a an indefinite about of managed servers at the same time, not all the managed servers.
    For example, suppose I have 5 clusters in a domain, and there are 3 servers in each cluster. I might want to bring up all the major servers first at the same time,
    which mean to bring up one server in each cluster at the same time.
    Please help.

  • Error while starting managed servers in a cluster

    Hi,
              I have Weblogic 8.1.3 deployed on my system. We've have a Ant script that set's up the project domain etc. We have an admin server and two other managed servers which are part of a cluster. I am able to start the admin server and access the admin console without any errors. However when I start any of the managed servers in the cluster, using the following command (startManagedWebLogic.cmd Reactor-1 http://localhost:80 OR startManagedWebLogic.cmd Reactor-2 http://localhost:80)
              I get the error listed below. The same Ant script was used to setup the project on another system and it worked but I haven't been able to set it up on my system.
              The error says that it could be due to servers having duplicate names in the cluster but thats not the case here, the managed servers are named Reactor-1 and 2.
              Also, the IP address being accessed, 192.168.141.50:81 is not my system, its another system on the network. I've done a full text search for the IP address but I've not been able to find it in ANY file under c:\bea.
              Can someone please tell me if I've missed something? I'd appreciated any help with this.
              Thanks
              Ameeth
              <Mar 21, 2005 4:52:43 PM GMT+05:30> <Notice> <Cluster> <BEA-000142> <Trying to download cluster JNDI tree from server Reactor-1
              .>
              <Mar 21, 2005 4:52:44 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 81.>
              <Mar 21, 2005 4:52:44 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
              r HTTP from Reactor-1.
              java.net.ConnectException: Tried all: '1' addresses, but could not connect over HTTP to server: '127.0.0.1', port: '81'
              at weblogic.net.http.HttpClient.openServer(Ljava.lang.String;I)V(HttpClient.java:275)
              at weblogic.net.http.HttpClient.openServer()V(HttpClient.java:329)
              at weblogic.net.http.HttpClient.<init>(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSoc
              ketFactory;I)V(HttpClient.java:128)
              at weblogic.net.http.HttpClient.New(Ljava.net.URL;Lweblogic.security.SSL.SSLClientInfo;Lweblogic.security.SSL.SSLSocket
              Factory;I)Lweblogic.net.http.HttpClient;(HttpClient.java:196)
              at weblogic.net.http.HttpURLConnection.connect()V(HttpURLConnection.java:119)
              at weblogic.cluster.MemberManager.waitForSync(J)V(MemberManager.java:213)
              at weblogic.cluster.MemberManager.waitToSyncWithCurrentMembers()V(MemberManager.java:160)
              at weblogic.cluster.ClusterCommunicationService.initialize()V(ClusterCommunicationService.java:58)
              at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:924)
              at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
              at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String)I(T3Srvr.java:344)
              at weblogic.Server.main([Ljava.lang.String)V(Server.java:32)
              >
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090170> <Loading the private key stored under the alias DemoIdenti
              ty from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090171> <Loading the identity certificate stored under the alias D
              emoIdentity from the jks keystore file C:\bea\weblogic81\server\lib\DemoIdentity.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Warning> <WebLogicServer> <BEA-000311> <Attempting to use low strength (exportable) certif
              icates with a full strength (domestic) license.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
              :\bea\weblogic81\server\lib\DemoTrust.jks.>
              <Mar 21, 2005 4:52:47 PM GMT+05:30> <Notice> <Security> <BEA-090169> <Loading trusted certificates from the jks keystore file C
              :\bea\JROCKI~1\jre\lib\security\cacerts.>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "SSLListenThread.Default" listening on port
              7002, ip address 127.0.0.1>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000355> <Thread "ListenThread.Default" listening on port 81,
              ip address 127.0.0.1>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <Cluster> <BEA-000102> <Joining cluster ReactorCluster on 237.0.0.1:7001>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000332> <Started WebLogic Managed Server "Reactor-1" for dom
              ain "ReactorAdminServer" running in Development Mode>
              <Mar 21, 2005 4:52:48 PM GMT+05:30> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
              <Mar 21, 2005 4:52:51 PM GMT+05:30> <Warning> <Net> <BEA-000905> <Could not open connection with host: 127.0.0.1 and port: 82.>
              <Mar 21, 2005 4:52:52 PM GMT+05:30> <Error> <Cluster> <BEA-000141> <TCP/IP socket failure occurred while fetching statedump ove
              r HTTP from 8288749592481618145S:localhost:[81,81,-1,-1,81,-1,-1,0,0]:192.168.141.50:81,192.168.141.50:82:ReactorAdminServer:Re
              actor-1.
              java.io.IOException: Reference to server no longer exists.
              Possible reasons for failure include having servers with duplicate names running on a cluster. Please check your configuratio
              n for this error.
              at weblogic.rmi.cluster.ServerInfoManager.updateServerInfo(Lweblogic.rmi.cluster.ServerInfo)V(ServerInfoManager.java:1
              11)
              at weblogic.rmi.cluster.ServerInfoManager.readUpdate(Ljava.lang.Object)V(ServerInfoManager.java:95)
              at weblogic.cluster.MemberAttributes.readExternal(Ljava.io.ObjectInput)V(MemberAttributes.java:103)
              at java.io.ObjectInputStream.readExternalData(Ljava.io.Externalizable;Ljava.io.ObjectStreamClass)V(Unknown Source)
              at java.io.ObjectInputStream.readOrdinaryObject(Z)Ljava.lang.Object;(Unknown Source)
              at java.io.ObjectInputStream.readObject0(Z)Ljava.lang.Object;(Unknown Source)
              at java.io.ObjectInputStream.readObject()Ljava.lang.Object;(Unknown Source)
              at weblogic.cluster.HTTPExecuteRequest.execute(Lweblogic.kernel.ExecuteThread)V(HTTPExecuteRequest.java:91)
              at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest)V(ExecuteThread.java:219)
              at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
              at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread)V(Unknown Source)

    make sure you use a unique cluster multicast ip address. are you sure that your etc/hosts file has proper entries for localhost?

  • Problem starting managed server in Cluster

    Hi,
    I'm using cluster with 2 managed server. other managed server2 is runing ok in the cluster now when I am starting managed server1 in a cluster this error is coming
    The WebLogic Server encountered a critical failure
    Reason: Assertion violated
    Exception in thread "main" java.lang.NoClassDefFoundError
    at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIdentityManager.java:65)
    at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:170)
    at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(ServerLifeCycleRuntime.java:677)
    at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:406)
    at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:392)
    at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:172)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:373)
    at weblogic.Server.main(Server.java:67)
    Could you pl tell the reason of this error?
    Thanks in advance
    Hi,
    Can anybody help?
    Edited by: user10680571 on Dec 4, 2008 4:42 AM

    Thanks David.
    During starting this managed server in cluster when I do tail -f <log_file_name> I can see this error message. But this message I can't see in log however ending log details- Is this something related with CLASSPATH problem?
    <04-Dec-2008 10:11:18 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <04-Dec-2008 10:11:21 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <04-Dec-2008 10:11:33 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <04-Dec-2008 10:12:06 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <04-Dec-2008 10:12:06 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <04-Dec-2008 10:12:06 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <04-Dec-2008 12:12:26 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <04-Dec-2008 12:12:35 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <04-Dec-2008 12:13:03 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <04-Dec-2008 12:13:56 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <04-Dec-2008 12:13:58 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <04-Dec-2008 12:14:00 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    <05-Dec-2008 06:21:55 o'clock GMT> <Notice> <WebLogicServer> <BEA-000395> <Following extensions directory contents added to t
    he end of the classpath:
    /software/bea/wls/920/weblogic92/platform/lib/p13n/p13n-schemas.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_c
    ommon.jar:/software/bea/wls/920/weblogic92/platform/lib/p13n/p13n_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wl
    p/netuix_common.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/netuix_schemas.jar:/software/bea/wls/920/weblogic92/pla
    tform/lib/wlp/netuix_system.jar:/software/bea/wls/920/weblogic92/platform/lib/wlp/wsrp-common.jar>
    <05-Dec-2008 06:21:57 o'clock GMT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) Serve
    r VM Version 1.5.0_07-b03 from Sun Microsystems Inc.>
    <05-Dec-2008 06:22:04 o'clock GMT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 9.2 Fri Jun 23 20:47:26 EDT 20
    06 783464 >
    <05-Dec-2008 06:22:23 o'clock GMT> <Info> <WebLogicServer> <BEA-000215> <Loaded License : /software/bea/wls/920/license.bea>
    <05-Dec-2008 06:22:23 o'clock GMT> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to STARTING>
    <05-Dec-2008 06:22:23 o'clock GMT> <Info> <WorkManager> <BEA-002900> <Initializing self-tuning thread pool>
    Thanks for your help.....

  • 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

  • IPhone 5, Is there a way to stop screen rotation for specific apps?

    The automatic screen rotation feature is useful - sometimes, and just plain annoying other times.  I prefer to read my e-mail in portrait mode, however the slightest movement or rotation while doing so will cause the screen to rotate (with the phone

  • Display changed/overscan not working after most recent update

    I'm running my mini through an LG 42" plasma TV using a store-bought HDMI to DVI cable, and I had the resolution at 1344x756. After I did the most recent update for what I assume was Leopard 10.5.7, my resolution and colour quality changed. Now with

  • Dnl_cust_prod1 download problem

    Hello, We are doing upgrade project from CRM4 to CRM2007, Our CRM2007 system is a copy of old CRM4 system. We are trying to Redefine replication from ECC6. Initial load of DNL_cust_prod1 is failed with message "Hierarchy ID R3prodhier can be changed

  • Where is the DVD menu?

    Reading from Apples page about Compressor 3.5 new features "Blu-ray disc and DVD burning2 You can now easily burn a Blu-ray disc or a DVD directly from Compressor. Quickly add a menu to your disc by choosing one of the beautiful Apple-designed HD or

  • Templates not updating pages at all

    I have a similar problem to several other posters. I have one template that is attached to about a dozen pages. When I make a change to the template, and then save it, not dialog comes up asking if I want to update the dependent pages, and the change