Error in WebLogic Clustering : socket MaxMessage Size Exceeded Exception

I recently encountered below error (weblogic.socket.MaxMessageSizeExceededException) in WebLogic Server logs for J2EE application deployed on WebLogic Server .

 

<21-May-2013 20:04:06 o’clock UTC> <Error> <Socket> <BEA-000403> <IOException occurred on socket: Socket[addr=oimvhn1.mydomain.co.uk/192.168.1.1, port=14000,localport=37400]
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: ‘10000080’ bytes exceeds the configured maximum of: ‘10000000’ bytes for protocol: ‘t3’.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: ‘10000080’ bytes exceeds the configured maximum of: ‘10000000’ bytes for protocol: ‘t3’
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:174)
at weblogic.rjvm.t3.MuxableSocketT3.incrementBufferOffset(MuxableSocketT3.java:351)
at weblogic.socket.SocketMuxer.readFromSocket(SocketMuxer.java:983)
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:922)
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:898)
Truncated. see log file for complete stacktrace

_____

To fix above errors, increase Maximum Message Size for WebLogic Server at following three places (depending on server configuration and how you start services , parameter weblogic.MaxMessageSize may pick value from different places )

  • Add parameter -Dweblogic.MaxMessageSize to value higher than one mentioned in error message (10000080) for WebLogic Server . WebLogic Console -> Servers ->[server_name] ->  Protocols -> General -> Max Message Size
  • Add Maximum Message Size to value higher than one mentioned in error message (10000080) for WebLogic Server
    WebLogic Console -> Servers ->[server_name] ->  Configuration -> Server Start -> Arguments-Dweblogic.MaxMessageSize = 10000080
  • Add below parameter -Dweblogic.MaxMessageSize in environment variable file $DOMAIN_HOME/bin/setDomainEnv.sh or setSOADomainEnv.sh (for SOA application)EXTRA_JAVA_PROPERTIES=”${EXTRA_JAVA_PROPERTIES} -Dweblogic.MaxMessageSize=10000080

 

 

Related/References

  • FVC Utility: How To Solve the WLS Incoming Message Of Size: ‘10000080’ Bytes Exceeds The Configured Maximum ? [ID 1552859.1]
  • FVCUtil.cmd Fails with Error “Weblogic.socket.MaxMessageSizeExceededException” [ID 1552487.1]
  • Can Not Access The Audit Trail From Enterprise Manager: “weblogic.socket.MaxMessageSizeExceededException” “weblogic. rmi. extensions. RequestTimeoutException” [ID 1352342.1]

 

Learn Oracle Weblogic Server Administration

 

Get 100 USD OFF + 100% Money Back Guarantee

Click here to get Early Bird Discounts

Share This Post with Your Friends over Social Media!

About the Author Atul Kumar

Oracle ACE, Author, Speaker and Founder of K21 Technologies & K21 Academy : Oracle Gold Partner specialising in Design, Implement, and Trainings.

follow me on:

Leave a Comment:

1 comments
APOC says October 2, 2014

About setting arguments from GUI:

Remove blank spaces before and after “=”.

Use this:
-Dweblogic.MaxMessageSize=10000080

not this

-Dweblogic.MaxMessageSize = 10000080

Otherwise AdminServer, SOA server wont start and you will have to edit config.xml and startup.properties manually to fix issue.

Reply
Add Your Reply