[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp-interop] Java dynamic domain name workaround
Andre Kramer <andre.kramer@eu.citrix.com>
06/24/2003 09:01 AM |
To: Rich Thompson/Watson/IBM@IBMUS, wsrp-interop@lists.oasis-open.org cc: Subject: RE: [wsrp-interop] Java dynamic domain name workaround |
David Ward <david.ward@oracle.com>
06/23/2003 06:11 PM | To: Richard Jacob <richard.jacob@de.ibm.com> cc: wsrp-interop@lists.oasis-open.org Subject: [wsrp-interop] Java dynamic domain name workaround |
This turned out to be due to the way Java caches IP addresses. The java.net.InetAddress class by default caches IP addresses forever once it has resolved them once. However, the IBM domain name wsrp.dyndns.org actually gets associated with a new IP address every 24 hours, so this was bound to cause problems for our servlet container JVM that stays up forever.
If we were running on JDK 1.4, it appears we would be able
to control the "time to live" for cached IP addresses through
a security
policy. However, it seems that the 'private'
sun.net.inetaddr.ttl System property mentioned
in the JDK 1.4 docs also has the same effect on JDK 1.3.
My solution was to edit the config file containing the startup options
for the servlet container JVM (in Oracle 9iAS this is in opmn/conf/opmn.xml)
so that the sun.net.inetaddr.ttl property is set with a small timeout (I
used 120 seconds).
E.g.
java -Dsun.net.inetaddr.ttl=120 <normal JVM startup options>
Regards
David
--
David Ward
Principal Software Engineer Oracle Portal | Oracle European Development Centre 520 Oracle Parkway Thames Valley Park Reading Berkshire RG6 1RA UK |
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]