Agile Application Server Performance Issue with weblogic.socket.MaxMessageSizeExceededException for weblogic.socket.NIOSocketMuxer in the Stack Trace
(Doc ID 2735018.1)
Last updated on JANUARY 24, 2024
Applies to:
Oracle Agile PLM Framework - Version 9.3.6.0 and laterInformation in this document applies to any platform.
Symptoms
Getting the below error constantly on the Agile Application Servers.
This issue is coming constantly and getting lots of stuck threads which is causing performance issue with the Agile Application Server:
Error
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '20000160' bytes exceeds the configured maximum of: '20000000' bytes for protocol: 't3'.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '20000160' bytes exceeds the configured maximum of: '20000000' bytes for protocol: 't3'
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:246)
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:207)
at weblogic.rjvm.t3.MuxableSocketT3.incrementBufferOffset(MuxableSocketT3.java:687)
at weblogic.socket.SocketMuxer.readFromSocket(SocketMuxer.java:1010)
at weblogic.socket.NIOSocketMuxer.readFromSocket(NIOSocketMuxer.java:782)
Truncated. see log file for complete stacktrace
Steps
The issue can be reproduced at will with the following steps:
1. Keep Agile Application Server running
2. See the error
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 |