Managed Servers vs. Admin Server - heap sizes

I have a question. I opened a support ticket with BEA yesterday, the technician got back to me and completely confused the hell out of me.
We're looking to upgrade to WLS10 with an admin server/managed server design. I was under the impression that each server instance, when fired up, starts up in its own JVM with its own memory allocations. If I set the admin server startup script to have a min and max of 1024, the managed server starts up with the same memory settings. The technician I spoke with yesterday from BEA support to clarify this then explains to me that each server instance, admin and managed, do not exist in their own JVMs but that they share the same JVM. I found verbage in the documentation that says the complete opposite...that one server instance can only exist in one JVM...SO if I have the admin server with 1024 and the managed server with 1024 and the machine only has 2 gigs, that's pretty much all I can have running on this machine, right?
The thing I don't understand at all is why would I want the admin server and my application on the managed server to use the same amount of ram? My managed server should have way more ram available to it than the admin server which is rarely used throughout the day. Is there a way to set the admin server to 512 and then fire up the managed server with a gig and a half?
I would think it makes more sense that you specify a different heap size for the admin versus the managed...but maybe not. What is the recommended heap size for the admin server? Is it strictly recommended to let them all use the same heap size settings? Can someone explain why I'd want the admin server to have access to the same amount my heavyweight, client-hit-all-day-long application?
Any help would be greatly appreciated.
Cheers,
rlb

Thanks David. As God as my witness, the tech seriously told me that they all use the same JVM. Then I got seriously confused, like I was an idiot and didn't understand what a JVM was and I started second-guessing myself. The whole conversation was very strange and yes, there was definitely a language barrier and I'm guessing I just wasn't being clear enough...I don't know...all I know is I walked away from the phone call in worse shape then when I first opened the ticket.
At any rate, do you have recommendations for admin server ram? I know there are performance tuning tools to help us figure out the optimum settings for our managed server, and I plan on implementing them...but going back to the ram for the Admin server, versus managed server...is there a recommended way of specifying different heap size for the managed servers? Is the recommended way to set the the -Xms and -Xmx settings via the 'Arguments' field on Environment > Servers > serverName > Configuration > Server Start tab via the admin console?
Thanks again for your quick reply!
Cheers,
rlb

Similar Messages

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

Monitoring Managed servers if Admin server is unavailable in Weblogic

Is it possible to find managed servers state ( example: RUNNING, FAILED, UNKNOWN etc..) if Admin server is unavailable( may be down) in Weblogic.
We can search the state of managed server using keywords in managed server logs. But we don't want to do that.
Is there any other way to find the managed servers state.
Thanks,
Venkat

WLST and connecting to managed servers is one option.
Another one is using a RESTful approach: the one that comes with WLS12c in centrally located on the admin server and therefore not really helpful in your case
You might try OpenSource Jolokia ( Overview ) which is a nifty little tool.
Some more infos about Jolokia and WebLogic:
RESTful WebLogic Monitoring of Servers, Applications, JDBC and JMS with Jolokia — munz & more
best regards!

Browse jms destinations on managed servers (from admin server)

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

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

Clustered enviroments -Starting/Stopping Managed servers, NodeManager & Admin server from single node

Hi,
We have 5 node Weblogic cluster. At the time of some mass activities like patching we have to stop all our managed, Admin Servers and node manager and it takes a lot of time to do this by logging in to all 5 managed servers and stopping all components. Though we have node manager configured so we can stop managed servers from console itself, but still have to login to each server to stop NodeManager and Oracle Http Servers.
Things become worse when wee have to shutdown almost 15-20 instances.
Is there a way (using wlst or shell script) that we can do all these tasks from by logging in to just one server?
Thanks,
Suraj

