|
Ron,We have seen such a pattern with incorrect DNS-configurations. Try to add log statements (log4j is great for this) which let you determine where the time is spent.
First try to figure out of the live WAS server or the live SQL Server is
causing the problem - SQL Server might be retrieving the list in half a
second, and then WAS is locked up thinking about it for 55 seconds before
it decides to display anything.
As an Amazon Associate we earn from qualifying purchases.
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.