Message Size Limit in JMSReceiver
(Doc ID 1597457.1)
Last updated on JANUARY 03, 2023
Applies to:
Siebel System Software - Version 8.1.1.7 SIA [21238] and laterInformation in this document applies to any platform.
Symptoms
On : 8.1.1.7 SIA [21238] version, Siebel EAI
There is a use case where UCM reads the messages from SOA Queues using JMS Receiver component and the following error is being observed while reading huge payloads.
ERROR
-----------------------
ObjMgrBusServiceLog Error 1 00000027526e251b:0 2013-10-28 15:50:03 (jmsbsvc.cpp (350)) SBL-EAI-05103: A JMS exception occurred in EAI JMS Transport: 'Exception: weblogic.jms.common.JMSException: weblogic.messaging.dispatcher.DispatcherException: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3s'; Message: weblogic.messaging.dispatcher.DispatcherException: weblogic.rjvm.PeerGoneException: ; nested exception is:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3s''.
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 |
Cause |
Solution |
References |