You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tomcat.apache.org by bu...@apache.org on 2003/10/23 20:54:34 UTC

DO NOT REPLY [Bug 24075] New: - mod_jk will not resolve hostnames

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24075>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24075

mod_jk will not resolve hostnames

           Summary: mod_jk will not resolve hostnames
           Product: Tomcat 4
           Version: 4.1.24
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:JK/AJP (deprecated)
        AssignedTo: tomcat-dev@jakarta.apache.org
        ReportedBy: josh@betterway.net


I just installed mod_jk on apache 2.0.47 and was unable to connect to tomcat. I
knew tomcat was configured correctly because I had an older apache 1.3
distribution with mod_jk on the same machine connecting to the same tomcat with
no problems. After some debugging and code fiddeling, I found out that my
hostname of "localhost" wasn't getting resolved. When I put in 127.0.0.1
instead, it worked fine.

I know this module is deprecated, but I hope this will help others with this
connector.

-Josh

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org