Managed Servers and NotOwnerException

"Perry Hoekstra" <[email protected]> wrote in message
news:[email protected]...
Greet the sun all:
I setup a domain and server. I started up the admin server and can see
the administrative console. However, when I start a managed server
instance, I receive a:
<May 1, 2001 10:49:48 AM CDT> <Emergency> <Server> <Unable to initialize
the server: 'Fatal initialization exception
Throwable: java.lang.IllegalAccessError:
java.security.acl.NotOwnerException
java.lang.IllegalAccessError: java.security.acl.NotOwnerException
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:36)
at weblogic.security.acl.Realm.authenticate(Realm.java:183)
at
weblogic.security.acl.Realm.getAuthenticatedName(Realm.java:233)
at
weblogic.security.acl.internal.Security.authenticate(Security.java:116)
at
weblogic.jndi.WLInitialContextFactoryDelegate.pushUser(WLInitialContextFacto
ryDelegate.java:429)
>
at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFac
toryDelegate.java:272)
>
at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialCon
textFactoryDelegate.java:244)
>
at weblogic.jndi.Environment.getContext(Environment.java:135)
at
weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:888)
at weblogic.management.Admin.start(Admin.java:303)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:331)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:169)
at weblogic.Server.main(Server.java:35)
I followed the "java.security.acl.NotOwnerException when Administration
Port is set" thread of 4/3/2001 but believe it does not apply due to the
fact that I have the Administration Port set to 0. In addition, the
system password is passed to WebLogic through the
weblogic.management.password parameter in the startup script (I copied
the startManagedServer script from config/domain as a template).
Under what circumstances would this exception be thrown when a managed
server instance starts up?
Perry Hoekstra
E-Commerce Architect
Talent Software Solutions
[email protected]

Similar Messages

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

Multiple managed servers, Multiple machines and Multiple clusters

Hi,
I have couple of applications to be deployed in high availabliity. I
have been a Tomcat/Apache guy so far. Yesterday night I read the whole admin doc
and tried some installations on the boxes. But have some confusion here.
Since our application is getting commercialised and I like to have 12 managed
serves on each of the three big linux servers and one windows machine as admin
server port 9002. 18 for each application in clustered environment. cluster of
18 for each application.
FIRST CONFUSION is
I want to use only one domain name. So I install weblogic81
on win box and call it dls and then I find out that I need to install weblogic81
as good as the one on win box on linux servers, not surpised, but during the installation
when it asked me for a domain name I was confused. No option to join the existing
domain that I created on my winbox.
Why??? So I type dls again.
Is there a way not to do all this as it may be creatign another domain and just
start nodemanager and not install domain at all ?
SECOND CONFUSION is
When I was installing weblogic on win machine as admin server. I was given
options of adding managed servers and clusters amd machines. So do we need to
have all the managed servers already running before I add them here or I can do
it later.
Thanks n Advance.
Vivke

http://www.rittmanmead.com/2010/07/obiee-11gr1-scaleout-clustering-and-high-availability/
hope it helps

Best practice to restart weblogic and managed servers after changing pass

hi
i need to know if have an installation with the following structer what is the best practice to restart the servers after we change weblogic password ?and i know that i should change boot.properties with the new password ,is there anything else to change ? please advise .
oracle access manager &oid (dose it affected by weblogic password change ?)
thank you
Edited by: hsweiss on Jul 31, 2012 10:45 AM

the order is to restart:All managed servers and followed by Admin server
If your weblogic server is integrated with oid, you need to change the credentilas in both the places ie weblogic server(boot.properties) and idm server
if your weblogic server is using your internal ldap for the authentication, your idm and oam wil not effect with this change
if you change the boot.properties file that is enough, you don't need to change anywhere

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

Need recommendation - iis with two physical servers and clusters

