URL being inserted in packet headers

book

Article ID: 187027

calendar_today

Updated On:

Products

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

Issue/Introduction

Below is a packet trace taken from a request between a websphere 10.5 agent and our mainframe.  We noticed there are two header fields being inserted - the correlation id, and a path to an agent, including the webservice name that originated the call.

Has this always been in the packet?  The symptom described by the mainframe team is that the extra data causes packets to be split due to overall length, and the "host" field is being passed in a supplemental packet, causing a mainframe CWXN transaction burst when this occurs.

Is it possible to disable this URI/Agent part injection, without disabling the CorrID?

 

Data Below from packet trace

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

POST /hostbridge HTTP/1.1..Authorization: Basic XXXXXXXXXXXXXXXX

XXX=..CorID: F1E083280AC44071F745F8AEAF4E6E62,1:2,0,0,sawdggg

was02|WebSphere|1cell/SOA_02|WebServices|Server|

urn_//xxx1.org/channel/v1_0|getAccountDetails,1,AgAABEhIQ

gAAAAFGAAAAAQAAABFqYXZhLnV0aWwuSGFzaE1hcAAAAAxIQgAAAAJGAAAAAgAAA

BBqYXZhLmxhbmcuU3RyaW5nABZBcHBNY

XBDYWxsZXJNZXRob2ROYW1lSEIAAAADR

QAAAAIAK1dlYlNlcnZpY2UgYXQgaHR0c

F8vL29zYS1wcm9kLm5mY3UubmV0XzcxM

TdIQgAAAARFAAAAAgALQXBwTWFwQnRjS

WRIQgAAAAVFAAAAAgASNzAwMDAwMDAwM

DAwMDAxNDc1SEIAAAAGRQAAAAIAE0Nhb

Environment

Release : 10.7.0

Component : APM Agents

Resolution

 Use introscope.agent.crossprocess.correlationid.maxlimit agent property as the workaround configuration to keep the URI/Agent data part of CorID minimum.