By Luz Mestre-Oracle on Jun 25, 2014
If you are using a weblogic standalone client like wlthint3client.jar you might hit MaxMessageSizeExceededException.
If you still see the exact error after setting MaxMessageSize in the Administration Console in Protocols->General, you might be hitting this issue.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
Try setting the value programatically in your java code e.g:
You can also set the value in your JAVA_OPTIONS -Dweblogic.MaxMessageSize=300000000
Sometimes you still can see the same error after set MaxMessageSize in the Administration Console in Protocols->General, but you see the parameter being picked:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '30000080' bytes exceeds the configured maximum of: '30000000' bytes for protocol: 't3'
In these cases, you need to investigate why you have these huge messages along your environment. You can review a tcpdump to research further.