In this post, I am going to list of some of the problems
which I could remember; I have faced during SOA Suite 11g to SOA Suite 12c
migration for one the recent project which I have completed.
Problem1: 'jca.retry.count’ error
While running some of the composite, transaction was getting
rolled back with below error message –
Cannot parse JCA binding
retry property 'jca.retry.count', value '0' due to: Value of JCA binding retry
property
'jca.retry.count' must
be a positive number: Cannot parse JCA binding retry property
'jca.retry.count', value '0' due to:
Value of JCA binding
retry property 'jca.retry.count' must be a positive number</summary>
,code=<code>oracle.fabric.common.FabricException</code>
,detail=<detail>oracle.fabric.common.FabricException:
javax.resource.ResourceException: Cannot parse JCA binding
retry property
'jca.retry.count', value '0' due to: Value of JCA binding retry property
'jca.retry.count' must be a positive
number: Cannot parse JCA
binding retry property 'jca.retry.count', value '0' due to: Value of JCA
binding retry property
'jca.retry.count' must
be a positive number
at
oracle.integration.platform.blocks.event.jms2.EdnBus12c.publish(EdnBus12c.java:1438
Solution 1:
This error was coming because ‘0’ was set for “NumberofRetry”
located at this path
We have modified
soainfrastructure>>
SOA
Administration>> common properties>> More SOA Advance Configuration
Properties >> Application
Defined Beans >> oracle.as.soainfra.config>>EDNConfig>>edn
I believe some internal changes been made for EDN delivery
retry mechanism. Earlier as part of 11g, we were able to set “NumberOfRetry=0”
but when we carried forward same value for SOA Suite 12c then composite start
failing JCA error as listed above.
To fix this error we just change “NumberOfRetry =1” or any
positive number up to 5.
Note: Setting number of “NumberOfRetry” =1 does not retry
failed JCA transaction automatically.
Refer this document for detailed understanding about
different value of NumberOfRetry and its impact.
