We just had an issue with one of our java service applications where a client had changed the IP address of one of their domains, yet all our service code remained sending to the old address, a quick search finds mentioned on the InetAddress JavaDoc:

networkaddress.cache.ttl (default: -1)
Indicates the caching policy for successful name lookups from the name service. The value is specified as as integer to indicate the number of seconds to cache the successful lookup. A value of -1 indicates "cache forever".

Oh great, so by default java will forever cache looked up IP addresses.

links: digg this del.icio.us technorati reddit

comments (2)

1. a reader left...

Thursday, 1 July 2004 2:31 pm

For a client application, "forever" is probably okay. A server app can configure it, I guess.

Hey, at least it is configurable. :)

(Oh, and thanks for this; I've been wondering how to configure this feature)

Robert Watkins

2. a reader left...

Friday, 2 July 2004 7:10 am

JavaBlogs ha(s|d) this problem. I discovered it for a while when my blog had a proper name, but was on a dynamic ip. I used DynDns, which worked for everything else, but JavaBlogs would never get the new ip when it changed. Very annoying.

Joey Gibson

My Top Tags

My Jaiku

Chrome Division – Doomsday Rider

1 Session per VM: Another Scaling Alternative

The BGGA myth - Functional Java | Google Groups

Spock's Beard – On A Perfect Day (live)

Ola Bini: JtestR 0.3.1 Released

Tech Transit: PutPinfInItsPlace: An iTunes Plus fixer for Nokia mobile phones

Enslaved – Violet Dawning

Distributed Messaging with Jetlang and Terracotta

The Music of 2008 - week 33

There Can Be Only One

Recruitment

Search Box

Monthly Archives

Java InetAddress caching...