On 20.06.2012 23:35, Lahiru Gunathilake wrote:
Hi Jeff,
Thanks for the response, actually my requirement is to make the life easier
for the admin, and if something goes wrong he has an ID of the request
which failed (This is not a system which is getting millions of http
requests) and then he
On 20/06/2012 22:39, Lahiru Gunathilake wrote:
Hi Caldarale,
Its not a website.. I am hosting a middleware which will be used by
scientist to run their application in the Grid. So Ideal scenario is like
2--30 requests per day but they are long running and very time consuming
(Some jobs
Are you sure of that, a single file for a single HTTP request. I don't know
a file system capable to handle that ?
Jeff
On Wed, Jun 20, 2012 at 10:38 PM, Lahiru Gunathilake glah...@gmail.comwrote:
Hi All,
I have my webapp deployed on tomcat. I am using slf4j for my logging and
everything
Hi Jeff,
Thanks for the response, actually my requirement is to make the life easier
for the admin, and if something goes wrong he has an ID of the request
which failed (This is not a system which is getting millions of http
requests) and then he should be able to figure out the logs for that
From: Lahiru Gunathilake [mailto:glah...@gmail.com]
Subject: Creating separate log for each request
I am using slf4j for my logging and everything works fine and all
the logs comes to catalina.out.
Which means that things are seriously broken or incredibly badly configured.
Logging
Hi Caldarale,
Its not a website.. I am hosting a middleware which will be used by
scientist to run their application in the Grid. So Ideal scenario is like
2--30 requests per day but they are long running and very time consuming
(Some jobs would take 2,3 days or one week to finish), so the logs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lahiru,
On 6/20/12 5:39 PM, Lahiru Gunathilake wrote:
Hi Caldarale,
Its not a website.. I am hosting a middleware which will be used
by scientist to run their application in the Grid. So Ideal
scenario is like 2--30 requests per day but they
