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

JMSSecurityException trying to read JMS Queue

304 views
Skip to first unread message

Ryan Richards

unread,
May 30, 2003, 2:02:38 PM5/30/03
to

I am trying to read any JMS queue in weblogic 7.0 SP2. I have created a client
that allows me to read messages from any queue on 8.1. I have tried on a different
environment (running WL Integration) and now I get Access Denied errors even with
the admin user and pw. I am sending these credentials. Here is the error:

Got the queue: RyanTestQueue
weblogic.jms.common.JMSSecurityException: Access denied to resource: type=<jms>,
application=, destinationType=queue, resource=RyanTestQueue, action=browse

Start server side stack trace:
weblogic.jms.common.JMSSecurityException: Access denied to resource: type=<jms>,
application=, destinationType=queue, resource=RyanTestQueue, action=browse
at weblogic.jms.JMSService.checkPermission(JMSService.java:1065)
at weblogic.jms.JMSService.checkBrowsePermission(JMSService.java:1081)
at weblogic.jms.frontend.FESession.browserCreate(FESession.java:1100)
at weblogic.jms.frontend.FESession.invoke(FESession.java:2254)
at weblogic.jms.dispatcher.Request.wrappedFiniteStateMachine(Request.java:602)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchAsync(DispatcherImpl.java:152)
at weblogic.jms.dispatcher.DispatcherImpl.dispatchSyncFuture(DispatcherImpl.java:303)
at weblogic.jms.dispatcher.DispatcherImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:362)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:313)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:821)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:308)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
End server side stack trace

at weblogic.rmi.internal.BasicOutboundRequest.sendReceive(BasicOutboundRequest.java:109)
at weblogic.rmi.internal.BasicRemoteRef.invoke(BasicRemoteRef.java:127)
at weblogic.jms.dispatcher.DispatcherImpl_WLStub.dispatchSyncFuture(Unknown Source)
at weblogic.jms.dispatcher.DispatcherWrapperState.dispatchSync(DispatcherWrapperState.java:282)
at weblogic.jms.client.JMSSession.createBackEndBrowser(JMSSession.java:1749)
at weblogic.jms.client.JMSQueueBrowser.<init>(JMSQueueBrowser.java:46)
at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1344)
at weblogic.jms.client.JMSSession.createBrowser(JMSSession.java:1324)
at Test.init(Test.java:41)
at Test.main(Test.java:115)
Exception in thread "main"

Thanks for any help
Ryan

Tom Barnes

unread,
Jun 2, 2003, 12:28:09 PM6/2/03
to Ryan Richards
"browse" "send" and "receive" are the three types of things
that can be configured for security on a queue. I suspect
you've configured "send" and "receive" permission and not
browse - or that you've configured "browse" to require
different security privileges than "send" or "receive.
0 new messages