Souvik, I have a different take: a couple, in fact. Sorry it's not a brief answer, but given what's been said so far, it seems this will take some digging into.
1) Following up on the client var aspect (as Priyank and BKBK pursued), I notice also that the stack trace includes mention of the Tomcat remoteipvalve. Perhaps something is amiss with the result of that valve's processing that confuses the client var processing (though I'd think the latter cares only about cookies, not ip addresses).
a) Anyway, that valve is not implemented in cf by default, so you or someone there enabled that (in the server.xml of cf, which I discuss here). I could certainly see a connection between that and the random nature of your problem, perhaps based on the nature of an incoming request.
Have you tried removing it? Even if you "need it", I mean to suggest you consider removing it even if only temporarily, at least long enough to see if you'd get past however frequently you've been seeing this error.
b) If you "can't change that", a next step could be to observe what the ip is when it happens. But it's not as simple as looking at the apache log. Since you're using the remoteipvalve, that would mean you get requests through some proxy or firewall, such that the "real" ip is provided by that in a header, and the valve is used to extract that (in tomcat and for cf). Apache's log would likely report instead the ip of the proxy or firewall, which would not help us to solve this. (You could also look into configuring apache to log based on the ip headers also.)
Or if you may have fusionreactor, it can show you the headers (I don't think the PMT tracks headers)--and? Fusionreactor can also be configured to show and log the ip based on those headers, as I discuss here.
2) If none of the above helps, there may be other characteristics about your situation that we should understand, lest we make any mistaken presumptions:
- What version of apache are you running?
- is it running running in the same container as cf?
- Is this using Adobe's cf image or one you built?
- If you built it, did you implement cf in the image using the full installer or the zip approach that's new to 2021?
- Is that Ajp (cf/web server) connection configuration one that you built by running the cf wsconfig tool, or something you created by hand?
- Have you run your combination of cf and apache as containers outside of aci?
3) Finally, as a real shot in the dark, have you considered NOT using Ajp, but instead configure apache (or any other web server or ingress) to just forward requests to the internal (tomcat) web server within CF at port 8500?
That's possible and supported. I show doing that (with nginx, without Ajp) here. While that shows configuring cf images via docker compose, the general idea can be implemented without it.
Again, sorry for the brain dump folks. But since the problem seems a knotty one, these these are where the clues so far would take me.
/Charlie (troubleshooter, carehart. org)
14
Replies
AdChoices