-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
All,
Motivated by seeing Rainer's presentation at ApacheCon 2013,
"Monitoring Apache Tomcat and the Apache Web" [1], I started looking
at mod_jk's status worker - particularly the XML output as I believe
it will be the easiest format to parse for monitoring purposes.
Each worker has a number of URL mappings, but they are not actually
nested within each worker's XML element. What I would have expected
(and, indeed, the elements are *indented* in this way):
<jk:ajp_workers
count="4"
>
<jk:ajp
name="worker01"
type="ajp13"
host="localhost"
...
/>
<jk:map
id="1"
server="www.foo.com [_default_:443]"
uri="/url-path"
...
/>
Note that the <jk:ajp> element is an unpaired tag: the <jk:map>
elements that "belong" to it are not actually nested under it. The XML
is well-formed: there is no spurious </jk:ajp> tag or anything like that.
But, it seems that there is no way to tie a <jk:map> element to its
parent <jk:ajp> element -- there are no identifiers, etc. that link
one to the other. Nor is there a parent-child relationship between them.
Is that intentional? I would think that having those <jk:map> elements
nested under the <jk:ajp> elements would be more useful.
Is anyone using the XML format of the mod_jk status worker? Has it
been frustrating to use, or is it just not that useful to inspect the
<jk:map> elements and so nobody cares?
Thanks,
- -chris
[1] http://na.apachecon.com/schedule/presentation/169/ No slides yet :(
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.17 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iEYEAREIAAYFAlEyEjMACgkQ9CaO5/Lv0PBESQCgqsrI8z9BLEQcllzD0ysn6UNa
TT8An30Y+Ko/w1jHBSpE8KimoxM7w/cY
=xLMu
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