The simple code below would shutdown all the running Servers. Some of the APIs for ex MBeanHome are deprecated..still work though..if your concerned about that..I am working on the same using JMX API..if you want I could share that too. And also as described in the below link..you can Cluster stop and start using WLST commands. Managing the Server Life Cycle - 12c Release 1 (12.1.1)
<This code is from Oracle Weblogic documentation>
import java.util.Set;
import java.util.Iterator;
import java.rmi.RemoteException;
import javax.naming.Context;
import javax.management.ObjectName;
import java.io.*;
import java.net.*;
import weblogic.jndi.Environment;
import weblogic.management.MBeanHome;
import weblogic.management.WebLogicMBean;
import weblogic.management.configuration.ServerMBean;
import weblogic.management.runtime.ServerRuntimeMBean;
import weblogic.management.runtime.ServerStates;
import weblogic.management.WebLogicObjectName;
public class ServerStopper {
public static void stop() throws Exception {
    MBeanHome home = null;
    //url of the Admin server
    String url = "t3://localhost:7001";
    String username = "weblogic";
    String password = "welcome1";
    ServerRuntimeMBean serverRuntime = null;
    Set mbeanSet = null;
    Iterator mbeanIterator = null;
    try {
      // Set ContextClassloader to prevent assertions
      URL[] urls = { new File("/").toURL() };
      Thread.currentThread().setContextClassLoader(new
         URLClassLoader(urls));
      Environment env = new Environment();
      env.setProviderUrl(url);
      env.setSecurityPrincipal(username);
      env.setSecurityCredentials(password);
      Context ctx = env.getInitialContext();
      home = (MBeanHome)
           ctx.lookup("weblogic.management.adminhome");
      mbeanSet = home.getMBeansByType("ServerRuntime");
      mbeanIterator = mbeanSet.iterator();
      while(mbeanIterator.hasNext()) {
        serverRuntime = (ServerRuntimeMBean)mbeanIterator.next();
        if(serverRuntime.getState().equals(ServerStates.RUNNING)){
            serverRuntime.shutdown();
    } catch (Exception e) {
      e.printStackTrace();

Starting Managed Servers without admin Server

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

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

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>

Node manager or the Admin server - which one to start first?

Hi Experts,
Somewhere i see its this way.
OBIEE 11.1.1.6 | OBIEE
To start the Oracle Business Intelligence system, you start:
the Node Manager(It is by default windows service in Enterprise Installation of OBIEE 11G)
the Administration Server (It is weblogic Admin Server)
the Managed Servers(Comes with Enterprise Installation of OBIEE 11G)
and then you start the system components.(All OBIEE Components : BI Server,Presentation Server,Schedular,Java Host,Cluster Services.
and at other places i see this...
OBIEE 11G - Starting Oracle Business Intelligence | GerardNico.com (BI, OBIEE, OWB, DataWarehouse)
To start the Oracle Business Intelligence system, you start:
the Administration Server
the Node Manager
the Managed Servers,
and then you start the system components.
I have Linux environment and it has just single BI Server and i go like this.
1) startWeblogic.sh script
2) startNodeManager.sh
3) startManagedWeblogic.sh
4) then system components.
Thanks
Ashish

so the way i am starting OBIEE Services currently is basically wrong ie..
1) startWeblogic.sh script
2) startNodeManager.sh
3) startManagedWeblogic.sh
4) then system components.
( by the way everything comes up perfect even if i start the nodemanager after the startWeblogic.sh script)
and i should do it this way..
1)startNodeManager.sh
2)startWeblogic.sh script
3)startManagedWeblogic.sh
4) then system components.
Kindly confirm...

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

SCOM 2012 R2 Management Servers and SQL Server Availability Groups

My team is in the middle of rolling out a brand new install of System Center Operations Manager 2012 R2.
I have set up a SQL Server Availability group that is spread across multiple subnets and installed the initial management server per
here.
As I have gone through attaching new management servers, I have noticed disturbing behavior. When the AG fails over to another node, the management servers will lose connectivity unless I either recycle the service or it fails back to the original
node. This is not a security issue as I have set up permissions. It says it cannot connect to the database anymore at all.
Has anyone else seen this behavior? Is there a setting I am missing somewhere?
Thanks for your help.
Dale

