Databases Reference
In-Depth Information
Sounds complex, right? But actually, the configuration change is extremely simple. In the
opmn.xml
file you will see a section similar to this:
<ias-component id="HTTP Server">
<process-type id="HTTP Server" module-id="OHS2">
<module-data>
<category id="start-parameters">
<data id="start-mode" value="ssl-enabled"/>
</category>
</module-data>
<process-set id="HTTP Server" numprocs="1"/>
</process-type>
</ias-component>
It is quite a simple change and involves adding an extra line, so the section becomes
<ias-component id="HTTP Server">
<process-type id="HTTP Server" module-id="OHS2">
<module-data>
<category id="start-parameters">
<data id="start-mode" value="ssl-enabled"/>
<data id="mpm" value="worker"/>
</category>
</module-data>
<process-set id="HTTP Server" numprocs="1"/>
</process-type>
</ias-component>
Notice the addition of the setting of the
mpm
parameter to a value of
worker
. So what does that do?
Well, let's take a look at how it worked before we made that change. If we examine the running Apache
processes
[ohs@db1 conf]$ ps -u ohs | grep httpd
18296 ? 00:00:00 httpd
18302 ? 00:00:00 httpd
18304 ? 00:00:00 httpd
18306 ? 00:00:00 httpd
18309 ? 00:00:00 httpd
18314 ? 00:00:00 httpd
18317 ? 00:00:00 httpd
18326 ? 00:00:00 httpd
18329 ? 00:00:00 httpd
18330 ? 00:00:00 httpd
notice how many different httpd processes there are. Now let's look at the database sessions attributed
to that Unix user:
SQL> select count(*) from v$session where osuser = 'ohs';