Hello,
I was hoping to get a recommendation/opinion or two on the configuration I've inherited. I'm looking
at the following configuration using weblogic 8.1 sp4 server (to be upgraded to sp6) running on two physical machines:
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7001
ManagedServer2:7010
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:7001
ManagedServer4:7010
On MachineA: IIS Proxy Plugin with parameter in .ini file
WeblogicCluster: MachineA:7001, MachineA:7010, MachineB:7001,MachineB7010
Naturally, the IIS is acting as a round robin load balancer..
The domains were created using the wizard on both machines and basic domain template..
For proper failover to be taken advantage of, does something different need to be configured? Or is it fine?
And if so, does group replication have something to do with it?
Should either of the clusters be Managed Servers across physical machines?
or should this just be one cluster of 4 managed servers across two machines?
I really am not sure on any of this, even though i've read through much of the documentation for clustering..twice.
I should mention that there is only a .war file deployed with 4 connection pools and 4 Data Sources..No EJBs or JMS
Would really appreciate any feedback or opinions/advice..
Thanks

This is what I'd do
MachineA:
Domain: myDomain
Cluster: cluster1
Servers: Admin Server:9001 (not part of cluster)
ManagedServer1:7010
ManagedServer2:7020
MachineB:
Domain: myDomain
Cluster: cluster2
Servers: Admin Server:9001 (not part of cluster)
ManagedServer3:8010
ManagedServer4:8020
I just changed the port numbers so they flow and have a pattern - 70* port numbers belong to cluster 1, 80* port numbers belong to cluster 2. No technical benefit apart from it makes it tidier in my opinion.
Port 9001 for the admin server is normally the domain wide admin port - you could be using that, so that's fine, but my admin server is running 7001.
You also only need one admin server per domain, this can run on MachineA
Replication groups are used to help WLS figure out where to place the secondary http session. It will try servers on a different machine/replication group first, if none available, it will create secondary on the same machine.
What you will end up with is a domain with 4 managed servers in it. The admin server will run on machineA, say using port 7001, each of the managed servers will contact the admin server to download it's config.
The cluster1 will contain 2 managed servers and the same for cluster2.
providing you have your cluster multicast addresses set up and the cluster is working, that should be all you need to do for the session failover.
There's some BEA sample code somewhere which will deploy a web-app and show which managed server you've attached to. If you find that and then connect through IIS, shut down the server that the JSP tells you, you should be able to see the session fail-over nicely.
Hope that helps,
Pete

SCOM Management Servers not working after DW upgraded to SQL 2014

Hey guys,
Our setup is that we have 2 Management Servers running SCOM 2012 R2 UR3 on Server 2008. I want to say exactly what our problem is, and what my guesses are at it. Any additional information you need please just ask.
Problem = In the SCOM console we have the management servers and Gateway servers going grey. If i go to these servers and restart the Monitoring service, it acts like it was locked up or something and has to force stop it and restart it. Once back up, everything
works fine. Then it goes grey again at a random interval between 5-120 minutes. Recycle Repeat. I reviewed the Event Log during this and afterwards and ALOT of stuff points toward the DataWarehouse and not being able to write stuff to it. I have two suspicions.
Idea 1 = Another Engineer recently updated SQL on the Datawarehouse server to 2014. I recently found this had caused a problem with SCSM reporting and had to do some stuff to fix that.... so I was thinking that maybe this had something to do with it.
Idea 2 = Also around the same time... UR3 came out. This was auto pushed out to all the server and agents through WSUS, I also went through and manually did all the steps for this. Its still possible i suppose that I missed something.
Basically Im just looking to see if anyone has any advice as to what to check next, and/or see if anyone else has had this problem. Thanks guys!

I unfortunately do not have a solution for you, but can still try to provide some info :
1. SQL 2014 is NOT supported with system center 2012 R2! See http://technet.microsoft.com/library/dn281933.aspx
2. You might want to try the procedure for moving the databases : http://technet.microsoft.com/en-us/library/hh278848.aspx

Why SCOM 2012 R2 Agent version for Service Manager servers is 6.1.7221.49, why not 7.1.10184.

