My Oracle Support Banner

Enabled JMS Module Security In SOA, JMS Client Cannot Be Able To Connect (Doc ID 2731536.1)

Last updated on DECEMBER 01, 2020

Applies to:

Oracle SOA Suite - Version 12.2.1.3.0 and later
Information in this document applies to any platform.

Symptoms

PROBLEM STATEMENT

A JMS client is getting the following error:

 weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: java.rmi.UnmarshalException: Problem deserializing error response; nested exception is:
java.io.InvalidClassException: javax.jms.JMSException; local class incompatible: stream classdesc serialVersionUID = 8951994251593378324, local class
serialVersionUID = 2368476267211489441

When trying to make a client connection to a WLS/SOA JMS queue that they have configured module level security for the JMS service and configured policies for.

DETAILS

Customer is trying to connection to a WLS JMS Topic via a custom/thrd party Java Client and is running into a:

{...} javax.naming.NameNotFoundException: Unable to resolve 'SE-Alarms-Topic'. Resolved ''; remaining name 'SE-Alarms-Topic'
at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:309)
at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:555)
(…}

Error.

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


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