RE: Latest lead on our Tomcat/BIRT performance issue

Those were my first two thoughts as well.

Also check in the domain information if the host name search priority is
*LOCAL or *REMOTE. If it's *REMOTE then it's spending time asking all of
the DNS servers in the list for a resolution of the IP address, then finally
getting back to the host table. OK if your DNS is fast and correct, bad if
it's not.

Setting it to *LOCAL with very few entries does not slow down other
processes that need DNS so it might solve this problem too.


--
Jim Oberholtzer
Agile Technology Architects


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Evan
Harris
Sent: Wednesday, February 08, 2017 12:07 PM
To: Midrange Systems Technical Discussion
Subject: Re: Latest lead on our Tomcat/BIRT performance issue

Wild-assed guesses here:
(1) Check whether the fully qualified system name is in the hosts table
(2) Check whether the rdb name matches the configured host name

On 9/02/2017 5:50 AM, "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
wrote:

We just recently got a new lead on our Tomcat/BIRT performance issue.
It seems that it's taking longer for code on the customer box to
establish a JDBC connection to the Host Server ports through the
Loopback ports than it takes us to establish that same connection from
the other side of the continent (and an unknown number of relays) away.

We know we can open a connection through these ports -- including
through JDBC -- in less than 1 second over the Internet from our IP
address. But somehow, making a connection from Java running on the
same physical box takes 5 or more seconds.

Any suggestions on an easy way to establish a test connection to the
Host Servers ports from ILE RPG or ILE C, without calling out to JAVA
to use JDBC?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at
http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD