>From some of the test cases I can safely say that tomcat is hitting some
limits, I have two test cases ran with two diff size of payload and without
any queryParams. The servlet is a empty servlet just returns after
receiving without doing any business side logic
h2load -n100 -c1 -m1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
John,
On 3/5/19 15:25, John Dale wrote:
> On 3/5/19, youness.dakk...@bnpparibasfortis.com
> wrote:
>> /logs/stderr.log
>
> I do not typically use that log file .. have you searched other
> log files in the tomcat/logs/* directory?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Helena,
On 3/6/19 03:07, Helena Carbajo wrote:
>> Getting closer but my question still stands. What problem are you
>> trying to solve.
>
>> Note that by the time startTime is set, a thread has been
>> allocated so it won't give you the time you
Is there reference to this file in the tomcat startup output? Are you
*sure* that this is being loaded?
On 3/6/19, youness.dakk...@bnpparibasfortis.com
wrote:
> This is the content of the log4j.properties file:
>
> # Root logger
> # console will log to console (local tomcat) or stdout.log im
When you run your test(s), does it fail after a certain period of
time, or just keep on going under a certain number of requests?
Also, to confirm: you're sending 1000 Byte + query strings?
Are you doing anything in the server side component to verify that
your parameters have been received
Greetings;
>From Mark below:
"by the time startTime is set, a thread has been allocated so it won't
give you the time you are looking for"
Are you building Tomcat from source? If so, you could instrument the
code in another location (I'm not exactly sure where that would be, so
I would have to
Dear Apache Enthusiast,
(You’re receiving this because you are subscribed to one or more user
mailing lists for an Apache Software Foundation project.)
TL;DR:
* Apache Roadshow DC is in 3 weeks. Register now at
https://apachecon.com/usroadshowdc19/
* Registration for Apache Roadshow Chicago is
>are you looking to measure request handling time?
>if so, startTime will not give you what you need since threads get
>reused by many requests.
Sorry, I don't really understand what you mean. From what I see in the code
the start time is set in Http11InputBuffer when processing the request
This is the content of the log4j.properties file:
# Root logger
# console will log to console (local tomcat) or stdout.log im Tomcat/logs
log4j.rootLogger=ALL, console
# Console appender.
log4j.appender.console=org.apache.log4j.ConsoleAppender
I hope so, I used updated packages/components at the time of development.
few may be outdated like tomcat native as I was using 1.2.18 while
developing but 1.2.21 got released recently.
On Wed, Mar 6, 2019 at 6:18 PM John Dale wrote:
> Have you upgraded to the most recent release of your major
Have you upgraded to the most recent release of your major version?
If so, and if this issue still persists, it is something that the core
development team might want to look at assuming they can replicate the
issue.
On 3/5/19, Santhosh Kumar wrote:
> Sometimes more than 10x
>
> On Tue, Mar 5,
are you looking to measure request handling time?
if so, startTime will not give you what you need since threads get
reused by many requests.
Sincerely,
John
On 3/6/19, Helena Carbajo wrote:
> >I want to know how much time my requests have to wait before they are
> handle, but I finally
Check your log4j configuration .. make sure it's got a console
appender configured (based on the log file names, it would seem like a
console logger will be required). If you can, try to post up your
log4j configuration .. there will be key classes for logging within
tomcat that must be enabled.
>I want to know how much time my requests have to wait before they are
handle, but I finally manage to get it by inheritance. I just had to create
the class in the same package.
Sorry to ask again about the same issue. It seems that creating the class
in the same package is not an ideal solution
Those are the files on tomcat/logs/*
- commons-daemon.-MM-DD.log
- tomcat.gc.log
- stdout.log
- stderr.log
This Tomcat is used inside SAP Business Objects.
My questions are:
- How we can get better logs on Tomcat ?
- Do you already had that kind of behaviour --> From HTPPS you get a blank
>Getting closer but my question still stands. What problem are you trying
>to solve.
>Note that by the time startTime is set, a thread has been allocated so
>it won't give you the time you are looking for.
I want to know how much time my requests have to wait before they are
handle, but I
16 matches
Mail list logo
