With Large JMS Messages, Siebel JMS Component Fails to Retrieve the Message and the JMS Durable Subscriber is Stuck

(Doc ID 2422212.1)

Last updated on JULY 12, 2018

Applies to:

Siebel CRM - Version 16.19 [IP2016] and later
Information in this document applies to any platform.

Symptoms

On : 16.19 [IP2016] version, Siebel EAI

ACTUAL BEHAVIOR
---------------
There is a problem when the message size exceeds a certain size
With Large Incoming messages Into a JMS TOPIC ( > 24,187 bytes ), Siebel JMS Component fails to retrieve the message and the JMS durable subscriber is stuck.

EXPECTED BEHAVIOR
-----------------------
Siebel JMS component should retrieve the message.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
Post a message with size > 24,187 bytes to the topic.



Changes

 

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms