Greetings.
I am experimenting with the (alpha level, I know) thread support of modperl2
on winnt.
While the server does no longer block on outstanding modperl requests (I can
request static pages while modperling: this was not possible on 1.x), it
wouldappear that multiple requests to the interpeter lock it up.
My handler counts to 20 while sleeping 1 sec.
I test concurrency by loading a frameset pointing to the same handler (from
different locations, say /counter1/ and /counter2.).
This locks all the modperl locations from any client indefinitely (so it
looks its'deadlocking, not serializing).
I am using AS perl build 630 -
C\> perl -MConfig -e "print $Config{useithreads}"
define
The relevant config part is:
KeepAlive Off
PerlOptions +Parent
PerlInterpStart 4
PerlInterpMax 20
PerlInterpMinSpare 2
PerlInterpMaxRequests 5000
PerlInterpScope handler # or request, makes no difference.
I have tried also without KeepAlivve and PerlInterpScope directives, with no
change.
looking at /server-status/ I can see that all the requests to modperl get
stuckin a 'W' status.
I've tried to configure a /perl-status/ location - but, Apache::Status
complainsquite loudly (any way to get it working?).
And lastly - is ths stuff OT on this list? Should I be posting to the user
listinstead?
Cheers,
alf
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
