Re^2: Web Service using mod_perl with PerlTransHandler running out of threads

You are using a threaded version of Apache on Windows server? No wonder?

Amazing isn't it, esp since apache.org provides them, because they actually work on windows, because windows has better threads than linux

Comment on Re^2: Web Service using mod_perl with PerlTransHandler running out of threads

Replies are listed 'Best First'.
Re^3: Web Service using mod_perl with PerlTransHandler running out of threads by Anonymous Monk on May 17, 2012 at 04:32 UTC
Gee, and for all these years I thought the threaded model was a workaround for systems that didn't have fork.	[reply]
Re^3: Web Service using mod_perl with PerlTransHandler running out of threads by jswalker (Initiate) on May 18, 2012 at 14:06 UTC
Since the mix of Apache and Windows and mod_perl seems to have sparked some discussion - Is there some disconnect in these implementations (even though all of them are builds intended for the Win32 environment)? Some inherent instability? I'm game to fight this fight but not if it is a lost cause from the start. While we are on the topic is there anything suitable to this environment that would give me the sort of visibility of Apache processing that 'procmon' from the Windows sysinternals package provides for that environment? I am inclined to think I could resolve this if I had some way of seeing what is going on in there as Apache winds down to flatline. VMonitor is not an option. Apache::DB seems too 'down in the weeds' given that this is not a hard stop but a slow death. I am thinking I need to see the dynamics of what is going on with the various Apache threads but I haven't a clue yet on how to get that.	[reply]