what happens when the database that is being accessed by the above binding component goes down?

Composite X invokes an outbound DB adapter to write data to a database table. You have
configured JCA at the binding component as follows:
<property name = “jca.retry.count” type = “xs:int” many = “false” override = “may” > 2</property>
<property name = “jca.retry.interval” type = “xs:int” many = “false” override = “may” > 2</property>
You have also modeled a modeled a fault policy to retry the invocation three times in case of
remoteFault as follows:
<retryCount>3<retryCount>

<retryInterval>3<retryInterval>
Which result describes what happens when the database that is being accessed by the above
binding component goes down?

A.
The invocation is retrieved for a total of two times every two seconds. Fault policy retries are
ignored.

B.
The invocation is retried for a total of six times every three seconds.

C.
The invocation is retried for a total of six times every two seconds.

D.
The fault policy retries occur within the JCA retries. So two JCA retries are executed two
seconds apart. Within each JCA retry, three fault policy retries are executed three seconds apart.

E.
The JCA retries occur within the fault policy retries. So three fault policy retries are executed
three seconds apart. Within each fault policy retry, two JCA retries are executed two seconds
apart.

Explanation:

Note:
* Global retries for any error handling are returned to the BPEL Receive activity instance, for
example, or, more generally, to the point at which the transaction started. Such a retry could occur
if there was an error such as a temporary database fault. The default retry count is by default
indefinite, or specified in the jca.retry.count property.
* Properties you can specify in the composite.xml file include:
/jca.retry.count
Specifies the maximum number of retries before rejection. Again, specifying this value is a prerequisite to specifying the other property values.
/jca.retry.interval
Specifies the time interval between retries (measured in seconds.)
* A remoteFault is also thrown inside an activity. It is thrown because the invocation fails. For
example, a SOAP fault is returned by the remote service.