Weblogic.socket.MaxMessageSizeExceededException: Incoming Message Of Size: '########' Bytes Exceeds the configured maximum of: '50000000' bytes (Doc ID 2639229.1)

Last updated on OCTOBER 17, 2023

Applies to:

Symptoms

We see the maxmessage size exception in the NMS client log when trying to load maps in the viewer.


ERROR
-----------------------
Caused by: weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '########' bytes exceeds the configured maximum of: '50000000' bytes for protocol: 't3'
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:246) ~[wlthint3client.jar:?]
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(BaseAbstractMuxableSocket.java:207) ~[wlthint3client.jar:?]
at weblogic.rjvm.t3.client.MuxableSocketT3.incrementBufferOffset(MuxableSocketT3.java:200) ~[wlthint3client.jar:?]
at weblogic.socket.SocketMuxer.readFromSocket(SocketMuxer.java:1010) ~[wlthint3client.jar:?]
at weblogic.socket.SocketMuxer.readReadySocketOnce(SocketMuxer.java:940) ~[wlthint3client.jar:?]
at weblogic.socket.SocketMuxer.readReadySocket(SocketMuxer.java:907) ~[wlthint3client.jar:?]
at weblogic.socket.JavaSocketMuxer.processSockets(JavaSocketMuxer.java:385) ~[wlthint3client.jar:?]
at weblogic.socket.SocketReaderRequest.run(SocketReaderRequest.java:30) ~[wlthint3client.jar:?]
at weblogic.work.ExecuteRequestAdapter.execute(ExecuteRequestAdapter.java:21) ~[wlthint3client.jar:?]
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:147) ~[wlthint3client.jar:?]

This is happening by selecting an outage in Workagenda and then selecting the target to focus on the event's device in the viewer.

Attempts to increase the message size did not correct the problem.  

1. Increase the Maximum Message Size setting in Weblogic (page 3-24 of the NMS Install Guide)

Configure T3 Protocol
1.  If you have not already done so, in the Administration Console Change Center, click Lock & Edit.
2.  In the left pane of the Console, expand Environment and select Servers.
3.  On the Servers page, click on the server name.
4.  Select Protocols > General.
5.  In the Maximum Message Size field, enter 50000000.

2. in the $NMS_CONFIG/server/CentricityServer.properties   (you should create a project-specific version of this file, then set the this parameter higher or comment out for testing)

# The max size of a map request that can be returned in bytes. This should be a maximum
# of 90% of what the MaxMessageSize is set to. If not set, it will not attempt to limit
# the return size.
viewer.max_base_maps_size = 45000000

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.