Hi Dale,
What about ApplicationIntent\Readonly?
http://msdn.microsoft.com/en-us/library/hh205662(v=vs.110).aspx
Still thinking about DNS, may be this could be for your case:
http://www.sqlservercentral.com/Forums/Topic1449216-2799-1.aspx
Natalya

How to run OPatch against Node Manager from the admin server

How to run OPatch against Node Manager from the admin server

Hello,
I'm not sure what you meant by Opatch against nodemanager.You can check the below document about how to apply patches using Opatch
Oracle Fusion Middleware Patching with OPatch - 12c (12.1.2)
Refer the section " Common OPatch Commands When Patching an Oracle Fusion Middleware Oracle home"
/MR

Starting managed servers from admin console vs. command line

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

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

Automating start / restart of WebLogic Admin and managed servers on MS Windows

Hi All,
Please help me to do the automation of start and stop scrip of Oracle Weblogic 10.3.6 and Forms and Reports 11.1.2.2.0(Managed Servers) On Windows server 2008.
Here are two options for automating start / stop of WebLogic Admin and managed servers on MS Windows. Please suggesst which one is standrad procedure.
Use NodeManager (installed as a MS Windows Service)
or
Create Windows Service(s) for the server(s) - no NodeManager
Following Document : 1060058.1
Please suggest me the best practice. Many thanks in advance.
Kind Regards,
Mohan

Hi Borys,
Thank you for quick reply...
If we use the first option "Create Windows Service(s) for the server(s) - no NodeManager" then we will be facing issue Like "Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running"
In the document : 1060058.1 : Mentioned as Important Note: The second option has a limitations.
Limitaion is below when we use first option : "Create Windows Service(s) for the server(s) - no NodeManager" -
Windows Services Manager only monitors the JVM process. If the JVM process fails (shuts down), then Windows Services Manager will attempt to restart it. But there are some scenarios where the Admin Server or Managed Server may go into an unhealthy or failed state but the JVM is still running. The Windows Service will not know to restart the process in these cases. If a server is started using NodeManager, NodeManager would recognize such a state and restart the process accordingly. Furthermore, if you start up managed servers via a MS Windows Service, you cannot monitor and/ or stop the managed server via the Weblogic Admin Console and/or Fusion Middleware ( Enterprise Manager ) Control.
I have implemented the second option "Use NodeManager starting admin and manged servers via WLST script" - Python script. Its working well without issue...No Limitation...
Script Contains Below :
print "================== Start scripts of Managed servers and Admin server ======================"
nmConnect(userConfigFile='D:/myFiles/myuserconfigfile.secure',userKeyFile='D:/myFiles/myuserkeyfile.secure',host='00.0.00.00',port='5556',domainName='ClassicDomain',domainDir='D:\Oracle\Middleware\user_projects\domains\ClassicDomain',nmType='ssl')
print "================== Adminserver Starting ================================================"
nmStart('AdminServer')
connect('weblogic','Password1','10.4.93.117:7001')
print "================== MANAGED SERVER (FROMS) Starting ====================================="
start('WLS_FORMS','Server')
print "================== MANAGED SERVER (REPORTS) Starting ==================================="
start('WLS_REPORTS','Server')
exit()
HOPE WE WILL MEET AGAIN AND AGAIN...
Many thanks for your comments!
Kind Regards,
Mohan

Unable to start the Managed servers OIM and SOA after starting the Weblogic

Hi,
We are unable to start the any manager servers after starting the weblogic Admin Server.
We are getting the below error after trying to start the OIM or SOA managed servers.
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have also cross verified that the port 5555 is listening after starting the weblogic Admin server.
Please help us to start the managed servers in the weblogic 10.3.5.
Thanks.

