On 9/24/25 10:30 AM, Mark Thomas wrote:
Make a bunch of requests that should get routed to that Tomcat instance but will result in 404s. Then check the access log for those URLs (they are hopefully unique) and see what IP address they are associated with.
Briefly, I was stumped by "access log," but realized that it was "localhost_access_log" for the current date.
Came back with 192.0.2.46, which (I see) is designated as a "test address." And this matches the address that seemed most likely out of the 50-odd addresses I got when I did a WRKTCPSTS.
But merely editing the context.xml didn't do anything. Which didn't surprise me much: Tomcat on IBM Midrange boxes tends to be "funny" that way, not resetting things on update, where it would on any other platform.
But I believe there's a nightly Tomcat restart, so I'm not all that concerned. Either it will work or it won't.
-- JHHL --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
