Post Cartridge Deployment Getting Error "Access Denied To Resource: Type=<jms>"
(Doc ID 2691816.1)
Last updated on MAY 06, 2022
Applies to:
Oracle Communications ASAP - Version 7.3.0.0.0 and laterInformation in this document applies to any platform.
Symptoms
Post Cartridge deployment getting error "Access denied to resource: type="
Customer performing ASAP 7.3.0.4 fresh installation. Post ASAP custom Cartridge installation, seeing below error in logs.
ERROR
-----------------------
javax.jms.JMSSecurityException: Access denied to resource: type=, application=AS7.asap_jms_module, destinationType=queue, resource=AS7.JVTEventQueue, action=receive
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:110)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:45)
at weblogic.jms.client.JMSSession.consumerCreate(JMSSession.java:3048)
at weblogic.jms.client.JMSSession.setupConsumer(JMSSession.java:2806)
at weblogic.jms.client.JMSSession.createConsumer(JMSSession.java:2748)
at weblogic.jms.client.JMSSession.createReceiver(JMSSession.java:2627)
at weblogic.jms.client.WLSessionImpl.createReceiver(WLSessionImpl.java:966)
at com.xxxxx.jsrp.asap.JSRPNotificationJMSReceiver.initialize(JSRPNotificationJMSReceiver.java:218)
at com.xxxxx.jsrp.asap.JSRPNotificationJMSReceiver.run(JSRPNotificationJMSReceiver.java:250)
at weblogic.jms.dispatcher.DispatcherAdapter.convertToJMSExceptionAndThrow(DispatcherAdapter.java:127)
at weblogic.jms.dispatcher.DispatcherAdapter.dispatchSync(DispatcherAdapter.java:51)
at weblogic.jms.frontend.FEConsumer.(FEConsumer.java:297)
at weblogic.jms.frontend.FESession$2.run(FESession.java:1091)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:368)
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |