Hi -
I've got to load test a clustered application server. External users of the application (whom JMeter must simulate) access it through a hardware load balancer. However, internal access goes through DNS Round Robin load balancing (implemented in Active Directory). This means that each DNS request to resolve a hostname will resolve to a different primary IP address. I understand that the JVM caches DNS lookups forever by default. This article implies that a JMeter load test accessing a cluster through the DNS Round Robin above, will only load test 1 node in the cluster as it caches the first name resolution it does: http://www.rgagnon.com/javadetails/java-0445.html Once an application has performed network access (i.e. urlconnection, parsing of xml document with external references, etc), the DNS settings get cached so any subsequent operation will use the old settings even if the real settings have changed. To reset everything, you have to restart the server since the default setting JVM setting is to cache forever. Is this true? How does this impact JMeter testing? I found this related bug on the Sun website. http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6376406 Kind regards, Sonam Chauhan -- Corporate Express Australia Ltd. Phone: +61-2-93350725, Email: [EMAIL PROTECTED]
