FabricInvocationException_Error at the callback forCAVS Testing with AIA3.1

Question

While testing the ProviderABCS from CAVS with aTest Definition (With out simulator TD)
Steps followed for Testing a CAVS RequestorABCS
1. Created a Async 2 way response test definition
2. Updated the route to CAVS=true for the callback service in AIACOnfigurationProperties.xml file in AIA_Home/Metadata/Config location.
3. Ran the UpdatemetadaDP.xml
4. Did cross check with the Setup console of the CAVS and the route to CAVS is updated.
5. When the CAVS test is executed the response from the back end is coming as expected. But as the route to CAVS is enable to true it needs to route
the response to CAVS. Throwing the following.
Error in the RequestorABCS:
++Unable to invoke the end point http://<hostname:port>/AIAValidationSystemServlet/asyncresponserecipient++
But this endpoint is visible from the browser.
Error at the callback after the Requestor ABCS invoked:
FabricInvocationException :oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=UTF-8
Much appreciate your response in advance
Regards
Raj
Edited by: user10359791 on Aug 3, 2011 10:08 AM

Answer 1

Yes, This is accessible from SOA Server. The response is as
" This is Composite Application Validation System Http Soap Service."
Other workaround that i have done is :
Modified the url end point of Callback service to "http://xyz" --->Updated in AIAConfigurationproperties.xml file
The error it is giving @ callback is:
javax.xml.soap.SOAPException: javax.xml.soap.SOAPException: Message send failed: xyz
Before this trail the end point url of the callback service is given as :
http://<hostname:port>/AIAValidationSystemServlet/asyncresponserecipient
The error is is giving is:
javax.xml.soap.SOAPException: oracle.j2ee.ws.saaj.ContentTypeException: Not a valid SOAP Content-Type: text/html; charset=UTF-8
But with both the modifications the visibility of the error in cavs is the same:
Asynchronous Response Timeout - Correlation ID could not be mapped with any of the Delayed instances - (Try increasing the timeout time/check for correlation ID value in the response soap message).
We did increase the timeout and the correct correlation id is also given.
Edited by: user10359791 on Aug 3, 2011 2:18 PM