The jk2 connector has a status page and some experimental support for remote JMX. That means the internal components in the C code are visible in the JMX console, and you can also perform some limited control.
To experiment:
- insert in jk2.properties:
No Format |
---|
modjk.webServerPort=APACHE_PORT |
- make sure /jkstatus is enabled
The code is generic and is beeing merged with commons-modeler, which will provide typed attributes - right now everything is treated as a string, descriptions and more.
If you play with the setters - it is very important to make sure that workers2.properties is writtable by the apache user. To deal with the multi-process servers we need to save the file so all processes are synchronized. Also keep in mind that all changes made via JMX on mod_jk are persisted automatically ( unlike the changes in /admin, which need an explicit save ).