Very Computer

for example, we run the server Apache + JServe on Solaris. I can use
Solaris's "snoop" to diagnose traffic from apache to the outside, but
i if i use snoop to monitor the port Jserve is using to communicate
with Apache, snoop returns nothing.

i don't know much about unix sockets, but i suspect this is because
snoop only capture traffics that goes thru the physical network
interface card.

What really happens in my case is that browser stalls in the middle of
a particular web page in a site using our in-house application server
that involves apache + jserv and an in-house application server. I can
see when packets stalls between host and the browser client, but i
need to see which one of these application is responsible for the
stalling. So if i can see the traffic between Apache and JServe, or
between JServe and inhouse-server, that'll pinpoint my problem.

few weeks ago i learned about lsof here, but haven't studied it yet.
Would lsof be useful?

PS what's snoop equivalent in linux?

thanks.

 Xah

 http://xahlee.org/PageTwo_dir/more.html

Quote:>how to monitor localhost network socket traffic that does not go
>through a physical interface?

Quote:>for example, we run the server Apache + JServe on Solaris. I can use
>Solaris's "snoop" to diagnose traffic from apache to the outside, but
>i if i use snoop to monitor the port Jserve is using to communicate
>with Apache, snoop returns nothing.
...
>What really happens in my case is that browser stalls in the middle of
>a particular web page in a site using our in-house application server
>that involves apache + jserv and an in-house application server. I can
>see when packets stalls between host and the browser client, but i
>need to see which one of these application is responsible for the
>stalling. So if i can see the traffic between Apache and JServe, or
>between JServe and inhouse-server, that'll pinpoint my problem.

Another possibility might be (?) to temporarily move the JServe to another
machine, and log the traffic between two machines.

Yet another would be to run the JServe (or Apache) under "truss" to see
the I/O at system call level.

Quote:>PS what's snoop equivalent in linux?

snoop -d lo
gives
snoop: /dev/lo: No such file or directory

similar for tcpdump

snoop host localhost
sits there empty too; similar for tcpdump.
--

Thanks Juha for the suggestions.

We couldn't do the things you suggested, because this bug happens on
production and is only 50% reproducible with the one and only unique
account. (and it is through HTTPS, btw.)

I tried tcpdump on solaris and apparently it doesn't capture localhost
traffic either.

Thanks.

 Xah

 http://xahlee.org/PageTwo_dir/more.html

.