The mpm module (prefork.c) ... will just not do

The mpm module (prefork.c) ... will just not do

by Alex Jordan -
Number of replies: 1
I'm installing WeBWorK on Oracle 8. In patrolling the apache error log, I find:

[Mon Sep 12 10:02:14.079169 2022] [http2:warn] [pid 224343] AH10034: The mpm module (prefork.c) is not supported by mod_http2. The mpm determines how things are processed in your server. HTTP/2 has more demands in this regard and the currently selected mpm will just not do. This is an advisory warning. Your server will continue to work, but the HTTP/2 protocol will be inactive.

This is discussed here:
where the recommendation is to move to "event" instead of "prefork".

Changing apache from the default "event" to "prefork" is just part of every manual WeBWorK installation I've looked through. So I assume it is important.

I'm unsure if I should just leave it alone or try to change to "event". Does anyone understand the consequences of either?

In reply to Alex Jordan

Re: The mpm module (prefork.c) ... will just not do

by Glenn Rice -

mpm_prefork is required for modperl2.  There really is not other option.  So until we remove the dependence on modperl2 we are stuck with it.

If you disable the http2 module, that warning will go away.  It is not used by webwork2, and as long as you are using mpm_prefork, you can't use http2.

Webwork3 won't depend on modperl2, so it will be better to use mpm_event module instead with apache2.