You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Konstantin Preißer <ve...@t-online.de> on 2012/03/16 16:27:54 UTC
IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
Hi all,
I have a system with Windows Server 2008 32 bit, IIS 7.0, Java 1.7.0_03, Tomcat 7.0.26 and the ISAPI redirector.
Since I updated the ISAPI redirector from 1.2.32 to 1.2.33, it seems that each time when IIS tries to recycle its application pool, the IIS worker process (w3wp.exe) crashes in isapi_redirect.dll. In the event log, an "Application Error" of w3wp.exe is logged (here is an English translation):
Faulty application w3wp.exe, Version 7.0.6002.18005, time stamp 0x49e023cf, faulty module isapi_redirect.dll, Version 1.2.33.0, time stamp 0x4f59be7d, exception code 0xc0000005, error offset 0x0002bb16, process ID 0x10f0, application start time 01cd0336e5b7824a.
(The process ID does not match the one of w3wp.exe before the crash, nor the one after the crash, so it seems a bit like when the new w3wp.exe is launched after recycle, it crashes and immediately another w3wp.exe is started).
In the ISAPI log, following lines appear when w3wp.exe crashes:
[Fri Mar 16 06:37:38.402 2012] [4336:6828] [error] ajp_worker_factory::jk_ajp_common.c (3006): allocating ajp worker record from shared memory
[Fri Mar 16 06:37:38.417 2012] [4336:6828] [error] wc_create_worker::jk_worker.c (150): factory for ajp13 failed for worker1
[Fri Mar 16 06:37:38.426 2012] [4336:6828] [error] build_worker_map::jk_worker.c (261): failed to create worker worker1
[Fri Mar 16 06:37:38.434 2012] [4336:6828] [error] extension_fix::jk_uri_worker_map.c (554): Could not find worker with name 'worker1' in uri map post processing.
Any idea what these lines could mean / that caused them? Note that it seems that after the crash (when a new w3wp.exe is created), pages are served fine again (though I do not know what happens with request that are made exactly in the time when IIS resets the app pool).
The crashes and these log lines didn't appear in ISAPI 1.2.32.
I think I read somewhere in the thread "Issues with the tomcat connector (On W2k8 + IIS7.5)" about some change in the ISAPI connector which has to do with shared memory, but I'm not sure.
Thanks!
Regards,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/19/2012 12:00 AM, Alex Samad - Yieldbroker wrote:
> Hi
>
> Sorry it failed for me, started up, but I got some error messages
>
> [Mon Mar 19 09:43:13.970 2012] [2096:2984] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
This is caused by unable to allocate the buffer.
Now, it seems either memory is exhausted or shared memory still wrong (I recon its later)
>
> [Mon Mar 19 09:49:52.489 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (158): enter
> [Mon Mar 19 09:49:52.489 2012] [5804:5836] [debug] jk_shm_open::jk_shm.c (305): Initialized shared memory Global\JK_DEV_YIELDBROKER_COM_2_JAKARTA_ISAPI_REDIRECT size=1856 free=1728 addr=0x1f0000
> [Mon Mar 19 09:49:52.489 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (311): exit
> [Mon Mar 19 09:49:52.504 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (158): enter
> [Mon Mar 19 09:49:52.504 2012] [5804:5836] [debug] jk_shm_open::jk_shm.c (166): Shared memory is already opened
> [Mon Mar 19 09:49:52.504 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (167): exit
That's weird. jk_shm_open gets called twice from the same process/thread.
Could you send me some more log data surrounding those two calls so I can figure out from
where init_jk was called.
Please use the newest build (#6)
from http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
> -----Original Message-----
> From: Mladen Turk [mailto:mturk@apache.org]
> Sent: Tuesday, 20 March 2012 5:57 PM
> To: users@tomcat.apache.org
> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
> redirector 1.2.33
>
> On 03/20/2012 06:55 AM, Alex Samad - Yieldbroker wrote:
> >
> >
> >>
> >> You should
> >> 1. Create a separate 'Unmanaged' application pool for isapi_redirect
> >> 2. Disable recycling for that pool 3. Have multiple vhost mapping
> >> inside uriworkermap.properties instead
> >> having multiple configuration files and instances for each vhost.
> >> 4. Use a single process for that pool.
> >
> > Okay I can see that
> > Our original thinking was if we separate prd and uat, they could not affect
> each other.
> >
>
> Sure that's probably the only reason to have multiple instances and pools.
> However this still does not require multiple worker processes or recycling.
Yep, I think the recycling and worker process was a hangover from the move from weblogic to tomcat (and iis 6.x)
>
> >
> > :) true, but I don't believe the above is true on IIS/Windows.
> > The think I am unsure on is how the connector uses the shared memory
> > If its index (?) by the name of the worker thread or loadbalancer name then
> there will be a problem.
> >
> > I have the same config in UAT and PRD.. and thus the same worker names
> > and load balancer names
> >
>
> You will need to have /jakarta inside different 'Site' and each site bound to its
> own AppPool.
yep
> Shared memory is constructed from site name, so for example for 'Default Web
> Site'
> it becomes something like JK_LOCALHOST_1_...
>
> Suppose you have that separated already between production and staging.
Yep
So on the NLB / RP
I have
C:\ABC\<ENV>
Each env has
\wwwroot
\apjconfig
\other stuff
Apjconfig has the dll and the configs
Each environment has its own virtual site and each site has its own application pool
Thanks very much for your help on this
Alex
>
>
> Regards
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/20/2012 06:55 AM, Alex Samad - Yieldbroker wrote:
>
>
>>
>> You should
>> 1. Create a separate 'Unmanaged' application pool for isapi_redirect 2. Disable
>> recycling for that pool 3. Have multiple vhost mapping inside
>> uriworkermap.properties instead
>> having multiple configuration files and instances for each vhost.
>> 4. Use a single process for that pool.
>
> Okay I can see that
> Our original thinking was if we separate prd and uat, they could not affect each other.
>
Sure that's probably the only reason to have multiple instances and pools.
However this still does not require multiple worker processes or recycling.
>
> :) true, but I don't believe the above is true on IIS/Windows.
> The think I am unsure on is how the connector uses the shared memory
> If its index (?) by the name of the worker thread or loadbalancer name then there will be a problem.
>
> I have the same config in UAT and PRD.. and thus the same worker names and load balancer names
>
You will need to have /jakarta inside different 'Site' and each site bound to its own AppPool.
Shared memory is constructed from site name, so for example for 'Default Web Site'
it becomes something like JK_LOCALHOST_1_...
Suppose you have that separated already between production and staging.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
> -----Original Message-----
> From: Mladen Turk [mailto:mturk@apache.org]
> Sent: Tuesday, 20 March 2012 4:09 PM
> To: users@tomcat.apache.org
> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
> redirector 1.2.33
>
> On 03/20/2012 02:01 AM, Alex Samad - Yieldbroker wrote:
> > This has me thinking and think I have found another bug. :)
> >
> > Our setup is IIS 7.5 setup as a Reverse proxy. We run PRD, UAT
> > through here. Trying to treat this an infrastructure box. We have 2 in
> > a NLB setup
> >
> > For each environment I have a separate web server and directory setup
> > so
> >
> > C:\ABC\
> > Prod\
> > Ajpconfig\
> > UAT\
> > Ajpconfig\
> >
> > In each environment I have a ajpconfig directory where I put my dll and I keep
> all my config files for just that environment.
> >
> > The idea was that I could have different version of the tomcat connector thus
> test stuff out in UAT and then move on to PRD.
> >
> > BUT there is no way to set the name space used in the tomcat connector in
> relation to the Shared Memory or to semaphore.
> >
> > So Global\\JK_ISAPI_REDIRECT_MUTEX is used by all tomcat connectors
> > (the ones in prod and the ones in UAT)
> >
>
> Yes, but thats used only inside jk_init and locks for 1ms during new worker
> process creation while the isapi_redirect gets loaded to memory.
>
> Like explained in BZ52659 you have things conceptually wrong.
> isapi_redirect is proxy, it does its own connection pool management, recycling,
> virtual host mapping handling etc.
I'm a linux guy stuck in a MS world :)
>
> You should
> 1. Create a separate 'Unmanaged' application pool for isapi_redirect 2. Disable
> recycling for that pool 3. Have multiple vhost mapping inside
> uriworkermap.properties instead
> having multiple configuration files and instances for each vhost.
> 4. Use a single process for that pool.
Okay I can see that
Our original thinking was if we separate prd and uat, they could not affect each other.
Say for example right now where I want to test the new connector
I have tested on dev, but the spec of the machine is not the same as the prod/uat setup
I can't have separating logging all the prd/uat/sim will go into 1 set of files
Apart for the separation of prod and testing Minor.
>
> You can eventually have two separate pools (one for testing and other for
> production)
>
>
> > And I would presume the Shared Memory would also be shared between the 2
> ?
> >
> > Quote from the doco !
> > " The ISAPI redirector can read it's configuration from a properties file instead
> of the registry. This has the advantage that you can use multiple ISAPI
> redirectors with independent configurations on the same server. The redirector
> will check for the properties file during initialisation, and use it in preference to
> the registry if present."
> >
>
> If something is possible it doesn't mean you should use it in production and in all
> cases.
:) true, but I don't believe the above is true on IIS/Windows.
The think I am unsure on is how the connector uses the shared memory
If its index (?) by the name of the worker thread or loadbalancer name then there will be a problem.
I have the same config in UAT and PRD.. and thus the same worker names and load balancer names
If its worker name and dest server ip (this I believe to be more likely) then it should be okay...
>
> > You can't do this with the IIS connector and with multiple processes (web
> gardens)!
> >
>
> Again, you should think 'differently'
> Entire IIS worker process recycling is meant for handling crappy .NET
> applications with memory and resource leaks.
> isapi_redirect is proxy, nothing else, nothing more.
Yep understand, it was out tool for invoking this bug, as it also happened upon reboot of the server or restart of IIS
>
>
>
> Regards
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/20/2012 02:01 AM, Alex Samad - Yieldbroker wrote:
> This has me thinking and think I have found another bug. :)
>
> Our setup is IIS 7.5 setup as a Reverse proxy. We run PRD, UAT through here. Trying to treat this an infrastructure box. We have 2 in a NLB setup
>
> For each environment I have a separate web server and directory setup so
>
> C:\ABC\
> Prod\
> Ajpconfig\
> UAT\
> Ajpconfig\
>
> In each environment I have a ajpconfig directory where I put my dll and I keep all my config files for just that environment.
>
> The idea was that I could have different version of the tomcat connector thus test stuff out in UAT and then move on to PRD.
>
> BUT there is no way to set the name space used in the tomcat connector in relation to the Shared Memory or to semaphore.
>
> So Global\\JK_ISAPI_REDIRECT_MUTEX is used by all tomcat connectors (the ones in prod and the ones in UAT)
>
Yes, but thats used only inside jk_init and locks for 1ms during new worker process creation
while the isapi_redirect gets loaded to memory.
Like explained in BZ52659 you have things conceptually wrong.
isapi_redirect is proxy, it does its own connection pool management, recycling,
virtual host mapping handling etc.
You should
1. Create a separate 'Unmanaged' application pool for isapi_redirect
2. Disable recycling for that pool
3. Have multiple vhost mapping inside uriworkermap.properties instead
having multiple configuration files and instances for each vhost.
4. Use a single process for that pool.
You can eventually have two separate pools (one for testing and other for production)
> And I would presume the Shared Memory would also be shared between the 2 ?
>
> Quote from the doco !
> " The ISAPI redirector can read it's configuration from a properties file instead of the registry. This has the advantage that you can use multiple ISAPI redirectors with independent configurations on the same server. The redirector will check for the properties file during initialisation, and use it in preference to the registry if present."
>
If something is possible it doesn't mean you should use it in production and in all cases.
> You can't do this with the IIS connector and with multiple processes (web gardens)!
>
Again, you should think 'differently'
Entire IIS worker process recycling is meant for handling crappy .NET applications with memory and resource leaks.
isapi_redirect is proxy, nothing else, nothing more.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
> -----Original Message-----
> From: Alex Samad - Yieldbroker [mailto:Alex.Samad@yieldbroker.com]
[snip]
>
> Hi Mladen
>
> Q) can I presume that this new version will not interfere with an old version
> 1.2.32 ? as the mutex name used in this new one 1.2.34 wasn't used in 1.2.32 ?
This has me thinking and think I have found another bug. :)
Our setup is IIS 7.5 setup as a Reverse proxy. We run PRD, UAT through here. Trying to treat this an infrastructure box. We have 2 in a NLB setup
For each environment I have a separate web server and directory setup so
C:\ABC\
Prod\
Ajpconfig\
UAT\
Ajpconfig\
In each environment I have a ajpconfig directory where I put my dll and I keep all my config files for just that environment.
The idea was that I could have different version of the tomcat connector thus test stuff out in UAT and then move on to PRD.
BUT there is no way to set the name space used in the tomcat connector in relation to the Shared Memory or to semaphore.
So Global\\JK_ISAPI_REDIRECT_MUTEX is used by all tomcat connectors (the ones in prod and the ones in UAT)
And I would presume the Shared Memory would also be shared between the 2 ?
Quote from the doco !
" The ISAPI redirector can read it's configuration from a properties file instead of the registry. This has the advantage that you can use multiple ISAPI redirectors with independent configurations on the same server. The redirector will check for the properties file during initialisation, and use it in preference to the registry if present."
You can't do this with the IIS connector and with multiple processes (web gardens)!
Could I make a bug/feature request to add something like
Shm_namespace
To the isapi_redirect.properties file and have this value post fixed to the shared memory name and the semaphore handle... Doesn't make sense if configured via the registry
I have create a bugzilla for this https://issues.apache.org/bugzilla/show_bug.cgi?id=52947 basically outlining what I have here. The one thing I am not sure of is how much of a problem that is...
The config files for uat and prd have different tomcat destinations, but the load balancer and worker names are the same !! The pathing is different though
The previous bug which I think this version fixes is https://issues.apache.org/bugzilla/show_bug.cgi?id=52659 which I guess can be closed
Thanks
>
> Alex
>
> -----Original Message-----
> From: Alex Samad - Yieldbroker [mailto:Alex.Samad@yieldbroker.com]
[snip]
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
Hi Mladen
Q) can I presume that this new version will not interfere with an old version 1.2.32 ? as the mutex name used in this new one 1.2.34 wasn't used in 1.2.32 ?
Alex
-----Original Message-----
From: Alex Samad - Yieldbroker [mailto:Alex.Samad@yieldbroker.com]
Sent: Tuesday, 20 March 2012 11:13 AM
To: Tomcat Users List
Subject: RE: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
Hi
Thanks, looks like this one is the winner !
Alex
-----Original Message-----
From: Mladen Turk [mailto:mturk@apache.org]
Sent: Tuesday, 20 March 2012 1:43 AM
To: Tomcat Users List
Cc: Alex Samad - Yieldbroker
Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
On 03/19/2012 12:00 AM, Alex Samad - Yieldbroker wrote:
> Hi
> [Mon Mar 19 09:43:53.266 2012] [2516:1892] [error]
> service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
Please use the newest build (#8)
from http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
There was a bug in shared memory sync caused by attaching new process while there was request pending In general caused by 'generation in future'.
Now the shared memory is synced only if we are below the shared sequence.
I have verified locally that it works now and no more those alloc failed errors (as well as none of the earlier one :)
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
B KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKCB [ X ܚX KK[XZ[
\ \ ][ X ܚX P X ]
\X K ܙ B ܈Y][ۘ[ [X[ K[XZ[
\ \ Z[ X ]
\X K ܙ B
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
Hi
Thanks, looks like this one is the winner !
Alex
-----Original Message-----
From: Mladen Turk [mailto:mturk@apache.org]
Sent: Tuesday, 20 March 2012 1:43 AM
To: Tomcat Users List
Cc: Alex Samad - Yieldbroker
Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
On 03/19/2012 12:00 AM, Alex Samad - Yieldbroker wrote:
> Hi
> [Mon Mar 19 09:43:53.266 2012] [2516:1892] [error]
> service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
Please use the newest build (#8)
from http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
There was a bug in shared memory sync caused by attaching new process while there was request pending In general caused by 'generation in future'.
Now the shared memory is synced only if we are below the shared sequence.
I have verified locally that it works now and no more those alloc failed errors (as well as none of the earlier one :)
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/19/2012 12:00 AM, Alex Samad - Yieldbroker wrote:
> Hi
> [Mon Mar 19 09:43:53.266 2012] [2516:1892] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
Please use the newest build (#8)
from http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
There was a bug in shared memory sync caused by attaching
new process while there was request pending
In general caused by 'generation in future'.
Now the shared memory is synced only if we are below the
shared sequence.
I have verified locally that it works now and no more those
alloc failed errors (as well as none of the earlier one :)
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
Hi
Sorry it failed for me, started up, but I got some error messages
I have 4 processes setup for non-overlapping recycle
Log 1
Log 2
[Mon Mar 19 09:43:13.970 2012] [2096:2984] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:13.986 2012] [2096:2984] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
[Mon Mar 19 09:43:14.079 2012] [2096:2984] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:14.079 2012] [2096:2984] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
[Mon Mar 19 09:43:53.453 2012] [2096:2288] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:53.453 2012] [2096:2288] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
Log3
[Mon Mar 19 09:43:53.359 2012] [3388:2244] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:53.359 2012] [3388:2244] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
[Mon Mar 19 09:43:53.391 2012] [3388:2276] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:53.391 2012] [3388:2276] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
[Mon Mar 19 09:43:53.484 2012] [3388:2244] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:53.484 2012] [3388:2244] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
Log4
[Mon Mar 19 09:43:53.266 2012] [2516:1892] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:53.313 2012] [2516:1892] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
[Mon Mar 19 09:43:53.359 2012] [2516:2776] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:53.359 2012] [2516:2776] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
[Mon Mar 19 09:43:53.500 2012] [2516:2776] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:43:53.547 2012] [2516:2776] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
I started IIS, used my client app to connect.. that worked well, only 4 connects, then started my stress test, with 500 users. Basically 500 users connecting to IIS. Failed with these errors. Using performance monitor I can see that the number of ISAPI Extension requests is increasing
I turned on trace ( I can send you the files if you needed) and it seemed to work okay (I wonder if the serialisation into logging has something to do with it !
Found these
[Mon Mar 19 09:49:52.489 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (158): enter
[Mon Mar 19 09:49:52.489 2012] [5804:5836] [debug] jk_shm_open::jk_shm.c (305): Initialized shared memory Global\JK_DEV_YIELDBROKER_COM_2_JAKARTA_ISAPI_REDIRECT size=1856 free=1728 addr=0x1f0000
[Mon Mar 19 09:49:52.489 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (311): exit
[Mon Mar 19 09:49:52.504 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (158): enter
[Mon Mar 19 09:49:52.504 2012] [5804:5836] [debug] jk_shm_open::jk_shm.c (166): Shared memory is already opened
[Mon Mar 19 09:49:52.504 2012] [5804:5836] [trace] jk_shm_open::jk_shm.c (167): exit
[Mon Mar 19 09:49:52.504 2012] [5804:5836] [trace] wc_open::jk_worker.c (50): enter
[Mon Mar 19 09:49:52.504 2012] [5804:5836] [debug] jk_map_dump::jk_map.c (589): Dump of map: 'worker.maintain' -> '60'
I still have a lot of stale ISAPA extension request's
I have tried to restart IIS, whilst my client is trying to talk over 500 connections, with failed request tracking on I get 500/200 ?
Notification 128 Internal Server Error
Only 1 of the 4 logs files has this is there
[Mon Mar 19 09:58:27.878 2012] [2620:4636] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:58:27.894 2012] [2620:4636] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
[Mon Mar 19 09:58:27.910 2012] [2620:4636] [error] service::jk_lb_worker.c (1172): Failed allocating AJP message buffer
[Mon Mar 19 09:58:27.910 2012] [2620:4636] [error] HttpExtensionProc::jk_isapi_plugin.c (2325): service() failed with http error 500
Thanks
Alex
-----Original Message-----
From: Mladen Turk [mailto:mturk@apache.org]
Sent: Monday, 19 March 2012 8:34 AM
To: users@tomcat.apache.org
Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
On 03/18/2012 09:34 PM, verlag.preisser@t-online.de wrote:
> -----Original-Nachricht-----
>> Von: Mladen Turk<mt...@apache.org>
>> An: users@tomcat.apache.org
>> Betreff: Re: IIS 7.0 Worker process crashes on App Pool recycling
>> since ISAPI redirector 1.2.33
>> Datum: Sun, 18 Mar 2012 18:39:15 +0100
>>
>> Could you please try the isapi_redirect_1.2.34_5-dev_win32.zip
>> If this one crashes we'll have to add some override to shared memory
>> so we can fallback to heap one and bypass memory corruption which
>> seems to occur at IIS worker recycle.
>
> Hi Mladen,
>
> thank you, I tried isapi_redirect_1.2.34_5-dev_win32.zip and so far no crashes, and also no warnings/errors in the ISAPI log.
> It seems the issue is fixed now.
>
Cool. Thanks again for testing those.
We'll release 1.2.34 by the end of this week probably.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/18/2012 09:34 PM, verlag.preisser@t-online.de wrote:
> -----Original-Nachricht-----
>> Von: Mladen Turk<mt...@apache.org>
>> An: users@tomcat.apache.org
>> Betreff: Re: IIS 7.0 Worker process crashes on App Pool recycling
>> since ISAPI redirector 1.2.33
>> Datum: Sun, 18 Mar 2012 18:39:15 +0100
>>
>> Could you please try the isapi_redirect_1.2.34_5-dev_win32.zip
>> If this one crashes we'll have to add some override to shared memory
>> so we can fallback to heap one and bypass memory corruption which
>> seems to occur at IIS worker recycle.
>
> Hi Mladen,
>
> thank you, I tried isapi_redirect_1.2.34_5-dev_win32.zip and so far no crashes, and also no warnings/errors in the ISAPI log.
> It seems the issue is fixed now.
>
Cool. Thanks again for testing those.
We'll release 1.2.34 by the end of this week probably.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by "verlag.preisser@t-online.de" <ve...@t-online.de>.
-----Original-Nachricht-----
> Von: Mladen Turk <mt...@apache.org>
> An: users@tomcat.apache.org
> Betreff: Re: IIS 7.0 Worker process crashes on App Pool recycling
> since ISAPI redirector 1.2.33
> Datum: Sun, 18 Mar 2012 18:39:15 +0100
>
> Could you please try the isapi_redirect_1.2.34_5-dev_win32.zip
> If this one crashes we'll have to add some override to shared memory
> so we can fallback to heap one and bypass memory corruption which
> seems to occur at IIS worker recycle.
Hi Mladen,
thank you, I tried isapi_redirect_1.2.34_5-dev_win32.zip and so far no crashes, and also no warnings/errors in the ISAPI log.
It seems the issue is fixed now.
Thanks,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
[snip]
> > Just wondering (thinking a bit left field), but question was asked of me.
> Any reason to have a shm across processes.
> >
>
> So that worker state is replicated across processes.
> Eg, if connection to one backend is broken each process will have to discover
> that by itself. Shared memory allows that if one worker process discovers
> that a backend is down other won't have to go trough the lengthy process of
> discovering that.
>
> Also loadbalancer load factors are calculated across all processes not just for
> the current one. So, the benefits are real.
Not deny that, just thinking out aloud, also been asking myself if there is any reason to run a 4 process web garden. The only benefit I can see is that if 1 process dies there will be other process to continue processing.
1 process + threads v's X processes + threads
>
> However unlike with httpd, IIS does not offer parent/child concept so we
> don't have the shared memory 'controller'.
> The ultimate solution would be to start a separate controller process, but
> that's probably something for the future.
>
> Even if the current set of patches work, I'm more convinced we should have
> a directive to disable shared memory usage, and think I'm going to add that
> option for 1.2.34 anyhow.
So would that effectively do what I was suggesting above ?
Thanks
>
>
> Regards
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/18/2012 08:30 PM, Alex Samad - Yieldbroker wrote:
> Hi
>
> Guys (Konstantin, Mladen), goo d work, sorry caught me on a Sunday, else I would have chipped in.
>
> Just wondering (thinking a bit left field), but question was asked of me. Any reason to have a shm across processes.
>
So that worker state is replicated across processes.
Eg, if connection to one backend is broken each process will
have to discover that by itself. Shared memory allows that if
one worker process discovers that a backend is down other won't
have to go trough the lengthy process of discovering that.
Also loadbalancer load factors are calculated across all processes
not just for the current one. So, the benefits are real.
However unlike with httpd, IIS does not offer parent/child
concept so we don't have the shared memory 'controller'.
The ultimate solution would be to start a separate controller
process, but that's probably something for the future.
Even if the current set of patches work, I'm more convinced
we should have a directive to disable shared memory usage, and
think I'm going to add that option for 1.2.34 anyhow.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
Hi
Guys (Konstantin, Mladen), goo d work, sorry caught me on a Sunday, else I would have chipped in.
Just wondering (thinking a bit left field), but question was asked of me. Any reason to have a shm across processes.
We already have threading inside each worker process. What are the benefits of connection pool sharing across process, compared to just keeping them in process.
Alex
> -----Original Message-----
> From: Mladen Turk [mailto:mturk@apache.org]
> Sent: Monday, 19 March 2012 4:39 AM
> To: users@tomcat.apache.org
> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
> redirector 1.2.33
>
> On 03/18/2012 03:11 PM, Konstantin Preißer wrote:
> > Hi Mladen,
> >
> >> -----Original Message-----
> >> From: Mladen Turk [mailto:mturk@apache.org]
> >> Sent: Sunday, March 18, 2012 2:54 PM
> >> To: Tomcat Users List
> >> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling
> >> since ISAPI redirector 1.2.33
> >>
> >>
> >> Please use isapi_redirect_1.2.34_3-dev_winXX.zip instead.
> >
> > Thank you.
> >
> > I tried with isapi_redirect_1.2.34_3-dev_win32.zip, but unfortunately
> > it seems that it causes w3wp.exe to crash again :(
> >
>
> Could you please try the isapi_redirect_1.2.34_5-dev_win32.zip
> If this one crashes we'll have to add some override to shared memory so we
> can fallback to heap one and bypass memory corruption which seems to
> occur at IIS worker recycle.
>
>
> Regards
> --
> ^TM
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/18/2012 03:11 PM, Konstantin Preißer wrote:
> Hi Mladen,
>
>> -----Original Message-----
>> From: Mladen Turk [mailto:mturk@apache.org]
>> Sent: Sunday, March 18, 2012 2:54 PM
>> To: Tomcat Users List
>> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since
>> ISAPI redirector 1.2.33
>>
>>
>> Please use isapi_redirect_1.2.34_3-dev_winXX.zip instead.
>
> Thank you.
>
> I tried with isapi_redirect_1.2.34_3-dev_win32.zip, but unfortunately it seems that it causes w3wp.exe to crash again :(
>
Could you please try the isapi_redirect_1.2.34_5-dev_win32.zip
If this one crashes we'll have to add some override to shared memory so we can fallback
to heap one and bypass memory corruption which seems to occur at IIS worker recycle.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
Posted by Konstantin Preißer <ve...@t-online.de>.
Hi Mladen,
> -----Original Message-----
> From: Mladen Turk [mailto:mturk@apache.org]
> Sent: Sunday, March 18, 2012 2:54 PM
> To: Tomcat Users List
> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since
> ISAPI redirector 1.2.33
>
>
> Please use isapi_redirect_1.2.34_3-dev_winXX.zip instead.
Thank you.
I tried with isapi_redirect_1.2.34_3-dev_win32.zip, but unfortunately it seems that it causes w3wp.exe to crash again :(
Logs:
[Sun Mar 18 15:05:48.648 2012] [7588:5124] [error] ajp_worker_factory::jk_ajp_common.c (3006): allocating ajp worker record from shared memory
[Sun Mar 18 15:05:48.661 2012] [7588:5124] [error] wc_create_worker::jk_worker.c (150): factory for ajp13 failed for worker1
[Sun Mar 18 15:05:48.669 2012] [7588:5124] [error] build_worker_map::jk_worker.c (261): failed to create worker worker1
[Sun Mar 18 15:05:48.677 2012] [7588:5124] [error] extension_fix::jk_uri_worker_map.c (554): Could not find worker with name 'worker1' in uri map post processing.
Thanks,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/18/2012 02:40 PM, Mladen Turk wrote:
> On 03/18/2012 02:34 PM, Mladen Turk wrote:
>> On 03/18/2012 12:16 PM, Konstantin Preißer wrote:
>>> Hello Mladen,
>>>
>>>
>>> Thank you very much. I tried the new version, and now when the Application Pool is recycled, the logs show these:
>>>
>>> [Sun Mar 18 12:10:36.324 2012] [4144:6216] [error] jk_shm_open::jk_shm.c (220): Failed to map shared memory JK_TTWEBINFO_DYNDNS_ORG_8_JAKARTA2_ISAPI_REDIRECT with errno=87
>>> [Sun Mar 18 12:10:36.337 2012] [4144:6216] [error] init_jk::jk_isapi_plugin.c (2801): Initializing shm:(null) errno=87. Load balancer will not work properly!
>>>
>>> But w3wp.exe doesn't crash anymore, so I think it is fixed. (I'm wondering now why mapping the shared memory fails..)
>>>
>>
>> Thanks for looking at this promptly!
>>
>> Could you try with the new builds
>> http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
>> (isapi_redirect_1.2.34_2-dev_winXX.zip)
>>
>
Please use isapi_redirect_1.2.34_3-dev_winXX.zip instead.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/18/2012 02:34 PM, Mladen Turk wrote:
> On 03/18/2012 12:16 PM, Konstantin Preißer wrote:
>> Hello Mladen,
>>
>>
>> Thank you very much. I tried the new version, and now when the Application Pool is recycled, the logs show these:
>>
>> [Sun Mar 18 12:10:36.324 2012] [4144:6216] [error] jk_shm_open::jk_shm.c (220): Failed to map shared memory JK_TTWEBINFO_DYNDNS_ORG_8_JAKARTA2_ISAPI_REDIRECT with errno=87
>> [Sun Mar 18 12:10:36.337 2012] [4144:6216] [error] init_jk::jk_isapi_plugin.c (2801): Initializing shm:(null) errno=87. Load balancer will not work properly!
>>
>> But w3wp.exe doesn't crash anymore, so I think it is fixed. (I'm wondering now why mapping the shared memory fails..)
>>
>
> Thanks for looking at this promptly!
>
> Could you try with the new builds
> http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
> (isapi_redirect_1.2.34_2-dev_winXX.zip)
>
Forget about that one. I'll create a new one in 20 minutes
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/18/2012 12:16 PM, Konstantin Preißer wrote:
> Hello Mladen,
>
>
> Thank you very much. I tried the new version, and now when the Application Pool is recycled, the logs show these:
>
> [Sun Mar 18 12:10:36.324 2012] [4144:6216] [error] jk_shm_open::jk_shm.c (220): Failed to map shared memory JK_TTWEBINFO_DYNDNS_ORG_8_JAKARTA2_ISAPI_REDIRECT with errno=87
> [Sun Mar 18 12:10:36.337 2012] [4144:6216] [error] init_jk::jk_isapi_plugin.c (2801): Initializing shm:(null) errno=87. Load balancer will not work properly!
>
> But w3wp.exe doesn't crash anymore, so I think it is fixed. (I'm wondering now why mapping the shared memory fails..)
>
Thanks for looking at this promptly!
Could you try with the new builds
http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
(isapi_redirect_1.2.34_2-dev_winXX.zip)
I added Global\\ prefix to shared memory name so that it can
be shared from multiple processes.
Also check if the errno changed from 87 (ERROR_INVALID_PARAMETER)
Thanks
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
Posted by Konstantin Preißer <ve...@t-online.de>.
Hello Mladen,
> -----Original Message-----
> From: Mladen Turk [mailto:mturk@apache.org]
> Sent: Sunday, March 18, 2012 8:46 AM
> To: users@tomcat.apache.org
> Cc: verlag.preisser@t-online.de; Alex.Samad@yieldbroker.com
> Subject: Re: IIS 7.0 Worker process crashes on App Pool recycling since
> ISAPI redirector 1.2.33
>
>
> Guys,
>
> Please try the binaries from:
> http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
>
> They contain two fixes:
> 1. Make sure we fallback to heap memory in case shared cannot be
> created
> 2. Fix shared memory create/open arguments
>
> The point is that is that we should have correct [error] log
> entries in case shared memory open fails.
> If it fails you should have [warn] line, load balancer will not
> function properly across multiple processes (will inside each of the
> process)
> but it shouldn't crash.
>
Thank you very much. I tried the new version, and now when the Application Pool is recycled, the logs show these:
[Sun Mar 18 12:10:36.324 2012] [4144:6216] [error] jk_shm_open::jk_shm.c (220): Failed to map shared memory JK_TTWEBINFO_DYNDNS_ORG_8_JAKARTA2_ISAPI_REDIRECT with errno=87
[Sun Mar 18 12:10:36.337 2012] [4144:6216] [error] init_jk::jk_isapi_plugin.c (2801): Initializing shm:(null) errno=87. Load balancer will not work properly!
But w3wp.exe doesn't crash anymore, so I think it is fixed. (I'm wondering now why mapping the shared memory fails..)
Thanks,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
redirector 1.2.33
Posted by Mladen Turk <mt...@apache.org>.
On 03/16/2012 04:27 PM, Konstantin Preißer wrote:
> Hi all,
>
> I have a system with Windows Server 2008 32 bit, IIS 7.0, Java 1.7.0_03, Tomcat 7.0.26 and the ISAPI redirector.
>
Guys,
Please try the binaries from:
http://people.apache.org/~mturk/tomcat-connectors/jk-1.2.34/
They contain two fixes:
1. Make sure we fallback to heap memory in case shared cannot be created
2. Fix shared memory create/open arguments
The point is that is that we should have correct [error] log
entries in case shared memory open fails.
If it fails you should have [warn] line, load balancer will not
function properly across multiple processes (will inside each of the process)
but it shouldn't crash.
I'd appreciate if you can check that ASAP cause we have regression in httpd
implementation so new version will be out in couple of days.
Regards
--
^TM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
[snip]
> >
> > Hi
> >
> > 1.2.32 was doing that for me.. 1.2.33 was meant to fix it, but I can't
> > get 1.2.33 to load.
> >
> > Do you use overlapping recycle and a web garden ?
> >
> > Alex
> >
>
> Thanks for your reply.
> I don't think I'm using a web garden - I just have one application pool for all
> virtual hosts which use the ISAPI redirector, and that application pool consists
> of a maximum of 1 worker process (the default IIS values). It is set to be
> recycled every 1740 minutes, and "disallowOverlappingRotation" for that
> pool is set to "false" - I guess that means I'm using overlapping recycle (a new
> w3wp.exe is started which takes new requests, and after all old requests are
> finished, the old w3wp.exe will be stopped).
The 1 processor thread is the key. The problem I summarised with 1.2.32 is that the shared memory is not protected by a OS semaphore, but an in process semaphore... 1.2.33 was mean to address this by changing from an inprocess semaphore to a OS semaphore.
I am surprised you have 1.2.33 loading and working, every time I try to load it crashes out on me.
Only quick solution I can think is that you move back to 1.2.32 :)
You might want to trial the system under load. I found that if you had about 500 connections all try and reconnect at the same time with overlapping recycling it would corrupt the sharememory it was a bit of a silent killer for us.
>
> Thanks,
> Konstantin Preißer
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
Posted by Konstantin Preißer <ve...@t-online.de>.
Hi Alex,
> -----Original Message-----
> From: Alex Samad - Yieldbroker [mailto:Alex.Samad@yieldbroker.com]
> Sent: Friday, March 16, 2012 5:23 PM
> To: Tomcat Users List
> Subject: RE: IIS 7.0 Worker process crashes on App Pool recycling since
> ISAPI redirector 1.2.33
>
> Hi
>
> 1.2.32 was doing that for me.. 1.2.33 was meant to fix it, but I can't
> get 1.2.33 to load.
>
> Do you use overlapping recycle and a web garden ?
>
> Alex
>
Thanks for your reply.
I don't think I'm using a web garden - I just have one application pool for all virtual hosts which use the ISAPI redirector, and that application pool consists of a maximum of 1 worker process (the default IIS values). It is set to be recycled every 1740 minutes, and "disallowOverlappingRotation" for that pool is set to "false" - I guess that means I'm using overlapping recycle (a new w3wp.exe is started which takes new requests, and after all old requests are finished, the old w3wp.exe will be stopped).
Thanks,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since
ISAPI redirector 1.2.33
Posted by Alex Samad - Yieldbroker <Al...@yieldbroker.com>.
> -----Original Message-----
> From: Konstantin Preißer [mailto:verlag.preisser@t-online.de]
> Sent: Saturday, 17 March 2012 2:31 AM
> To: 'Tomcat Users List'
> Subject: RE: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI
> redirector 1.2.33
>
> >
> > Any idea what these lines could mean / that caused them? Note that it
> > seems that after the crash (when a new w3wp.exe is created), pages are
> > served fine again (though I do not know what happens with request that
> > are made exactly in the time when IIS resets the app pool).
> > The crashes and these log lines didn't appear in ISAPI 1.2.32.
Hi
1.2.32 was doing that for me.. 1.2.33 was meant to fix it, but I can't get 1.2.33 to load.
Do you use overlapping recycle and a web garden ?
Alex
> >
>
> Sorry, forgot to post my configuration:
>
> uriworkersmap.properties:
>
> /*=worker1
>
>
> workers.properties:
>
> # Define 1 real worker using ajp13
> worker.list=worker1
> # Set properties for worker1 (ajp13)
> worker.worker1.type=ajp13
> worker.worker1.host=localhost
> worker.worker1.port=8019
>
>
> Thanks,
> Konstantin Preißer
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: IIS 7.0 Worker process crashes on App Pool recycling since ISAPI redirector 1.2.33
Posted by Konstantin Preißer <ve...@t-online.de>.
>
> Any idea what these lines could mean / that caused them? Note that it
> seems that after the crash (when a new w3wp.exe is created), pages are
> served fine again (though I do not know what happens with request that
> are made exactly in the time when IIS resets the app pool).
> The crashes and these log lines didn't appear in ISAPI 1.2.32.
>
Sorry, forgot to post my configuration:
uriworkersmap.properties:
/*=worker1
workers.properties:
# Define 1 real worker using ajp13
worker.list=worker1
# Set properties for worker1 (ajp13)
worker.worker1.type=ajp13
worker.worker1.host=localhost
worker.worker1.port=8019
Thanks,
Konstantin Preißer
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org