All,
When looking at the JMX tree for my "server info filter" referenced in
another thread, I was wondering what would happen if I added a second
<Engine> to my configuration. After re-reading the configuration guide
and seeing that *exactly one* <Engine> can be within a <Service>,
modified by configuration to essentially just add this to the end of my
conf/server.xml file:
<Service name="Catalina2">
<Engine name="otherEngine" jvmRoute="foo"
defaultHost="foo.example.com">
<Host name="foo.example.com" appBase="/tmp/not-there"
unpackWARs="false" autoDeploy="false">
</Host>
</Engine>
</Service>
When I start the server, I see that I have the usual /Catalina tree (for
the stock/default Service) and inside that I have "Engine" which
contains the information about the engine itself.
I would have expected to have another top-level item named /Catalina2
also containing an Engine with the information about /that/ one.
Instead, I have a top-level item named "otherEngine" which contains a
subset of the "Catalina" items (probably because I haven't defined any
Datasource, Connection, etc.) and its own "Engine" child item.
So maybe the only thing that's unexpected is that the second <Service>
has somehow inherited the "name" attribute from the <Engine>.
I haven't traced through the code or anything yet. I was wondering if
this rang a bell with anyone.
I'm running Tomcat 8.5.72 on Java 8.
-chris
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
