JMS Message Corrupted with "found an incomplete message"
(Doc ID 1603982.1)
Last updated on MARCH 14, 2019
Applies to:
Oracle Java CAPS Enterprise Service Bus - Version R6.2 and laterInformation in this document applies to any platform.
Symptoms
Message got corrupted and stuck in queue, seeing the following message in stcms log:
27-Sep-2013 14:47:14.416 stcms ERROR 3488 []: Read() : found an incomplete message
Has applied the latest stcms hotfix per doc 1028107.1 but problem remains.
Also noticed the following memory related error in log right before the corruption:
27-Sep-2013 14:45:54.991 stcms INFO 2524 [IMessageManager.cpp:527]: UpdateMemoryTracker() : total data memory is 33842698, still exceeds limit 20480000, tick count 3658956300
27-Sep-2013 14:45:54.991 stcms INFO 2524 [SessionManager.cpp:1552]: TruncateInDoubtPayloads() : started
27-Sep-2013 14:45:54.991 stcms INFO 2524 [SessionManager.cpp:1581]: TruncateInDoubtPayloads() : recovered 0 bytes
27-Sep-2013 14:45:54.991 stcms INFO 2524 [IMessageManager.cpp:556]: UpdateMemoryTracker() : total data memory is 33842698, exceeded limit 20480000
27-Sep-2013 14:45:54.991 stcms INFO 2524 [MQManager.cpp:1023]: TruncateUnsentPayloads() : truncating new payloads...
27-Sep-2013 14:45:54.991 stcms INFO 2524 [MQManager.cpp:1089]: TruncateUnsentPayloads() recovered 0 bytes (required 0 bytes)
27-Sep-2013 14:45:54.991 stcms INFO 2524 [MQManager.cpp:1093]: TruncateUnsentPayloads() could not recover the required amount of memory.
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 |