CorID header is much larger than it used to be
search cancel

CorID header is much larger than it used to be


Article ID: 142074


Updated On:


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


Looking at HTTP POST requests that are now being split across 2 packets. We are trying to identify why and found that the CorID name/value pair appears to be much larger than it used to be.  We are trying to identify what options made this data so much larger in the CorID value than it used to be. 


1. What makes a CorID larger?

2. What does it contain?

3. What is the impact of truncating the CorID?



All Supported Releases.


Possible causes are given in the resolution.


1. The CorID header size could become much larger due to the length of the name path to identify the outgoing cross process caller component/node and more often the size and number of optional parameters listed at the end of the header.

2. If the CorID header was truncated by a specified size limit, then the last part of the CorID header would be impact and most likely it would be just the optional parameters used for better processing and optimizing the showing of correlation edges in appmap. Transaction trace correlation should still work ok.