weblogic.socket.MaxMessageSizeExceededException

I am getting this:

<Error> <Socket> <BEA-000403> <IOException occurred on socket: Socket[addr=10.10.200.200/10.10.200.200,port=4243,localport=7011]

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.AbstractMuxableSocket.incrementBufferOffset(AbstractMuxableSocket.java:262)

at weblogic.rjvm.t3.MuxableSocketT3.incrementBufferOffset(MuxableSocketT3.java:343)

at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:910)

at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:859)

at weblogic.socket.DevPollSocketMuxer.processSockets(DevPollSocketMuxer.java:120)

at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:29)

at weblogic.socket.SocketReaderRequest.execute(SocketReaderRequest.java:42)

at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:145)

at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:117)

>

You can identify the client issuing the request looking at the IP address (10.10.200.200).


Solution:

On the receiving side, go to:
Server/Protocols/General/Maximum Message Size

and increase it.

"The maximum number of bytes allowed in messages that are received over all supported protocols, unless overridden by a protocol-specific setting or a custom channel setting."


The console help on this attribute is very interesting:



The order of precedence for setting message size maximums is as follows:

- A channel-wide maximum in a custom network channel.

- A protocol-specific setting in the default network channel.

See

MaxCOMMessageSize

MaxHTTPMessageSize

MaxIIOPessageSize

MaxT3MessageSize


The message maximum in this attribute.

This maximum message size helps guard against a denial of service attack in which a caller attempts to force the server to allocate more memory than is available thereby keeping the server from responding quickly to other requests.

MBean Attribute:
ServerMBean.MaxMessageSize

Minimum value: 4096

Maximum value: 2000000000

Secure value: 10000000


Related Tasks

Configure T3 protocol
Configure HTTP protocol
Enable and configure IIOP
Enable jCOM
Related Topics

Configuring Network Resources






Otherwise, change the JAVA_OPTIONS to incorporate

-Dweblogic.MaxMessageSize=20000000