Hi , there are several reasons for this
A) did anything change on agile end ? Like the pwd or user used to update the eco ?
B) try restarting agile and then soa . When they are out of sync this issue can occur
C) was this working before ,? Is this first time you are seeing the issue ?
D) send me the error log

This is a known issue . Also policies might need to be updated if a composite was redeployed

Hi Rama,

Thanks for your Reply.

A) No Nothing has changed.suddenly we are seeing this issue.
B)This step is already done.
C)Its the first time, we are seeing
D)This is the error Log:

com.oracle.bpel.client.BPELFault: faultName: {{http://schemas.oracle.com/bpel/extension}remoteFault} messageType: {{http://schemas.oracle.com/bpel/extension}RuntimeFaultMessage} parts: {{ summary=<summary>oracle.fabric.common.FabricInvocationException: Unable to invoke endpoint URI “http://set.at.runtime” successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: set.at.runtime: Name or service not known</summary> ,detail=<detail>Unable to invoke endpoint URI “http://set.at.runtime” successfully due to: javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: set.at.runtime: Name or service not known</detail> ,code=<code>null</code>} *—-Previous error has caused the below error—-* AGILE XREF ERROR – An error has occurred in the Agile requester that may have prevented the Agile cross reference records from being written in the ITEM_ITEMID and CHANGE_CHANGEID tables. If there are no Agile XREF records for the ECO and item(s) that were sent, manual intervention MUST be done to fix this issue. First, the original issue that caused the requester to fail must be corrected. Second, the ECO that was sent to the provider application needs to be removed from the provider application. Third, the provider (e.g. EBIZ or JDEE1) and common XREF records should be removed from the ITEM_ITEMID and CHANGE_CHANGEID tables for the ECO and item(s). If these steps are not done, the ECO cannot be resubmitted from the queue, as that ECO and item(s) will already exist in the provider edge application.

Thank you.