Perhaps the term 'misconfigured network' IS a little bit harsh, but you
overlook a feature of DHCP which can alleviate this issue and is quite
necessary in a heterogenous network. DHCP can, after all update DNS with
the hostname - IP Address mappings needed automatically. So while your
enableLookups=false
sounds like a classically misconfigured DNS on the box that your
tomcat resides. it was trying to log host names but those were timing out
causing poor poor response in the server. this isn't a cocoon, tomcat,
or even an IE issue it's simply an artifact of a misconfigured
Jacob L E Blain Christen dijo:
enableLookups=false
it's simply an artifact of a misconfigured network
Not really, you can use WINS instaead of DNS inside your network. And that
does not mean that you have missconfigured your internal network.
DNS is a static file where the IP address are
Jacob L E Blain Christen dijo:
Jacob L E Blain Christen dijo:
enableLookups=false
it's simply an artifact of a misconfigured network
Not really, you can use WINS instaead of DNS inside your network. And
that
[snip]
so
again i will re-state that this issue concerns neither cocoon,
Hi to all!
I just want to share new info about the bad response time problem between
Tomcat 4.1.12 and MS IE 6.0.
I found that the performance of Tomcat can be improved setting the options:
enableLookups=false
tcpNoDelay=true
in the Connector className=org.apache.coyote.tomcat4.CoyoteConnector
