hill_t
New Contributor
Joined 9 years ago
User Profile
User Widgets
Contributions
Re: Setting for endpoint dns cache
We found a solution to this issue so I wanted to post it here in case someone else was searching for something similar and found my post. Changed the value of networkaddress.cache.ttl property in java.security from -1 to 0. This property indicates how many seconds to cache the most recent successful lookup. A value of -1 means to "cache forever" and a 0 means "never cache".6.5KViews1like0CommentsRe: Setting for endpoint dns cache
Yes, we could do something like that where we try and IP and if it is not available to we try another. However, part of the point of this test is to make sure we are redirected correctly when one set of servers is taken offline. So doing something within our tests would really defeat the purpose in this case.6.4KViews0likes1CommentRe: Setting for endpoint dns cache
We are doing a test where one set of servers is taken offline and we should start using the other set of servers that is still available. New tests initiated at that point will correctly go to the set of servers still online but tests already running do not appear to query the dns again and continue to go to the old servers. I was looking for a way to force it to query the dns at a more frequent interval.6.5KViews0likes3CommentsSetting for endpoint dns cache
Is there any way to control the dns cache settings for Load UI tests? The issue is when testing with network changes going on we want to ensure that requests do not continue to go to one server if it is no longer available. Does anyone have experience with controlling this either through Ready API! settings or a system setting?Solved6.6KViews0likes5Comments