Re: log all traffic go to our web app server -- WEB400

Subject: Re: log all traffic go to our web app server
From: "Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx>
Date: Thu, 5 Mar 2009 09:23:54 -0600
List-archive: <http://archive.midrange.com/web400>
List-help: <mailto:web400-request@midrange.com?subject=help>
List-id: Web Enabling the AS400 / iSeries <web400.midrange.com>
List-post: <mailto:web400@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/web400>, <mailto:web400-request@midrange.com?subject=unsubscribe>

That is the problem, we do not know what is going on. Our admin is working with ibm on analyzing data generated from the JVM dump and JVM watch...

"Thorbjoern Ravn Andersen" <ravn@xxxxxxxxxx> wrote in message news:<mailman.7525.1236266386.26163.web400@xxxxxxxxxxxx>...

Lim Hock-Chai skrev:

So,... I really does not even know how to check if our JBOSS is
configure to work with Apache HTTP plug in. Will dig into it. Thanks
for all the help.

Consider using the tools for the JVM you are using to analyse what
exactly is going on at these spikes. It might be a slow response from
the database which cause requests to pile up waiting for database
answers so you need to know what is going on.

--
Thorbjørn Ravn Andersen "...plus... Tubular Bells!"

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: log all traffic go to our web app server , Thorbjoern Ravn Andersen

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.