Friday, September 18, 2015

weblogic.socket.MaxMessageSizeExceededException in SOA server

In this post we shall see solution of "weblogic.socket.MaxMessageSizeExceededException" error observed in SOA server log.

ISSUE:


Error Observed: 

 

Log Location: $DOMAIN_HOME/base_domain/servers/WLS_SOA1/logs/WLS_SOA1.out


<<
Incoming message of size: '10000480' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'.
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000480' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'
>>

Impact:


1) SOA server not responding.

2) Health of SOA server showing blank

3) SOA server loosing connectivity with Admin server.

Cause:


1) The issue is due to MaxMessageSizeExceededException being thrown:
 
 
weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000480' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'

2) SOA server tries to send the message of size more than 10 MB and in turns fails  with above exception. 

3) It is observed that after above error  message is observed in SOA server logs , it looses connectivity with the Admin server.

Solution: 


Step 1) Login to WebLogic console
 http://Hostname:Port/console

Step 2) Click Lock & Edit

Step 3) Go to Servers --> Admin Server --> Protocols --> General

Step 4) Update the Maximum Message Size value 
            Current (Previous) : 10000000
            New (Updated) :  20000000

Step 5) Go to Servers --> WLS_SOA1 --> Protocols --> General

Step 6) Update the Maximum Message Size value 
            Current (Previous) : 10000000
            New (Updated) :  20000000

 
 

Step 7) Save and activate the changes.

Step 8) Restart both admin and SOA server
.

No comments:

Post a Comment

Other Posts