use JMSHelper class to create new Destination

[Liping Li]

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 method in weblogic.jms.extensions.JMSHelper class in my
startup class. However, I always get the following Exception on the
server consol. How can I do it correctly? Thank you in advance.

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Exception in thread "main" weblogic.jms.common.JMSException:
weblogic.management.NoAccessRuntimeException: loo
k for details in server log
at
weblogic.jms.extensions.JMSHelper.createPermanentDestination(JMSHelper.java:120)

at
weblogic.jms.extensions.JMSHelper.createPermanentTopicAsync(JMSHelper.java:197)

at examples.jms.topic.TopicSend.init(TopicSend.java:78)
at examples.jms.topic.TopicSend.main(TopicSend.java:146)
----------- Linked Exception -----------
weblogic.management.NoAccessRuntimeException: look for details in server
log
at
weblogic.rmi.internal.AbstractOutboundRequest.sendReceive(AbstractOutboundRequest.java:90)

at
weblogic.management.internal.AdminMBeanHomeImpl_WLStub.getActiveDomain(AdminMBeanHomeImpl_WLStub.ja

va:2128)
at
weblogic.jms.extensions.JMSHelper.createPermanentDestination(JMSHelper.java:91)

at
weblogic.jms.extensions.JMSHelper.createPermanentTopicAsync(JMSHelper.java:197)

at examples.jms.topic.TopicSend.init(TopicSend.java:78)
at examples.jms.topic.TopicSend.main(TopicSend.java:146)
----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Here is what in the log file:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------

####<Sep 15, 2001 1:40:13 PM CDT> <Info> <Security> <DDYE> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <> <>
<000000> <Mbean access with clientHost=weblogic.rjvm.RJVMImpl@1e7fe -
id: '8027770612835557762C:199.82.241.11' connect time: 'Sat Sep 15
13:40:10 CDT 2001'>
weblogic.management.NoAccessRuntimeException: User guest does not have
access permission on weblogic.admin.mbean.MBeanHome
at
weblogic.management.internal.Helper.checkAdminPermission(Helper.java:1478)

at weblogic.management.internal.Helper.checkAccess(Helper.java:1463)
at
weblogic.management.internal.AdminMBeanHomeImpl.getActiveDomain(AdminMBeanHomeImpl.java:457)

at
weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(AdminMBeanHomeImpl_WLSkel.java:746)

at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)

at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)

at
weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)

at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)

at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
####<Sep 15, 2001 1:40:13 PM CDT> <Warning> <Adapter> <DDYE> <myserver>
<ExecuteThread: '1' for queue: '__weblogic_admin_rmi_queue'> <> <>
<000000> <RuntimeException thrown by rmi server(class
weblogic.management.internal.AdminMBeanHomeImpl)
[3267873577886035734S:199.82.241.11:[7001,7001,7002,7002,7001,7002,-1]/308]:
weblogic.management.internal.AdminMBeanHomeImpl@786a3c>
weblogic.management.NoAccessRuntimeException: User guest does not have
access permission on weblogic.admin.mbean.MBeanHome
at
weblogic.management.internal.Helper.checkAdminPermission(Helper.java:1478)

at weblogic.management.internal.Helper.checkAccess(Helper.java:1463)
at
weblogic.management.internal.AdminMBeanHomeImpl.getActiveDomain(AdminMBeanHomeImpl.java:457)

at
weblogic.management.internal.AdminMBeanHomeImpl_WLSkel.invoke(AdminMBeanHomeImpl_WLSkel.java:746)

at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:373)

at
weblogic.rmi.internal.BasicServerAdapter.invoke(BasicServerAdapter.java:237)

at
weblogic.rmi.internal.BasicRequestHandler.handleRequest(BasicRequestHandler.java:118)

at
weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:17)

at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)

[Tom Barnes]

The context you are using does not have permission to modify the configuration.
You must either use a context that is the "administrator" user, or
increase the privileges of the user for the context, or decrease the
security requirements of the ACL that protects the configuration. I'm
not sure how to do the latter two (or even it is possible), but I know the
the former works.