Hi ,
In SCOM 2012 R2 console if i look at all of my agent managed servers have agent builds of 7.1.10184 but my two service manager servers have agent builds of 6.1.7221.49
Can anyone let me know is this known issue or how can we upgrade the agent to correct version.
Thanks in advance
Bharath

Hi,
SCOM and SCSM are built on the same structure, Management Servers and DAta Warehouse etc. This means that when you install the SCSM Management Server, the Microsoft Monitoring Agent is also installed. When
you want to monitor Service Manager and the server it´s installed on, you need to configure the SCOM parameters from the control panel at the SCSM management server.
If you were to try and install the SCOM agent at the SCSM server, it would fail and tell you that you can´t install the agent on a server where Service Manager is installed. The agent will be upgraded when
you upgrade Service Manager so this is all expected and It´s as it should be :)
Regards,
Daniel
IT Consultant at Viridis IT

Why 2 floating IP's are used to Weblogic managed servers?

In the configuration example discussed in this guide, two floating addresses
are used to each of the WebLogic Managed Servers and to the Administration
Server. The first type of floating IP address uses the IPoIB (BOND0) interface,
and the second type of floating IP uses the EoIB (BOND1) interface.
The above are excerpts from this document: http://docs.oracle.com/cd/E18476_01/doc.220/e18479.pdf page 3-10
My question is, why do I have to use 2 floating IP's, one uses bond0 and the other uses bond1? can I just create one floating on bond1 and for all purposes, for instance? For what reasons, do I have to use 2 floating IP's?
Thanks!
Edited by: 943714 on Jan 29, 2013 12:01 PM

Hi,
Two floating IP's should be used because on an Exalogic machine there are multiple network interfaces. As it says on that document, bond0 is for IPoIB and bond1 is EoIB.
bond1 is the interface available outside the Exalogic machine. But, for example, if you need to connect to an Exadata machine (using Weblogic with JDBC/GridLink) that must be done through InfiniBand (IPoIB - bond0 interface).
Hope this helps.
-Cris

Weblogic.Admin command for stopping all Managed Servers in cluster

Hello All,
I am using Weblogic 9.2 MP3 on Linux env. I have a domain which has 16 Managed servers which are part of a cluster, I have eight Managed Servers running on one physical machine and other eight running on another physical Machine.
I know we can do all stop and all start of Managed servers from console if we have node manager setup. We do not want to have node manager setup in our env.
I am looking for a way to do that using java weblogic.Admin utility
Please let me know on how we can achieve this using weblogic.Admin utility by passing clustername argument.
Thanks
Weblogic Consultant

hi sir,
I think in weblogic 9.2 weblogic.Admin utility is deprecated but it works in 9.2. We have better option than weblogic.Admin utility nothing but WLST. If u want to start using weblogic.Admin we have command
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN managedservername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx START clustername
java weblogic.Admin -url adminhost:listenport -username xxxx -password xxxx SHUTDOWN clustername
If u want to use WLST for starting managed servers and clusters
check the follwing steps.
1. java weblogic.WLST
2. startNodeManager()
3. TAKE ANOTHER COMMAND PROMPT START ADMIN SERVER
4. TAKE ANOTHER COMMAND PROMPT
java weblogic.WLST
5. start('man1','Server') or start('man1','Server','localhost:7003')
6. start('mycluster','Cluster')
7.shutdown('man1','Server') or start('man1','Server','localhost:7003')
8.shutdown('mycluster','Cluster')
regards
abhi
Edited by: sumanth_abhi on Feb 5, 2009 8:54 PM

Weblogic 10.3.6 managed servers are not working properly

Hi,
i am using weblogic 10.3.6. I have 6 managed server and one Admin server. I observed one thing that when i up Managed6 and run my application. In one of the java file i am using one jar file to fetch one class(Bussiness Object instance). For managed 6 the code is working fine. it gives me the same class file. but if i up any other managed server then i am getting the Impl of that class.
can anyone help me out. Thanks in advance.

