The following error message is frequently written in the Foglight Management Server (FMS) log:
Request tag lost; data from this request will not be collected.
The JavaEE Agent follows a Tag and Follow approach and what it means is if a request flows from one JVM to another JVM, the agent follows through the request and creates one request that flows from JVM1 to JVM2. For the Tag and Follow flow, Both JVM1 and JVM2 should be instrumented and it should be connected to the same Nexus.
This error message indicates that Tag and Follow is broken. Sometimes, this flow can be broken, if the request tracking breaks somewhere in between.
There are are a few error messages that you may noticed about incomplete Request Timeout.
com.quest.pas.nexus.correlation.CompleteInProgressState - Incomplete request fragment received; switching to incomplete pending state.
This means tracking of a particular request stops after it reaches the timeout value (Default value is 2 minutes).
If this is the case, it is possible that some requests are taking more than 2 minutes; hence, the request tracking stops – and that can cause the Tag and Follow to break. So instead of seeing 1 request that flows from JVM1 to JVM2, you would now see 2 request types, one that originates from JVM1, and the second that originates from JVM2.
These errors are not harming your JVM, nor the agent. The timeout issue can be prevented by increasing the incomplete request timeout (IncompleteRequestTimeout) in the recording settings:
For Java Cartridge version 5.9.x and above:
Application Servers Administration | Nexus Administration | Recording Settngs | Nexus Recording | Edit | Advanced | IncompleteRequestTimeout
For Java Cartridge version pre 5.9.x:
The recording.config file can be located in the FMS Console: Administration | Agents | Agent Properties | JavaEE-Cartridge