Configure Auto-Recovery in Oracle SOA Suite
1) Change RecurringScheduleConfig (see also the screenshot below)
- Right-click soa-infra (SOA_cluster_name)
- Choose SOA Administration > BPEL Properties
- Click "More BPEL Configuration Properties"
- Click "Recovery Config"
- Change values for RecurringScheduleConfig
- maxMessageRaiseSize = 0
- startWindowTime = 00:00
- stopWindowTime = 00:00
- Click Apply
2) Change StartupScheduleConfig (see also the screenshot below)
- Right-click soa-infra (SOA_cluster_name)
- Choose SOA Administration > BPEL Properties
- Click "More BPEL Configuration Properties"
- Click "Recovery Config"
- Change values forStartupScheduleConfig
- maxMessageRaiseSize = 0
- startupRecoveryDuration = 0
- subsequentTriggerDelay = 0
- Click Apply
3) Change GlobalTxMaxRetry
The property GlobalTxMaxRetry specifies how many retries are performed if an error is identified as a retriable one. For example, after several web service invocations, if dehydration fails due to a data source error, then this is identified as a retriable error and all activities from the prior dehydration state are retried. If the activities being retried are not idempotent (that is, their state can change with each retry and is not guaranteed to give the same behavior), then multiple retries can be problematic.
You can set GlobalTxMaxRetry to 0 in the Systems MBean Browser.
- Right-click soa-infra (SOA_cluster_name)
- Choose SOA Administration > Common Properties
- Click "More SOA Infra Advanced Configuration Properties"
- Click "GlobalTxMaxRetry"
- In the Value field, enter an appropriate value
- Click Apply
No comments:
Post a Comment