My Oracle Support Banner

OEP application tries to connect to JMS queue with credentials from another OEP application (Doc ID 2154738.1)

Last updated on FEBRUARY 28, 2019

Applies to:

Oracle Stream Analytics - Version and later
Information in this document applies to any platform.



-2 Oracle Event Processing applications deployed in OEP 12.1.3 domain (Application A and Application B)
-2 JMS queues deployed in WLS 12.1.2 domain (Queue A and Queue B)
-Application A consume messages from Queue A using a given user and password
-Application B consume messages from Queue B without credentials
-Patch 22820048 is applied to OEP domain

After patch 22820048 has been installed and OEP instances are started, the following exception is thrown:

####<May 3, 2016 4:45:50 PM CEST> <Warning> <com.bea.core.asyncbeans.internal.DefaultMessageListenerContainer> <> <defaultserver> <[ACTIVE] ExecuteThread: '7' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1462286750189> <BEA-000000> <Could not refresh JMS Connection for destination '<module>' - retrying in 5000 ms. Cause: [Security:090398]Invalid Subject: principals=[user]>

Application B is trying to connect to its JMS Queue using the credentials from the Application A.


 Patch 22820048 was applied to OEP environment.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.