We are getting the below errors after starting the Admin server and Managed servers.
Admin Server:
<Jan 11, 2012 7:15:06 AM EST> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>
<Jan 11, 2012 7:16:02 AM EST> <Error> <org.apache.beehive.netui.pageflow.internal.AdapterManager> <BEA-000000> <ServletContainerAdapter manager not initialized correctly.>
Managed Server:
Starting WLS with line:
/opt/jdk1.6.0_27/bin/java -client -Xms1024m -Xmx4096m -XX:PermSize=512m -XX:MaxPermSize=1024m -Dweblogic.Name=oim_server1 -Djava.security.policy=/ama/Oracle/Middleware/wlserver_10.3/server/lib/weblogic.policy -Dweblogic.security.SSL.trustedCAKeyStore=/ama/Oracle/Middleware/wlserver_10.3/server/lib/cacerts -Xverify:none -da -Dplatform.home=/ama/Oracle/Middleware/wlserver_10.3 -Dwls.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dweblogic.home=/ama/Oracle/Middleware/wlserver_10.3/server -Dcommon.components.home=/ama/Oracle/Middleware/oracle_common -Djrf.version=11.1.1 -Dorg.apache.commons.logging.Log=org.apache.commons.logging.impl.Jdk14Logger -Ddomain.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -Djrockit.optfile=/ama/Oracle/Middleware/oracle_common/modules/oracle.jrf_11.1.1/jrocket_optfile.txt -Doracle.server.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/servers/oim_server1 -Doracle.domain.config.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig -Digf.arisidbeans.carmlloc=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/carml -Digf.arisidstack.home=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/arisidprovider -Doracle.security.jps.config=/ama/Oracle/Middleware/user_projects/domains/base_domain/config/fmwconfig/jps-config.xml -Doracle.deployed.app.dir=/ama/Oracle/Middleware/user_projects/domains/base_domain/servers/oim_server1/tmp/_WL_user -Doracle.deployed.app.ext=/- -Dweblogic.alternateTypesDirectory=/ama/Oracle/Middleware/Oracle_IDM1/server/loginmodule/wls,/ama/Oracle/Middleware/oracle_common/modules/oracle.ossoiap_11.1.1,/ama/Oracle/Middleware/oracle_common/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 -DXL.HomeDir=/ama/Oracle/Middleware/Oracle_IDM1/server -Djava.security.auth.login.config=/ama/Oracle/Middleware/Oracle_IDM1/server/config/authwl.conf -Dorg.owasp.esapi.resources=/ama/Oracle/Middleware/Oracle_IDM1/server/apps/oim.ear/APP-INF/classes -da:org.apache.xmlbeans... -Dsoa.archives.dir=/ama/Oracle/Middleware/Oracle_SOA1/soa -Dsoa.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dsoa.instance.home=/ama/Oracle/Middleware/user_projects/domains/base_domain -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=/ama/Oracle/Middleware/wlserver_10.3/server/lib/DemoTrust.jks -Dem.oracle.home=/ama/Oracle/Middleware/oracle_common -Djava.awt.headless=true -Dums.oracle.home=/ama/Oracle/Middleware/Oracle_SOA1 -Dweblogic.management.discover=false -Dweblogic.management.server=http://127.0.0.1:7001 -Dwlw.iterativeDev=false -Dwlw.testConsole=false -Dwlw.logErrorsToConsole=false -Dweblogic.ext.dirs=/ama/Oracle/Middleware/patch_wls1035/profiles/default/sysext_manifest_classpath:/ama/Oracle/Middleware/patch_ocp360/profiles/default/sysext_manifest_classpath weblogic.Server
Error: Exception thrown by the agent : java.rmi.server.ExportException: Port already in use: 5555; nested exception is:
java.net.BindException: Address already in use
We have to find out why the port 5555 is in listening mode after starting the Admin server.

Managed Servers vs. Admin Server - heap sizes

Similar Messages

Maybe you are looking for