Oracle SOA 11g - Disabling the Auto recovery of Faulted Instances,invoke and callback messages

Hi Friends,

　

Greetings to Everyone... !!!

Hope you all doing well. today we will talk about some SOA issue faced by one of my friend. We analyze this issue and found below solution.

Problem Statement :

We observe that there is excessive growth in DB from SOA applications. It generally happened when there are some failures in application calls.

Solution found is disabling the Auto recovery of Faulted Instances ,invoke and callback messages.

Let's talk about auto recovery, auto recovery is the functionality to recover the faulted instances and Invoke and Callback messages in SOA 11g.

Sometimes we need to disable this feature to avoid unnecessary table space growth and recovering the instance that fail even after the recovery.

Disabling recovery attempts for faulted instances.

Step 1. Log in to Oracle Enterprise Manager Fusion Middleware Control.

Step 2. Right-click soa-infra.

Step 3. Select SOA Administration > BPEL Properties.

Step 4. Click More BPEL Configuration Properties.

Step 5. In the Name column, click RecoveryConfig.

Step 6. Expand RecurringScheduleConfig.

Step 7. Set the following properties to values and click Apply.

maxMessageRaiseSize =0

Step 8. Expand StartupScheduleConfig, respectively.

Step 9. Set the following properties to values and click Apply.

maxMessageRaiseSize=0

I hope this will help in your issues.

Keep working on Middleware technologies and write me if you need any further help.

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

Regards,
Ajinkya Vicharehttp://ajinkya-vichare.blogspot.com

 

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