ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to prevent Java agent modifying the SOAP header for WebService calls


Article ID: 238240


Updated On:


DX Application Performance Management CA Application Performance Management (APM / Wily / Introscope) CA Application Performance Management Agent (APM / Wily / Introscope)


We are using  APM Java agent with Websphere and need to prevent SOAP header manipulation by the agent

The following property values were set


but the SOAP header still had the correlation id inserted causing the application to fail and we are seeing the following error in the application which sows the header is present

XSD: [ParserException]: The following errors occurred during the XSD check of the sent XML message: 
Line: 1 - Position: 251 - Could not find schema information for the element
''. # Line: 1 - Position: 299 - Could not find schema information
for the attribute 'CorID'. [ParserError=XSD, RawData=<soapenv:Envelope
xmlns:soapenc="" xmlns:soapenv=""
xmlns:xsd="" xmlns:xsi=""><soapenv:Header>
<WSCorIDSOAPHeader xmlns= CorID="96AD3D29AC138310B86D32CE7098395D,1:1,0,0



Not all tracers adhere to the property settings and need to be manually disabled


Release : 10.7.0

Component : Introscope


The SOAP header insertion was prevented by commenting the following tracer in spm-correlation.pbd 

TraceOneMethodWithParametersIfFlagged: ApacheCXFJaxWSClientTracing invokeSync(Ljava/lang/reflect/Method;Lorg/apache/cxf/service/model/BindingOperationInfo;[Ljava/lang/Object;)Ljava/lang/Object; ApacheCXFJaxWSSyncClientCorrTracer "WebServices"
A defect has been raised for the tracer to be corrected to observe the property settings