This content has been marked as final. Show 1 reply
1) After setting -Dweblogic.MaxMessageSize to 25000000
<BEA-000403> <IOException occurred on socket: Socket[addr=ac-sync-webserver1/172.24.128.8,port=9040,localport=36285]
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '25002240' bytes exceeds the configured maximum of: '25000000' bytes for protocol: 't3'
2) After setting -Dweblogic.MaxMessageSize to 50000000
<BEA-000403> <IOException occurred on socket: Socket[addr=ac-sync-webserver2/172.24.128.9,port=9040,localport=59925]
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '50000400' bytes exceeds the configured maximum of: '50000000' bytes for protocol:
And even after setting various values for -Dweblogic.MaxMessageSize , issue weblogic.socket.MaxMessageSizeExceededException was observed.
To overcome the issue set Manual Service Migration Only as after several experiments and replicating the issue it was found out that in case of no available pinned services, must set the migration policies of the migratable targets on "Manual Service Migration Only".
And once it is corrected; it was noticed that weblogic.socket.MaxMessageSizeExceededException issue also resolved.
WebLogic Server can fail over most services transparently, but it's unable to do the same when dealing with pinned services.
Pinned Services : JMS and JTA are considered as pinned services. They're hosted on individual members of a cluster and not on all server instances.
You can have high availability only if the cluster can ensure that these pinned services are always running somewhere in the cluster.
When a WebLogic Server instance hosting these critical pinned services fails, WebLogic Server can't support their continuous availability and uses migration instead of failover to ensure that they are always available.