×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
On 4/15/22 10:37 AM, Christopher Schultz (of the Tomcat Users' List) wrote:
. . .
Try specifying the "address" attribute of <Server> along with the port.
Give it a concrete IP address instead of "localhost" and see if that
improves things.
. . .
My Dear Mr. Schultz:
That did it!
Not knowing whether to give it 127.0.0.1 or give it the box's actual IP
address, I gave it the former.
It works. And the connector is configured to listen on anything, so it
came up just fine, and is entirely visible from the outside world.
But that still leaves open the question of why an IBM Midrange box would
suddenly start disregarding its own host table. I've never heard of a
scenario in which *any* box with a TCP stack would disregard its own
host table (and indeed, on any box under my control that can browse the
Web, in which the host table is user-modifiable, I use host table
entries to ensure that I can't be tricked [it's happened, more than
once] into accessing Facebook, Twitter, LinkedIn, or a few other noisome
domains).
What can make a box disregard its own host table?
--
JHHL
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
