On 19/10/2012 08:43, Romain Van der Keilen wrote:
> Hi Guys,
>
>> After that, I looked deeper into the database configuration, as I saw
>> in the tests that non db relative actions were responding very fast
>> (50ms for a 1000 users basis). I finally found an OracleDataSource in
>> the Oracle D
Hi Guys,
> After that, I looked deeper into the database configuration, as I saw
> in the tests that non db relative actions were responding very fast
> (50ms for a 1000 users basis). I finally found an OracleDataSource in
> the Oracle Driver, which reacts far way better than the
> BasicDataSo
Ok guys, apologies for my inconvenience. I was just wondering if there was
a way to solve a few problems that I'm facing here like threads that
get stuck and no way to release them.
I already chat with my client's architechs in order to ask them if they are
closing any output source when downloadi
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel,
On 10/18/12 10:12 AM, Daniel Barcellos wrote:
ok... thanks for nothing...
No thanks for the snarkiness. :(
Pid's advice is actually good, even if you don't want to hear it:
2012/10/18 Pid
It's probably not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel,
On 10/18/12 10:12 AM, Daniel Barcellos wrote:
> ok... thanks for nothing...
No thanks for the snarkiness. :(
Pid's advice is actually good, even if you don't want to hear it:
> 2012/10/18 Pid
>
>> It's probably not your connector config t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Romain,
On 10/18/12 6:05 AM, Romain Van der Keilen wrote:
> After that, I looked deeper into the database configuration, as I
> saw in the tests that non db relative actions were responding very
> fast (50ms for a 1000 users basis). I finally found an
s for 150
> users for the basic data source, 1.5s for the oracle one, same test).
> >>
> >> So I think my problems are solved, thanks to you guys!
> >>
> >> Many thanks for the advices,
> >>
> >> Romain.
> >>
> >> -
Hi.
Romain Van der Keilen wrote:
Hi there!
Some news for you about my problem.
I did all the modifications you suggested, it increased the response time a
little bit (2-3 seconds better on a 15 seconds scale). It was already good to
take, and helped me to create a healthy configuration.
As
Driver, which reacts far
>> way better than the BasicDataSource I was using before (12s for 150 users
>> for the basic data source, 1.5s for the oracle one, same test).
>>
>> So I think my problems are solved, thanks to you guys!
>>
>> Many thanks for the adv
anks for the advices,
>
> Romain.
>
> -Original Message-
> From: André Warnier [mailto:a...@ice-sa.com]
> Sent: mercredi 17 octobre 2012 11:49
> To: Tomcat Users List
> Subject: Re: asking advice for tomcat 7 config
>
> Pid wrote:
> ...
>
>>>
&g
for tomcat 7 config
Pid wrote:
...
>>
>> > maxThreads="650" minSpareThreads="100" />
>> > maxHttpHeaderSize="8192"
>> protocol="org.apache.coyote.http11.Http11NioProtocol"
>>connectionTimeou
On 17/10/2012 11:36, André Warnier wrote:
> Mark Thomas wrote:
>> http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Connector_Comparison
> Thanks.
> Yes, I saw that table, but it is may be a bit "summarised" for the
> average Tomcat user (or sysadmin). Is there somewhere a more
> global/i
Mark Thomas wrote:
On 17/10/2012 11:02, André Warnier wrote:
Mark Thomas wrote:
On 17/10/2012 10:49, André Warnier wrote:
1) So it means that if a client connects to the server, but does not
send any request line for a while on that connection, the server will
allocate a thread to serve the re
On 17/10/2012 11:02, André Warnier wrote:
> Mark Thomas wrote:
>> On 17/10/2012 10:49, André Warnier wrote:
>>> 1) So it means that if a client connects to the server, but does not
>>> send any request line for a while on that connection, the server will
>>> allocate a thread to serve the request;
>You've configured a separate pool for connectors on ports 80 and 443. Why?
I thought it was better this way... Normally, the port 80 should automatically
redirect to the port 443 and https only should be authorized. Is there any
proper way to do that?
>You've reduced the acceptCount to 50. W
Mark Thomas wrote:
On 17/10/2012 10:49, André Warnier wrote:
1) So it means that if a client connects to the server, but does not
send any request line for a while on that connection, the server will
allocate a thread to serve the request; this thread will wait up to 20 s
(on HTTP) or 60 s. (on
On 17/10/2012 10:49, André Warnier wrote:
> 1) So it means that if a client connects to the server, but does not
> send any request line for a while on that connection, the server will
> allocate a thread to serve the request; this thread will wait up to 20 s
> (on HTTP) or 60 s. (on HTTPS), before
Pid wrote:
...
connectionTimeout="2" redirectPort="443" server="lighthttpd/2.0.0" enableLookups="false" acceptorThreadCount="4" socket.directBuffer="false"
compression="off" compressableMimeType="text/html,text/xml,text/plain,text/javascript,text/css,image/jpeg,
On 10/17/2012 1:28 AM, Mark Thomas wrote:
On 17/10/2012 07:59, Romain Van der Keilen wrote:
Hi There,
I'm quiet new to this mailing list as I encounter some configuration
problems with Tomcat 7.0.30.
It is unlikely to help but you may as well upgrade to 7.0.32.
We are currently developing a
On 17/10/2012 08:59, Romain Van der Keilen wrote:
> Hi There,
>
> I'm quiet new to this mailing list as I encounter some configuration problems
> with Tomcat 7.0.30.
> We are currently developing a web application, and we wish to have a good
> response time with about 200 parallel sessions. My p
On 17/10/2012 07:59, Romain Van der Keilen wrote:
> Hi There,
>
> I'm quiet new to this mailing list as I encounter some configuration
> problems with Tomcat 7.0.30.
It is unlikely to help but you may as well upgrade to 7.0.32.
> We are currently developing a web
> application, and we wish to ha
I have faced similar issues as well! I have quite similar tomcat6 over a
similar hardware infrastructure and sometimes we noticed some unavailable
issues as well!
I already tried tuning tomcat but not success! The only thing I did last time
was increase the maxthread from 200 to 500 and another
Hi There,
I'm quiet new to this mailing list as I encounter some configuration problems
with Tomcat 7.0.30.
We are currently developing a web application, and we wish to have a good
response time with about 200 parallel sessions. My problem is that starting
from 70 users, the system does not re
23 matches
Mail list logo
