In Tomcat 4.x I've seen an "enableLookups" attribute on some of the
connectors can set in server.xml. Setting it to false would stop what
you're seeing. I've had a look in my old 3.2.1 config and don't see
anything similar.
A longshot and probably not the correct approach...The DNS timeouts
might be configurable at a JVM level. There used to be (maybe still
is ?) an issue where the JVM would cache the results of DNS lookups
and I know there was a switch (i.e. java property) to stop that behaviour.
...Peter
[EMAIL PROTECTED] writes:
> Hello guys,
>
> we are using cocoon 2.0.2 in a prototype and love the results. Implementation
> was fast and very efficient. However, there is one problem (or should I say
> challenge):
> whenever someone accesses cocoon over the internet from a client that does not
> have a DNS-entry (e.g. a client before a firewall at a IP-adress that has no
> name associated), cocoon is terribly slow The reason seems to be that cocoon
> performs reverse DNS-queries. If the nameserver does not find the right
> hostname, it takes a very long until a timeout is received by cocoon. Is there a
> way to turn that off?
>
> It seems like RequestSessionContext.buildMiscXML() calls Request.getRemoteHost()
> that calls InetAddress.getHostName() that triggers the host name lookup.
> OOur Config:
> Apache
> Tomcat 3.2
> Linux
>
> Thanks a lot for your help
>
> Ernst Nusterer
>
>
>
> ---------------------------------------------------------------------
> Please check that your question has not already been answered in the
> FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
>
> To unsubscribe, e-mail: <[EMAIL PROTECTED]>
> For additional commands, e-mail: <[EMAIL PROTECTED]>
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
