Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

java.security.acl.NotOwnerException

0 views
Skip to first unread message

Liping Li

unread,
Sep 17, 2001, 8:46:12 PM9/17/01
to
I am using WL6.0 sp2. I want to set up my Topic through a startup
class instead of through console. I tried to achieve that by invoking
the method weblogic.jms.extensions.JMSHelper.createPermanentTopicAsync()
in my startup class.

However, I found out that only the admin server can excute the startup
class and
create the Topic as expected. The managed server (even though they are
in the same box)
can not be started because of the java.security.acl.NotOwnerException.

I was told that the admin server and the managed server may get
different context and therefore will
have different accessibility.

My question is: can I change something (such as user privilege or
ACL...) so that my managed
server will be able to create a Topic?

Thanks in advance for any help. Here is what I got when I tried to
start my managed server:
--------------------------------------------------------------------------------------------

####<Sep 17, 2001 2:44:52 PM CDT> <Info> <Log Management> <DDYE>
<LiPingServer> <main> <> <> <170016> <FileLogger initialized. There may
be
some pre-initialization messages in
C:\WebGain\bea\wlserver6.0\LiPingServer-startup.log>

####<Sep 17, 2001 2:44:52 PM CDT> <Info> <Logging> <DDYE> <LiPingServer>

<main> <> <> <000000> <Only log messages of severity "Error" or worse
will
be displayed in the shell console.>

####<Sep 17, 2001 2:44:53 PM CDT> <Info> <WebLogicServer> <DDYE>
<LiPingServer> <main> <> <> <000000> <IIOP subsystem enabled.>

####<Sep 17, 2001 2:44:53 PM CDT> <Emergency> <Server> <DDYE>
<LiPingServer>
<main> <> <> <000000> <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(WLInitialContextFactoryDelegate.java:444)

at
weblogic.jndi.WLInitialContextFactoryDelegate.newContext(WLInitialContextFactoryDelegate.java:287)

at
weblogic.jndi.WLInitialContextFactoryDelegate.getInitialContext(WLInitialContextFactoryDelegate.java:259)

at weblogic.jndi.Environment.getContext(Environment.java:135)
at
weblogic.jndi.Environment.getInitialContext(Environment.java:118)
at
weblogic.management.Admin.initializeRemoteAdminHome(Admin.java:891)
at weblogic.management.Admin.start(Admin.java:305)
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)
-------------

Liping.

Liping Li

unread,
Sep 18, 2001, 10:56:25 AM9/18/01
to
Problem solved. Thank you all.
0 new messages