Apache and Weblogic - Performance issue

Answer 1

Hi Anuj,
This question should be directed to the weblogic.developer.interest.plug-in
group.
Regarding this issue, this is normal -- the access.log for WebLogic shows
the requests from the proxy. But, instead of showing you the IP address of
the proxy server, it instead shows you the IP address of the client. You
can also verify that this is a different request because the connection to
the proxy server used HTTP/1.1, and the connection to WLS used HTTP/1.0 --
this is the protocol that the proxy plug-in uses to communicate with WLS.
So, in summary, there is only one request made by the client per image, and
the plug-in is in turn making a request to WLS for each image.
Dennis Munsie
Developer Relations Engineer
BEA Support
"Anuj Nijhawan" <[email protected]> wrote in message
news:3c20e890$[email protected]..
>
We have a setup with apache acting as web server and BEA as app server.But it
seems both of them are serving images to the web browser at the same time.This
is consuming lots of memory. Can anybody help rectifing this,
here's what each log file's say,
first Apache (access_log) shows that it served it up:
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET /img/divider.gif
HTTP/1.1"
304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/i_user_collection.gif
HTTP/1.1" 304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/sort_last_manual.gif H
Then BEA (access.log) shows it too:
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET /img/divider.gif
HTTP/1.0"
304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/i_user_collection.gif
HTTP/1.0" 304 0
172.20.100.142 - - [19/Dec/2001:01:20:24 -0800] "GET
/img/sort_manual.gif HTTP/1
.0" 304 0