weblogic.socket.MaxMessageSizeExceededException in OSB11g

Hi Friends,

Greetings for the day..!!!

First of all Happy New year to you and your family..!!! Hope this year will be best technology year of your life.

I'm Writing this blog after so many days/month. I have got one query/question on email. Let's discuss on that problem today.

please find below problem statement for OSB and solution along with it.

Whenever we have a long running two-way OSB-DB API call.it takes much time to complete. It will show us the weblogic.socket.MaxMessageSizeExceededException in sbconsole debug console.

We can find below stack trace for the same :

  

Cause: weblogic.socket.MaxMessageSizeExceededException: Incoming message of size: '10000080' bytes exceeds the configured maximum of: '10000000' bytes for protocol: 't3'

After checking logs and stack trace, have found below solution or rather workaround for this issue.

Solution:

Step 1. Go to servers--->protocols--->general--->max message size--->change the value to sufficient memory (Do this for both the admin and the osb/soa). Please do it for all the OSB/SOA nodes in the cluster

Step 2. Go to servers--->configuration--->server start--->arguments--->-Dweblogic.MaxMessageSize = 20000000

Step 3. Restart all the servers.

Hope this will help you to resolve this issue.

Note: Please take back for configuration before doing any change on OSB.

In case of any queries or question, you can write me on middlewaresolution1@gmail.com.


Regards,
Ajinkya Vichare
http://ajinkya-vichare.blogspot.com