Hi,
You shouldn't have to edit the startup.properties manually.
Try the following sequence:
1. Shut down all managed servers;
2. Change the property in the Admin Console;
3. Restart the AdminServer;
4. Start the managed servers and check the property;
Make sure the managed server do not start in Independence Mode

Empty initial replica exception while starting up managed servers

Hi,
I am doing what should be a fairly straight forward installtion/configuration of the weblogic portal 10.3.2.
I have installed the portal, created a new domain with one admin server and two managed servers in it. I also have a cluster on which I have both my managed servers and finally I have a machine on which I have all the 3 of my servers.
I am able to successfully startup the nodemanager and then the admin server. But when I try to start up the managed servers from the admin console, I get this exception -
####<Feb 11, 2011 12:39:37 PM IST> <Critical> <WebLogicServer> <XXXXXXXX> <new_ManagedServer_1> <Main Thread> <<WLS Kernel>> <> <> <1297408177691> <BEA-000386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Empty initial replica
weblogic.ldap.EmbeddedLDAPException: Empty initial replica
     at weblogic.ldap.EmbeddedLDAP.getInitialReplicaFromAdminServer(EmbeddedLDAP.java:1301)
     at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:221)
     at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Any idea what could be the reason for this?
Regards,
Kunal
Edited by: kunal. on Feb 11, 2011 1:34 AM

Hi,
anybody got any solution to this?
Regards,
Kunal

Cannot start the managed servers because of this error.

Hi,
I installed weblogic 10.3.6 and created admin and managed servers and node manager. I am able to startup and shutdown the admin and managed servers using the node managers but when i try to start/shutdown the managed servers from the command prompt using startManagedWeblogic.cmd, i get this error:
<Apr 27, 2012 3:42:57 PM EDT> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason:
There are 1 nested errors:
java.net.UnknownHostException: XXXXXX.XXXX.XXXX : 7152
at java.net.Inet6AddressImpl.lookupAllHostAddr(Native Method)
at java.net.InetAddress$1.lookupAllHostAddr(InetAddress.java:849)
at java.net.InetAddress.getAddressFromNameService(InetAddress.java:1202)
at java.net.InetAddress.getAllByName0(InetAddress.java:1153)
at java.net.InetAddress.getAllByName(InetAddress.java:1083)
at java.net.InetAddress.getAllByName(InetAddress.java:1019)
at java.net.InetAddress.getByName(InetAddress.java:969)
at weblogic.rjvm.JVMID.setLocalID(JVMID.java:238)
at weblogic.rjvm.RJVMService.setJVMID(RJVMService.java:48)
at weblogic.rjvm.RJVMService.start(RJVMService.java:30)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:256)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:221)
>
The WebLogic Server encountered a critical failure
Reason: Assertion violated
Exception in thread "main" java.lang.NoClassDefFoundError: Could not initialize
class weblogic.protocol.ServerIdentityManager$Initializer
at weblogic.protocol.ServerIdentityManager.findServerIdentity(ServerIden
tityManager.java:64)
at weblogic.protocol.URLManager.findAdministrationURL(URLManager.java:173)
at weblogic.server.ServerLifeCycleRuntime.getLifeCycleOperationsRemote(S
erverLifeCycleRuntime.java:1078)
at weblogic.t3.srvr.ServerRuntime.sendStateToAdminServer(ServerRuntime.java:429)
at weblogic.t3.srvr.ServerRuntime.updateRunState(ServerRuntime.java:415)
at weblogic.t3.srvr.T3Srvr.setState(T3Srvr.java:206)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:482)
at weblogic.Server.main(Server.java:71)
Can anybody help me out with this. I am stuck here.
Thanks,
Robert
Edited by: Robert J on Apr 27, 2012 12:57 PM

try using flag -Djava.net.preferIPv4Stack=true within the startManagedWeblogic.cmd file to start the managed server with the command prompt.
Thanks,
Sandeep

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();

Managed Servers and NotOwnerException

Similar Messages

Maybe you are looking for