Dinesh,
If accessing the Apache machine from other
machines on the network is slow you may have a missing reverse lookup entry in
your DNS. To test you might try the following from one of the slow
machines.
nslookup (hostname where Apache is
installed)
nslookup 192.168.1.2
The results from the two commands should
match. Another test would be to add the 192.168.1.2 host to the hosts file
on one of the slow machines and see if response time improves. Good luck.
From: Dinesh Kumar
[mailto:pdineshk@xxxxxxxxxxx]
Sent: Monday, March 17, 2008 1:35
AM
To: users@xxxxxxxxxxxxxxxx
Subject: Re: Access
is slow when accessed by IP address instead of 'localhost'
This is resolved - an
entry for 192.168.1.2 in the hosts file did it
for access from the *same* machine. Now, I'm trying to check how to
resolve the slow response time when accessed over the LAN.
Thanks to Adam & others who responded.
Regards,
Dinesh.
On Tue, Mar 11, 2008 at 8:13 PM, David Cassidy <david@xxxxxxxxxxxxx> wrote:
Sorry
and glad to hear it :)
On Tue, 2008-03-11 at 20:12 +0530, Nilesh Govindrajan wrote:
> On Tue, 11 Mar 2008 14:39:36 +0000
> David Cassidy <david@xxxxxxxxxxxxx>
wrote:
>
> > Nilesh
> >
> > Check if its doing a reverse lookup.
> >
> > you need DNS for that ...
> >
> > D
> >
> > On Tue, 2008-03-11 at 19:48 +0530, Nilesh Govindrajan wrote:
> > > On Tue, 11 Mar 2008 09:10:16 -0500
> > > "Adam Martin" <Adam.Martin@xxxxxxxxx> wrote:
> > >
> > > > Dinesh,
> > > >
> > > >
> > > >
> > > > When I started reading I thought you may be experiencing a
delay
> > > > with the host resolution but when you mentioned that you
could
> > > > access another Tomcat application using the IP Address it
doesn't
> > > > sound like you are.
> > > >
> > > >
> > > >
> > > > To be sure you may want to add the 192.168.1.2 host to your hosts
> > > > file on the server and make sure the server is set to
resolve
> > > > names locally before accessing DNS to see if it makes any
> > > > difference. Other than that I got zip. Good
luck.
> > > >
> > > >
> > > >
> > > > ________________________________
> > > >
> > > > From: Dinesh Kumar [mailto:pdineshk@xxxxxxxxxxx]
> > > > Sent: Tuesday, March 11, 2008 6:29 AM
> > > > To: users@xxxxxxxxxxxxxxxx
> > > > Subject: Access is slow when accessed by IP
address
> > > > instead of 'localhost'
> > > >
> > > >
> > > >
> > > > Hi all,
> > > >
> > > > I'm facing a peculiar problem. My environment is as
follows:
> > > >
> > > > Apache 2.2.4
> > > > mod_jk 1.2.23
> > > > Tomcat 6.0.13
> > > >
> > > > When I access the Java application running on Tomcat like
this:
> > > > curl http://localhost/community/forums/list.page, I get a
> > > > response within 1 second. However, when I access it
like this:
> > > > http://192.168.1.2/community/forums/list.page, the response
takes
> > > > 10 seconds.
> > > >
> > > > To be clear, in both the cases I'm accessing the
application from
> > > > the *same* machine that runs httpd/tomcat. I found
out about
> > > > this issue when I tried to access it from another machine
on the
> > > > same LAN, which is how it will be actually accessed when
the
> > > > issue is resolved. I tried to find out what happened when I
> > > > accessed it from the same machine on which it is running,
and
> > > > found that it behaves similarly as I mentioned above.
> > > >
> > > > 192.168.1.2
is on eth0, and eth0 is setup as a trusted device.
> > > > When I access another Tomcat 6 application running locally
like
> > > > this: curl http://192.168.1.2/recruit/admin, the request is
> > > > served instantly.
> > > >
> > > > The extra time occurs between the following lines of
mod_jk.log:
> > > >
> > > > [Mon Mar 10 17:03:54 2008] [7071:60304] [debug]
> > > > ajp_send_request::jk_ajp_common.c (1287): (forum) request
body to
> > > > send 0
> > > > - request body to resend 0
> > > > [Mon Mar 10 17:04:04 2008] [7071:60304] [debug]
> > > > ajp_connection_tcp_get_message::jk_ajp_common.c (1043):
received
> > > > from ajp13 pos=0 len=133 max=8192
> > > >
> > > > I thought it was something to do with mod_jk and installed
version
> > > > 1.2.26, but the problem persists.
> > > >
> > > > Any pointers would be welcome!
> > > >
> > > > Thanks,
> > > > Dinesh.
> > > >
> > >
> > > According to me, an IP address doesn't need the DNS to resolve
> > > something.
> > >
> >
> >
> > ---------------------------------------------------------------------
> > The official User-To-User support forum of the Apache HTTP Server
> > Project. See <URL:http://httpd.apache.org/userslist.html> for more
> > info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
> > " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
> > For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
> >
>
> I am not the guy who has the problem!!! BTW, I know that for Reverse
> lookups, a DNS is needed.
>
---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html>
for more info.
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
" from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|
