search cancel

IFW sending empty SOAP message body


Article ID: 220876


Updated On:


CA Service Operations Insight (SOI) DX Application Performance Management



Investigation from APM has shown that the IFW on SOI manager machine is acting as a web services client.

But, in these calls, it cannot determine the service name or operation name. However the graph shows that it is a regular call happening every minute
Using APM debug logs, the soap message body is empty as shown in the log excerpts below: 
6/07/21 02:33:47 PM CEST [DEBUG] [IntroscopeAgent.Agent] Axis2ClientNameFormatter::getChild(data): soapBody=<soapenv:Body xmlns:soapenv="" />

6/07/21 02:33:47 PM CEST [DEBUG] [IntroscopeAgent.Agent] Axis2ClientNameFormatter::processInvocationData(data):  getChild(data) returns null; skip extracting namespace and operation info from SOAP object.
APM relies on the SOAP message body to determine namespace, operation names etc.
The part that could help to identify is seeing the information on the monitored SOI manager process which is formatted correctly
namespace is
with operation haveEvents
There's a need to understand if it is normal that the IFW is sending an empty SOAP body here.
The impact is also with APM monitoring not being able to determine data for the call, so returns metrics as unknown.



The haveEvents web service from the SOI side is checking for the below queues:








If all the above queues are empty then they will return blank response.

In this case, it simply returns Boolean values as false if everything is empty.

This is not impacting anything from the SOI side, this is expected behaviour.


Services and input information can be obtained using the below WSDL Url. 

As per haveEvents implementation, there is no input for this service.




Using a SOAP client, such as SOAP-UI, all the services can be found into that with the sample request.

A blank request provides the expected response from the service. 


<soapenv:Envelope xmlns:soapenv="">






Response :

<soapenv:Envelope xmlns:soapenv="">


      <ns:haveEventsResponse xmlns:ns="">





As an aside, details such as the namespace are visible in the body of the response, this is why the server side (WebServices|Server) of the APM monitoring of the SOI manager process is actually reporting correct values.


Release : 4.2

Component : Service Operations Insight (SOI) Generic Connector



So it is normal for IFW to send an empty SOAP body.

There is nothing that can be done on APM side in the current implementation, there is no way for it to determine the details of the webservice.


The GenericConnectorService in SOI has multiple web service operations, so it would be misleading to hard code the haveEvents call for the WebServices client in webservices.pbd configuration.