On 12.09.2012 01:52, Alex Samad - Yieldbroker wrote:
okay.. worked it out.
Seems like I had the application pool set to no .net framework... and
integrated pipeline NOT classic.
But it seem if you don't set a .net it uses the old IIS6 ISAPI reg settings !
So now I have set .net framework to 4 , even though the plugin doesn't use it
(I presume)
and the thread count is over the 264.....
oh yeah.....
the pain of using IIS !
Thanks for sharing the solution.
Rainer
-----Original Message-----
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Sent: Tuesday, 11 September 2012 7:54 AM
To: Tomcat Users List
Subject: Re: IIS 7.5 + AJP Connector
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Alex,
On 9/9/12 10:35 PM, Alex Samad - Yieldbroker wrote:
-----Original Message----- From: Martin Gainty
[mailto:mgai...@hotmail.com] Sent: Monday, 10 September 2012
12:11 PM To: Tomcat Users List Subject: RE: IIS 7.5 + AJP Connector
Alex
connection_pool_size is usually for pooling algorithms such as DBCP..
Are you following the DBCP configuration doc?
http://commons.apache.org/dbcp/configuration.html
? so I am looking at the AJP Connector used in IIS on Windows. I
believe this is the relevant page
http://tomcat.apache.org/connectors-doc/reference/workers.html
I believe the connection_pool_size is an indication of how many
(max) worker threads are used to connect from IIS+AJP to tomcat ...
So I am not sure how the BDCP is going to help me, as there is no ODBC
connectivity from my RP's
Just ignore Martin: he is posting random bits of information from teh
intarwebs. His comments are not relevant to your question and you can
pretend they were never offered.
- -chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org