× 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.


  1.  Home
  2. MIDRANGE-L
  3. February 2017

SOLVED, Re: Latest lead on our Tomcat/BIRT performance issue

It turns out it WAS somehow related to DNS settings.

But I don't entirely understand what the customer (or maybe their TCP consultant?) said:

Their CFGTCP option 12 shows *LOCAL host name search priority.
Since [redacted] is in the host table, the OS should
not be querying the remote DNS. Even so, I tested the configured
DNS’s to see if they are responding to queries. I found [redacted]
is a valid host (responds to PING), but does not respond to NSLOOKUP
requests. I am removing it from the list.

The BIRT reports now respond at normal speed.

But if search priority is set to *LOCAL, (which it is), and the domain was in the host table (which it is), then why would it have even made a difference if there was a bad DNS address listed?

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.