Maximum Message Size Parameter Change Within The Weblogic Console For T3 Protocol Not Taking Effect When Searching Admin History
(Doc ID 1335305.1)
Last updated on MAY 10, 2024
Applies to:
Oracle Agile PLM Framework - Version 9.2.2.6 to 9.3.1.0 [Release 9.2.0.0 to 9.3]Information in this document applies to any platform.
Symptoms
In Java client, when searching in the 'Administrator History, an error is thrown in the weblogic console.
Error:
weblogic.socket.MaxMessageSizeExceededException:
Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'.
The issue can be reproduced at will with the following steps:
1) Launch the Agile PLM Java Client
2) Go to the 'Administrator History' tab and attempt to search for anything. This takes around 30 seconds on our system.
3) The Java Console will have the usual error: weblogic.socket.MaxMessageSizeExceededException:
Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'.
Facts:
WebLogic
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 |