My Oracle Support Banner

Weblogic.socket.MaxMessageSizeExceededException When User Subscribes to Control Zones (Doc ID 1991805.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Utilities Network Management System - Version and later
Oracle Network Management for Utilities - DMS - Version and later
Information in this document applies to any platform.


In performing some pre-go live checks and tests you have encountered the following issue. When a user subscribes to the top level of control zone they are receiving a datastore error:

In the client(users) WebWorkspace log the following error occurs:
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '50000400' bytes exceeds the
configured maximum of: '50000000' bytes for protocol: 't3'.
at weblogic.socket.BaseAbstractMuxableSocket.incrementBufferOffset(
at weblogic.rjvm.t3.client.MuxableSocketT3.incrementBufferOffset(
at weblogic.socket.SocketMuxer.readFromSocket(
at weblogic.socket.SocketMuxer.readReadySocketOnce(
at weblogic.socket.SocketMuxer.readReadySocket(
at weblogic.socket.JavaSocketMuxer.processSockets(
at weblogic.kernel.ExecuteThread.execute(
2015-03-18 06:53:41,907 [Timer-0] ERROR com.splwg.oms.client.workagenda.AlarmsDataStore: execute command AlarmsDataStore::populate
at com.sun.proxy.$Proxy0.getTroubleEvents(Unknown Source)
at com.splwg.oms.client.workagenda.AlarmsDataStore$
at java.util.TimerThread.mainLoop(Unknown Source)
at Source)

The weblogic jvms are set to run with following parameter: -Dweblogic.MaxMessageSize=128000000

If user subscribes to specific control zone issue doesn't occur and workagenda populates.


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

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