Problem |
Potential
solution / explanation |
Error
parsing HTTP response:Reached end of stream while reading HTTP
response header |
This error
occurs when the connector invokes a SOAP/HTTP web service. It
occurs because your target web service sent an incorrect HTTP
response. Solution: make sure your target SOAP/HTTP web service end
point address is correct. |
Error in
the url mentioned , unable to extract host and port details
,destination is wrong <destination URL> |
This error
occurs when the connector invokes an SOAP/HTTP Web Service. It
occurs because you have specified an incorrect end point address
for the SOAP/HTTP web service. Solution: make sure you have
specified the correct end point address for the web service. |
Failure in
sending event business object <BO Name> with verb
<Verb> to the broker. Received execution status "-1"
and error message:
MapException: Unable to find the map to map
business objects <BO Name> for the connector
controller WebServicesConnector
. |
This error
occurs when the integration broker fails to process the event
because the collaboration to which the connector is sending the
event synchronously either does not exist or does not accept the
business object verb. Solution: if you are using a web services TLO
for event notification, examine the ws_collab object-level
ASI of the TLO. (The name of the TLO is given in the error
message.) Check the value of the ws_collab ASI. Make sure
this collaboration exists and is running. If ws_mode BO
level ASI is set to synch, ws_collab ASI is
required. Check the value of ws_verb object-level ASI.
Make sure the collaboration specified by the ws_collab ASI
can be triggered by the verb specified in the ws_verb ASI.
If you are using a non-TLO for event notification, examine the
WSCollaborations connector property. Find the collaboration that
will be invoked synchronously by this business object. Make sure
this collaboration exists and is running. |
Failed to
transform a soap request into a request business object. Soap
Fault:
Failure in generating request object -
no verb could be set on the request bo
|
This error
occurs during event notification when the connector is unable to
determine the verb of the business object that the connector is
attempting to send to the integration broker. Solution: if you are
using a web services TLO for event notification, make sure you have
specified ws_verb object-level ASI for this TLO. Specify
the verb as the value of this ASI. If you are using a non-TLO for
event notification, the SOAP message sent by your web service
client must contain the verb element. The SOAP data handler sets
the verb of the business object using the value of the verb element
in the SOAP message.If the web service client does not send the
verb in the SOAP message, the SOAP data handler cannot set the verb
on the business object. In this case, the connector cannot deliver
the business object to the integration broker. If you suspect that
your web service clients may not include a verb element in the SOAP
message, you may provide a DefaultVerb verb-level ASI for
this business object. If you do so, the connector sets this verb on
the business object before sending it to the integration
broker. |