The message "(3) Tried to create session redirection cycle. Disallowing this redirect" is appearing in /var/log/ecrit
This message means that for the same TCP connection (which FxM is treating as a single user session) FxM is seeing different values for the SAME session identifier.
So, for example, let's say there is a TCP connection with hits coming through like this with the session identifier as shown
FxM can be pretty sure that is all the same user session. However, if it looks like this:
FxM can be pretty sure that these are not the same user session and that the customer's network is multiplexing sessions onto the same TCP connection. That's what generates the message.
Sessionize by Hit will almost always be the preferred configuration setting. But historically, FxM only had Sessionize by Connection and there were some apps where it was useful to tie together hits into a single session that would otherwise show up as multiple sessions. Those apps would change the session identifier value mid-stream during a TCP connection. PeopleSoft is an example of an application that showed this behavior. So this capability was added to FxM to allowing FxM to correlate hits from the same user into a single session when the session identifier changed in the middle of a connection.
So, if a customer is getting this message they should switch to Sessionize by Hit because their user sessions could be mixing traffic from different users. There would be no feature loss in switching the method except for the rare case that they might have an app that changes session identifiers mid-stream in a TCP connection. Even if they did, the hits are all still captured, they would just show up as 2 d
Change to Sessionize by Hit and it should't appear.