You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Frank Schullerer <sc...@googlemail.com.INVALID> on 2018/12/04 10:19:28 UTC
Using tomcat manager to deploy to several services
Hello,
I think this question is independent from the tomcat version but I tried it
with Tomcat 9.0.13 on Windows.
We have several "service" tags in our server.xml because we have several
applications
running in one tomcat with several ports and different configuration
(clientAuth etc).
I tried to use the tomcat manager to deploy to different services but it
failed. It seems that the tomcat manager can only deploy within the same
service because when I deploy the tomcat manager itself to a different
service than it works. I can deploy to that service.
Is this correct or can I configure the tomcat manager to deploy to other
services? I also tried to achive that with a configuration with
"context.xml" but failed.
Please help!
Re: Using tomcat manager to deploy to several services
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Frank,
On 12/4/18 11:55, Frank Schullerer wrote:
> After searching the web many many times and reading all this here,
> it seems that there is no real good solution for this.
What exactly is "this"? What problem are you having that needs a
solution, and what is "not good" about the solutions you've been
presented with?
- -chris
> Am Di., 4. Dez. 2018 um 17:45 Uhr schrieb Christopher Schultz <
> chris@christopherschultz.net>:
>
> Frank,
>
> On 12/4/18 06:09, Frank Schullerer wrote:
>>>> Thanks!
>>>>
>>>> Ok let me know if I can achive things in a better way. Now I
>>>> have a server.xml like this:
>>>>
>>>> <Server port="8005" shutdown="SHUTDOWN"> <Listener ...
>>>> <Service name="Catalina"> <Connector port="8080" ... <Engine
>>>> name="Catalina" defaultHost="localhost"> <Realm ..
>>>>
>>>> <Host name="localhost" appBase="webapps" ... </Engine>
>>>> </Service>
>>>>
>>>> <Service name="a"> <Connector port="11111"
>>>> clientAuth="false" keyAlias="aaaaaaaa" /> <Engine name="a" >
>>>> <Realm ... <Host name="host1" appBase="services/a" > </Host>
>>>> </Engine> </Service> <Service name="b"> <Connector
>>>> port="222222" clientAuth="true" keyAlias="bbbbbbbb" />
>>>> <Engine name="b" > <Realm ... <Host name="host2"
>>>> appBase="services/b" > </Host> </Engine> </Service> <Service
>>>> name="c"> <Connector port="333333" clientAuth="true"
>>>> keyAlias="ccccccc" /> <Engine name="c" > <Realm ... <Host
>>>> name="host3" appBase="services/c" > </Host> </Engine>
>>>> </Service>
>>>>
>>>> Please note that we need different ports and different
>>>> configurations (like clientAuth or keyAlias) for the
>>>> applications. If there is a better way and have a tomcat
>>>> manager to deploy all applications, please let me know!
>>>>
>>>> Thank you in advance!
>
> As Mark said, you will need to deploy the Tomcat manager 4 times
> for the above configuration.
>
> -chris
>
>>>> Am Di., 4. Dez. 2018 um 11:53 Uhr schrieb Mark Thomas
>>>> <ma...@apache.org>:
>>>>
>>>>> On 04/12/2018 10:19, Frank Schullerer wrote:
>>>>>> Hello,
>>>>>>
>>>>>> I think this question is independent from the tomcat
>>>>>> version but I tried
>>>>> it
>>>>>> with Tomcat 9.0.13 on Windows. We have several "service"
>>>>>> tags in our server.xml because we have several
>>>>>> applications running in one tomcat with several ports and
>>>>>> different configuration (clientAuth etc). I tried to use
>>>>>> the tomcat manager to deploy to different services but it
>>>>>> failed. It seems that the tomcat manager can only deploy
>>>>>> within the same service because when I deploy the tomcat
>>>>>> manager itself to a different service than it works. I
>>>>>> can deploy to that service.
>>>>>>
>>>>>> Is this correct or can I configure the tomcat manager to
>>>>>> deploy to other services? I also tried to achive that
>>>>>> with a configuration with "context.xml" but failed.
>>>>>>
>>>>>> Please help!
>>>>>
>>>>> TL;DR you can't deploy services that way.
>>>>>
>>>>> The Tomcat Manager application only works with the Host to
>>>>> which it has been deployed.
>>>>>
>>>>> In Tomcat: - There is exactly one Server - A Server may
>>>>> contain 0 or more Services - A Service may contain 0 or
>>>>> more Connectors and no more than one Engine - An Engine may
>>>>> contain 0 or more Hosts - A host may contain 0 or more
>>>>> Contexts (Context == web application)
>>>>>
>>>>> (I left a few things like Valves and Executors out to keep
>>>>> it simple)
>>>>>
>>>>>
>>>>> The Tomcat Host Manager application only works with the
>>>>> Engine associated with the Host to which it has been
>>>>> deployed.
>>>>>
>>>>> Mark
>>>>>
>>>>> ------------------------------------------------------------------
- ---
>>>>>
>>>>>
>
>>>>>
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>>> For additional commands, e-mail:
>>>>> users-help@tomcat.apache.org
>>>>>
>>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>>
>>
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIyBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwH8GMACgkQHPApP6U8
pFhBhg/4kb3VWlmGJ246fSuWMw4Y581heIIzsNzxPcTIppIc586mSItulaunKPEB
VkOqWVHjIotwLlh18wTufd3U4R4MyOn8OK44wAMaSjJPGKwNQgKyD2CwoQ3sdJJJ
SpYlmWOcCoqkVCQ+Di4I7Wa2KuMvp/waccMnMdJ+osJ7RJsflqeho9NkCy8489NB
C7CSHHBvQaiPn2i8iMROKG2u7piY9JqZTK87k6O+cuzZxzQ91en5OhapuCZzUzsx
Thle+aDUhWfaoeyd31UYuRZTUm3/ptFlqrd8Lpr3W2UbR4rKqfQHA7hZD2axD3Kf
qM9N6npkFG1iI+zyMygbWZ2HHIMnSbc3Ij/aU2I2b0sNiE+mZAflX0Lvhi0Ecvlw
YPh4qiKUQik7H1Web5Ruuows9DiI3oxiQhmBso/GEcbyc7vRg/KdQUwnvJ0/s5hT
6V7+5yg8NeAprg3Mf62Cjj/ehXZm9/HSM6FuwJ0YpKxg0hoDyJCYppCVxBq6FZWO
9Sk9qxHXw4vVKLVTigLT4UyJ4aIi+kgxG5nOPIsK0xsGaraPxfC4byQrWdph3zrx
P9n6wfnRdPN76r9fFFGeN/s7nEv5PaHN38P5zbErH7em+YI12hrYd966DW3MMZUT
ALRdXyn9iUf2v6yVG7SpGOFsVTpOGMoffzGgGeVmFMpAxzyAXA==
=K45B
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Using tomcat manager to deploy to several services
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 04.12.2018 17:55, Frank Schullerer wrote:
> Hello @all,
>
> After searching the web many many times and reading all this here, it seems
> that there is no real good
> solution for this. In my example server.xml are 4 services but we have 25
> and more to come. So we need maybe a
> management solution like the Tcat server or I don't know . That's a little
> frustrating because I thought it'd be easier.
>
> But many thanks for all the answers!!!
You may be interested also in this :
https://stackoverflow.com/questions/45927603/multiple-tomcat-instances-vs-multiple-tomcat-services
There were also several discussions on the same theme in the past on this same list, of
which searchable archives are available, as per :
http://tomcat.apache.org/lists.html
for example :
https://markmail.org/search/?q=multiple%20instances%20list%3Aorg.apache.tomcat.user%2F
>
>
> Am Di., 4. Dez. 2018 um 17:45 Uhr schrieb Christopher Schultz <
> chris@christopherschultz.net>:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA256
>>
>> Frank,
>>
>> On 12/4/18 06:09, Frank Schullerer wrote:
>>> Thanks!
>>>
>>> Ok let me know if I can achive things in a better way. Now I have
>>> a server.xml like this:
>>>
>>> <Server port="8005" shutdown="SHUTDOWN"> <Listener ... <Service
>>> name="Catalina"> <Connector port="8080" ... <Engine name="Catalina"
>>> defaultHost="localhost"> <Realm ..
>>>
>>> <Host name="localhost" appBase="webapps" ... </Engine> </Service>
>>>
>>> <Service name="a"> <Connector port="11111" clientAuth="false"
>>> keyAlias="aaaaaaaa" /> <Engine name="a" > <Realm ... <Host
>>> name="host1" appBase="services/a" > </Host> </Engine> </Service>
>>> <Service name="b"> <Connector port="222222" clientAuth="true"
>>> keyAlias="bbbbbbbb" /> <Engine name="b" > <Realm ... <Host
>>> name="host2" appBase="services/b" > </Host> </Engine> </Service>
>>> <Service name="c"> <Connector port="333333" clientAuth="true"
>>> keyAlias="ccccccc" /> <Engine name="c" > <Realm ... <Host
>>> name="host3" appBase="services/c" > </Host> </Engine> </Service>
>>>
>>> Please note that we need different ports and different
>>> configurations (like clientAuth or keyAlias) for the applications.
>>> If there is a better way and have a tomcat manager to deploy all
>>> applications, please let me know!
>>>
>>> Thank you in advance!
>>
>> As Mark said, you will need to deploy the Tomcat manager 4 times for
>> the above configuration.
>>
>> - -chris
>>
>>> Am Di., 4. Dez. 2018 um 11:53 Uhr schrieb Mark Thomas
>>> <ma...@apache.org>:
>>>
>>>> On 04/12/2018 10:19, Frank Schullerer wrote:
>>>>> Hello,
>>>>>
>>>>> I think this question is independent from the tomcat version
>>>>> but I tried
>>>> it
>>>>> with Tomcat 9.0.13 on Windows. We have several "service" tags
>>>>> in our server.xml because we have several applications running
>>>>> in one tomcat with several ports and different configuration
>>>>> (clientAuth etc). I tried to use the tomcat manager to deploy
>>>>> to different services but it failed. It seems that the tomcat
>>>>> manager can only deploy within the same service because when I
>>>>> deploy the tomcat manager itself to a different service than it
>>>>> works. I can deploy to that service.
>>>>>
>>>>> Is this correct or can I configure the tomcat manager to deploy
>>>>> to other services? I also tried to achive that with a
>>>>> configuration with "context.xml" but failed.
>>>>>
>>>>> Please help!
>>>>
>>>> TL;DR you can't deploy services that way.
>>>>
>>>> The Tomcat Manager application only works with the Host to which
>>>> it has been deployed.
>>>>
>>>> In Tomcat: - There is exactly one Server - A Server may contain 0
>>>> or more Services - A Service may contain 0 or more Connectors and
>>>> no more than one Engine - An Engine may contain 0 or more Hosts -
>>>> A host may contain 0 or more Contexts (Context == web
>>>> application)
>>>>
>>>> (I left a few things like Valves and Executors out to keep it
>>>> simple)
>>>>
>>>>
>>>> The Tomcat Host Manager application only works with the Engine
>>>> associated with the Host to which it has been deployed.
>>>>
>>>> Mark
>>>>
>>>> ---------------------------------------------------------------------
>>>>
>>>>
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>>>> For additional commands, e-mail: users-help@tomcat.apache.org
>>>>
>>>>
>>>
>> -----BEGIN PGP SIGNATURE-----
>> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>>
>> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwGrywACgkQHPApP6U8
>> pFjwZhAAkXowqbvU3WteyhR+Zv2UkNcYhQ5XQH9Z/0kw0GF53+We2Tb4VH6dtXMK
>> CF/JEIRRLGaRW60HO2V5vXi3dP57+eZm2gpUIH4bpNfE5w7yCl0CdbSwgSzC5+IR
>> 4++CqvGRSQO1fMzIWQG+aYopvo1UDgfBl8mL5mcBcUrzkL1jeEledWDv63kI6MFQ
>> 3FlXjl6qgF1eV9EYUw2BUtQyRlgWVLmmMu9p/7PY90WupBMzFAIWcxas3YwITGTY
>> Ul2/ClxdfQdOU179l5YRD2nB5mgZNPZ1kIL6WNy9AJtzq8fHUrdj4CfTC4uy9FqL
>> BLw66Huj0AADMJn5RBH7WyH+hyVNbf8JSGjLyF6PLYvot6ZR6iRidzftpwT42kya
>> JZgpALSRBGIKOAPbNWEPRtrgTp5TjX1cMol23v86+jv6DEzLLptv4wa8jJyLbZ4w
>> UU5NW7RQ/oJoWY3IQ1fdsYmwsqYj08JkzN9ZEEWa0DlA150dJvMxrizSY5C3QGeo
>> S7WN2mWsbvppZRVg6qAlFlOyFjmJIKWWg4YBp1OybUzgAFb1w8E/xH521T5Zz1Rj
>> uV0xit65jvYZucSUsA13q/vEGESOc5VIex/rKCaDOJhtiTHLTtGzkbA7kYgJVAJS
>> NqKpbb7Zr+K7PS4i5pjIlAZjv6oqF40M9xwbTjEi6QyLyxQiYho=
>> =LeCR
>> -----END PGP SIGNATURE-----
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Using tomcat manager to deploy to several services
Posted by Frank Schullerer <sc...@googlemail.com.INVALID>.
Hello @all,
After searching the web many many times and reading all this here, it seems
that there is no real good
solution for this. In my example server.xml are 4 services but we have 25
and more to come. So we need maybe a
management solution like the Tcat server or I don't know . That's a little
frustrating because I thought it'd be easier.
But many thanks for all the answers!!!
Am Di., 4. Dez. 2018 um 17:45 Uhr schrieb Christopher Schultz <
chris@christopherschultz.net>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Frank,
>
> On 12/4/18 06:09, Frank Schullerer wrote:
> > Thanks!
> >
> > Ok let me know if I can achive things in a better way. Now I have
> > a server.xml like this:
> >
> > <Server port="8005" shutdown="SHUTDOWN"> <Listener ... <Service
> > name="Catalina"> <Connector port="8080" ... <Engine name="Catalina"
> > defaultHost="localhost"> <Realm ..
> >
> > <Host name="localhost" appBase="webapps" ... </Engine> </Service>
> >
> > <Service name="a"> <Connector port="11111" clientAuth="false"
> > keyAlias="aaaaaaaa" /> <Engine name="a" > <Realm ... <Host
> > name="host1" appBase="services/a" > </Host> </Engine> </Service>
> > <Service name="b"> <Connector port="222222" clientAuth="true"
> > keyAlias="bbbbbbbb" /> <Engine name="b" > <Realm ... <Host
> > name="host2" appBase="services/b" > </Host> </Engine> </Service>
> > <Service name="c"> <Connector port="333333" clientAuth="true"
> > keyAlias="ccccccc" /> <Engine name="c" > <Realm ... <Host
> > name="host3" appBase="services/c" > </Host> </Engine> </Service>
> >
> > Please note that we need different ports and different
> > configurations (like clientAuth or keyAlias) for the applications.
> > If there is a better way and have a tomcat manager to deploy all
> > applications, please let me know!
> >
> > Thank you in advance!
>
> As Mark said, you will need to deploy the Tomcat manager 4 times for
> the above configuration.
>
> - -chris
>
> > Am Di., 4. Dez. 2018 um 11:53 Uhr schrieb Mark Thomas
> > <ma...@apache.org>:
> >
> >> On 04/12/2018 10:19, Frank Schullerer wrote:
> >>> Hello,
> >>>
> >>> I think this question is independent from the tomcat version
> >>> but I tried
> >> it
> >>> with Tomcat 9.0.13 on Windows. We have several "service" tags
> >>> in our server.xml because we have several applications running
> >>> in one tomcat with several ports and different configuration
> >>> (clientAuth etc). I tried to use the tomcat manager to deploy
> >>> to different services but it failed. It seems that the tomcat
> >>> manager can only deploy within the same service because when I
> >>> deploy the tomcat manager itself to a different service than it
> >>> works. I can deploy to that service.
> >>>
> >>> Is this correct or can I configure the tomcat manager to deploy
> >>> to other services? I also tried to achive that with a
> >>> configuration with "context.xml" but failed.
> >>>
> >>> Please help!
> >>
> >> TL;DR you can't deploy services that way.
> >>
> >> The Tomcat Manager application only works with the Host to which
> >> it has been deployed.
> >>
> >> In Tomcat: - There is exactly one Server - A Server may contain 0
> >> or more Services - A Service may contain 0 or more Connectors and
> >> no more than one Engine - An Engine may contain 0 or more Hosts -
> >> A host may contain 0 or more Contexts (Context == web
> >> application)
> >>
> >> (I left a few things like Valves and Executors out to keep it
> >> simple)
> >>
> >>
> >> The Tomcat Host Manager application only works with the Engine
> >> associated with the Host to which it has been deployed.
> >>
> >> Mark
> >>
> >> ---------------------------------------------------------------------
> >>
> >>
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> >> For additional commands, e-mail: users-help@tomcat.apache.org
> >>
> >>
> >
> -----BEGIN PGP SIGNATURE-----
> Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
>
> iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwGrywACgkQHPApP6U8
> pFjwZhAAkXowqbvU3WteyhR+Zv2UkNcYhQ5XQH9Z/0kw0GF53+We2Tb4VH6dtXMK
> CF/JEIRRLGaRW60HO2V5vXi3dP57+eZm2gpUIH4bpNfE5w7yCl0CdbSwgSzC5+IR
> 4++CqvGRSQO1fMzIWQG+aYopvo1UDgfBl8mL5mcBcUrzkL1jeEledWDv63kI6MFQ
> 3FlXjl6qgF1eV9EYUw2BUtQyRlgWVLmmMu9p/7PY90WupBMzFAIWcxas3YwITGTY
> Ul2/ClxdfQdOU179l5YRD2nB5mgZNPZ1kIL6WNy9AJtzq8fHUrdj4CfTC4uy9FqL
> BLw66Huj0AADMJn5RBH7WyH+hyVNbf8JSGjLyF6PLYvot6ZR6iRidzftpwT42kya
> JZgpALSRBGIKOAPbNWEPRtrgTp5TjX1cMol23v86+jv6DEzLLptv4wa8jJyLbZ4w
> UU5NW7RQ/oJoWY3IQ1fdsYmwsqYj08JkzN9ZEEWa0DlA150dJvMxrizSY5C3QGeo
> S7WN2mWsbvppZRVg6qAlFlOyFjmJIKWWg4YBp1OybUzgAFb1w8E/xH521T5Zz1Rj
> uV0xit65jvYZucSUsA13q/vEGESOc5VIex/rKCaDOJhtiTHLTtGzkbA7kYgJVAJS
> NqKpbb7Zr+K7PS4i5pjIlAZjv6oqF40M9xwbTjEi6QyLyxQiYho=
> =LeCR
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Using tomcat manager to deploy to several services
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Frank,
On 12/4/18 06:09, Frank Schullerer wrote:
> Thanks!
>
> Ok let me know if I can achive things in a better way. Now I have
> a server.xml like this:
>
> <Server port="8005" shutdown="SHUTDOWN"> <Listener ... <Service
> name="Catalina"> <Connector port="8080" ... <Engine name="Catalina"
> defaultHost="localhost"> <Realm ..
>
> <Host name="localhost" appBase="webapps" ... </Engine> </Service>
>
> <Service name="a"> <Connector port="11111" clientAuth="false"
> keyAlias="aaaaaaaa" /> <Engine name="a" > <Realm ... <Host
> name="host1" appBase="services/a" > </Host> </Engine> </Service>
> <Service name="b"> <Connector port="222222" clientAuth="true"
> keyAlias="bbbbbbbb" /> <Engine name="b" > <Realm ... <Host
> name="host2" appBase="services/b" > </Host> </Engine> </Service>
> <Service name="c"> <Connector port="333333" clientAuth="true"
> keyAlias="ccccccc" /> <Engine name="c" > <Realm ... <Host
> name="host3" appBase="services/c" > </Host> </Engine> </Service>
>
> Please note that we need different ports and different
> configurations (like clientAuth or keyAlias) for the applications.
> If there is a better way and have a tomcat manager to deploy all
> applications, please let me know!
>
> Thank you in advance!
As Mark said, you will need to deploy the Tomcat manager 4 times for
the above configuration.
- -chris
> Am Di., 4. Dez. 2018 um 11:53 Uhr schrieb Mark Thomas
> <ma...@apache.org>:
>
>> On 04/12/2018 10:19, Frank Schullerer wrote:
>>> Hello,
>>>
>>> I think this question is independent from the tomcat version
>>> but I tried
>> it
>>> with Tomcat 9.0.13 on Windows. We have several "service" tags
>>> in our server.xml because we have several applications running
>>> in one tomcat with several ports and different configuration
>>> (clientAuth etc). I tried to use the tomcat manager to deploy
>>> to different services but it failed. It seems that the tomcat
>>> manager can only deploy within the same service because when I
>>> deploy the tomcat manager itself to a different service than it
>>> works. I can deploy to that service.
>>>
>>> Is this correct or can I configure the tomcat manager to deploy
>>> to other services? I also tried to achive that with a
>>> configuration with "context.xml" but failed.
>>>
>>> Please help!
>>
>> TL;DR you can't deploy services that way.
>>
>> The Tomcat Manager application only works with the Host to which
>> it has been deployed.
>>
>> In Tomcat: - There is exactly one Server - A Server may contain 0
>> or more Services - A Service may contain 0 or more Connectors and
>> no more than one Engine - An Engine may contain 0 or more Hosts -
>> A host may contain 0 or more Contexts (Context == web
>> application)
>>
>> (I left a few things like Valves and Executors out to keep it
>> simple)
>>
>>
>> The Tomcat Host Manager application only works with the Engine
>> associated with the Host to which it has been deployed.
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>>
>>
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>>
>
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwGrywACgkQHPApP6U8
pFjwZhAAkXowqbvU3WteyhR+Zv2UkNcYhQ5XQH9Z/0kw0GF53+We2Tb4VH6dtXMK
CF/JEIRRLGaRW60HO2V5vXi3dP57+eZm2gpUIH4bpNfE5w7yCl0CdbSwgSzC5+IR
4++CqvGRSQO1fMzIWQG+aYopvo1UDgfBl8mL5mcBcUrzkL1jeEledWDv63kI6MFQ
3FlXjl6qgF1eV9EYUw2BUtQyRlgWVLmmMu9p/7PY90WupBMzFAIWcxas3YwITGTY
Ul2/ClxdfQdOU179l5YRD2nB5mgZNPZ1kIL6WNy9AJtzq8fHUrdj4CfTC4uy9FqL
BLw66Huj0AADMJn5RBH7WyH+hyVNbf8JSGjLyF6PLYvot6ZR6iRidzftpwT42kya
JZgpALSRBGIKOAPbNWEPRtrgTp5TjX1cMol23v86+jv6DEzLLptv4wa8jJyLbZ4w
UU5NW7RQ/oJoWY3IQ1fdsYmwsqYj08JkzN9ZEEWa0DlA150dJvMxrizSY5C3QGeo
S7WN2mWsbvppZRVg6qAlFlOyFjmJIKWWg4YBp1OybUzgAFb1w8E/xH521T5Zz1Rj
uV0xit65jvYZucSUsA13q/vEGESOc5VIex/rKCaDOJhtiTHLTtGzkbA7kYgJVAJS
NqKpbb7Zr+K7PS4i5pjIlAZjv6oqF40M9xwbTjEi6QyLyxQiYho=
=LeCR
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Using tomcat manager to deploy to several services
Posted by Frank Schullerer <sc...@googlemail.com.INVALID>.
Hello @all,
again thanks for all the answers.
I'm thinking if it's better to have a separate Tomcat instance for each
service. At the moment we have many services running in one Tomcat
instance. The problem with restarting the Tomcat can be imagined by
everyone: all services are stopped.
Frank
Am Mi., 5. Dez. 2018 um 11:53 Uhr schrieb Jäkel, Guido <G....@dnb.de>:
> Dear Frank,
>
> I don't agree that this is "better". It will trigger the same things in
> the backend in the end. And obviously don't need the Tomcat Connector to be
> available.
>
> This might be important in situation with some malfunctions caused by
> near-OOM or out-of-request-workers (caused by long running or blocked
> requests).
>
> In my Tomcat farm control scripts, I also never use the "shutdown port"
> mechanism to (graceful) stop the Tomcat but send a SIGTERM to the JVM.
> Again, this will do the same thing but need much less to be fuctional. And
> if a graceful shutdown will fail, one even need to SIGKILL the JVM.
>
> >-----Original Message-----
> >From: Frank Schullerer [mailto:schullerer@googlemail.com.INVALID]
> >Sent: Tuesday, December 04, 2018 4:06 PM
> >To: users@tomcat.apache.org
> >Subject: Re: Using tomcat manager to deploy to several services
> >
> >Hello,
> >
> >thanks for the answer. That is exactly the way how we do this today (all
> >via a shell script and via Jenkins). But I thought the
> >"official" way to start/stop/deploy/reload applications via e.g. "curl
> >http://localhost:8080/manager/text/reload?... " is better
> >
> >Greetings
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
Re: Using tomcat manager to deploy to several services
Posted by Mark Thomas <ma...@apache.org>.
On 05/12/2018 11:09, André Warnier (tomcat) wrote:
> On 05.12.2018 11:53, Jäkel, Guido wrote:
>> Dear Frank,
>>
>> I don't agree that this is "better". It will trigger the same things
>> in the backend in the end. And obviously don't need the Tomcat
>> Connector to be available.
>>
>> This might be important in situation with some malfunctions caused by
>> near-OOM or out-of-request-workers (caused by long running or blocked
>> requests).
>>
>> In my Tomcat farm control scripts, I also never use the "shutdown
>> port" mechanism to (graceful) stop the Tomcat but send a SIGTERM to
>> the JVM. Again, this will do the same thing
>
> (just asking)
> Does it really ?
Yes. It triggers a shutdown hook and the end result is exactly the same
as if the shutdown port was used.
> If some tomcat code is at that time processing a client
> POST request, which potentially modifies data on the server (or a
> back-end database), is ditto tomcat code "informed" of the JVM shutdown,
> and does it have time to interrupt the processing in some
> predictable/recoverable way ?
It gets a configurable time to complete before the thread is killed.
ServletContextListeners will be informed of the shutdown. How well they
are able to communicate this to currently executing app threads will
depend on the app design. Pure servlets don't have a mechanism for this.
Mark
>
> but need much less to be fuctional. And if a graceful shutdown will
> fail, one even need to SIGKILL the JVM.
>
> That's another matter I believe. If a nuclear reactor was heading for
> meltdown, one would push the red button, even if someone is just brewing
> a cup of coffee nearby.
>
>>
>>> -----Original Message-----
>>> From: Frank Schullerer [mailto:schullerer@googlemail.com.INVALID]
>>> Sent: Tuesday, December 04, 2018 4:06 PM
>>> To: users@tomcat.apache.org
>>> Subject: Re: Using tomcat manager to deploy to several services
>>>
>>> Hello,
>>>
>>> thanks for the answer. That is exactly the way how we do this today (all
>>> via a shell script and via Jenkins). But I thought the
>>> "official" way to start/stop/deploy/reload applications via e.g.
>>> "curl
>>> http://localhost:8080/manager/text/reload?... " is better
>>>
>>> Greetings
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
>> For additional commands, e-mail: users-help@tomcat.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Using tomcat manager to deploy to several services
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 05.12.2018 16:54, Christopher Schultz wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> Guido,
>
> On 12/5/18 10:46, Jäkel, Guido wrote:
>>> Does it really ? If some tomcat code is at that time processing
>>> a client POST request, which potentially modifies data on the
>>> server (or a back-end database), is ditto tomcat code "informed"
>>> of the JVM shutdown, and does it have time to interrupt the
>>> processing in some predictable/recoverable way ?
>>
>> In no other way than a Tomcat worker get informed about a Tomcat
>> shutdown if you trigger this event e.g. by the shutdown port
>> mechanism or JXM. OT a feature of Tomcat is that it will first
>> stop accepting new requests by the connectors and let the servlet
>> containers stop the applications afterwards. Therefore, a started
>> request will be finished. And after all request workers are idle,
>> the worker pool will terminate.
>>
>> If you send a signal to a process, nothing is "interrupted" but
>> just a consumer in the process get signaled - that's why it's
>> called this way. And that's the reason why a process might not stop
>> if you send a SIGTERM to it. It's just a request to please the
>> process to terminate by itself. Some signals are handled outside
>> the process, for simplification let's say by the process scheduler.
>> If one send a SIGKILL, the scheduler will "hard kill" the process
>> (and it's threads) at any point of execution path and just recover
>> the reserved resources.
>
> This is exactly correct.
>
> It's often surprising to people when they find out that a SIGTERM can
> initiate a "graceful" shutdown of a running JVM. I think most people
> thing that SIGTERM and SIGKILL are roughly the same thing.
>
> It's an instructive thought-experiment to consider that most
> *NIX-style init systems send SIGTERM signals to all process as they
> are shutting-down the operating system. This doesn't "terminate" the
> processes (as the signal name might suggest), but rather "requests
> that they self-terminate" where the process gets to decide how to shut
> itself down.
>
> It's only SIGKILL (or some of the hardware-generated signals like
> SIGBUS) that will simply end a process without any notification or
> anything else.
>
> - -chris
Yes to both, but.
I stand contradicted in my doubt that a signal to the JVM would result in a "graceful"
tomcat shutdown. But that seems to be the case.
But Mark provided the real reason why that is so : tomcat registers a "hook" in the JVM,
so that it is notified that the JVM is shutting down. And presumably, the JVM waits for
tomcat to acknowledge, before really shutting down.
From the point of view of the OS, the only "process" is the JVM. Tomcat is not actually a
process, it is just a series of Java pre-compiled instructions being run by the JVM.
It was clear to me that the JVM actually gets signalled, and that it will, as a result,
shut down (= stop running Java code, and exit) (in its own time, unless the signal is KILL).
What was not clear to me is if the JVM in turn "signals" tomcat, or just stops running
tomcat's code immediately.
Mark clarified that.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Using tomcat manager to deploy to several services
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Guido,
On 12/5/18 10:46, Jäkel, Guido wrote:
>> Does it really ? If some tomcat code is at that time processing
>> a client POST request, which potentially modifies data on the
>> server (or a back-end database), is ditto tomcat code "informed"
>> of the JVM shutdown, and does it have time to interrupt the
>> processing in some predictable/recoverable way ?
>
> In no other way than a Tomcat worker get informed about a Tomcat
> shutdown if you trigger this event e.g. by the shutdown port
> mechanism or JXM. OT a feature of Tomcat is that it will first
> stop accepting new requests by the connectors and let the servlet
> containers stop the applications afterwards. Therefore, a started
> request will be finished. And after all request workers are idle,
> the worker pool will terminate.
>
> If you send a signal to a process, nothing is "interrupted" but
> just a consumer in the process get signaled - that's why it's
> called this way. And that's the reason why a process might not stop
> if you send a SIGTERM to it. It's just a request to please the
> process to terminate by itself. Some signals are handled outside
> the process, for simplification let's say by the process scheduler.
> If one send a SIGKILL, the scheduler will "hard kill" the process
> (and it's threads) at any point of execution path and just recover
> the reserved resources.
This is exactly correct.
It's often surprising to people when they find out that a SIGTERM can
initiate a "graceful" shutdown of a running JVM. I think most people
thing that SIGTERM and SIGKILL are roughly the same thing.
It's an instructive thought-experiment to consider that most
*NIX-style init systems send SIGTERM signals to all process as they
are shutting-down the operating system. This doesn't "terminate" the
processes (as the signal name might suggest), but rather "requests
that they self-terminate" where the process gets to decide how to shut
itself down.
It's only SIGKILL (or some of the hardware-generated signals like
SIGBUS) that will simply end a process without any notification or
anything else.
- -chris
-----BEGIN PGP SIGNATURE-----
Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/
iQIzBAEBCAAdFiEEMmKgYcQvxMe7tcJcHPApP6U8pFgFAlwH9KIACgkQHPApP6U8
pFic6Q/9EYOtfxeUnkLX76joeNYShpdlWhmATzHCHeW/jalATsrtZood0xVLzJze
Aw9yvYx1mdeOeJ0UyD9puv4/cOnI9dEsKgO4FMu3TjO6S9ern3sgK8bgJlVqI1Tf
dI4STGhfRDS0L8E6a6oyWDPpCmRgtLre67KFQFd6aAczSe9YxzSlLEp+eyBv3DXa
RjC/TDDHPi+dnJJKB7geOdZgv/Apso+z1c2CpZKGvud1m93S994NY2hQxuRTEXZ5
q6TWd/XarsuvcEOoU+4Jg6WX0ccqNF3AaTz5N0uAMcI+ZKAsc+6nQH65staOYEn3
9OFmBjNTZxXAD+7iJz2u2sk6REgHyvyhueqwwLDqM+FB4e0eQgLoq6dOhR0GegUD
IHAAgJ7jcpy5wOGZPHFg6DBONg+eiWHaRIrCQZQmS8OcALK5ZsasRHnWit7HdL4k
GJcC1jnXmIiK6ukRCil/GKusYVXvkDAhKkKcJ/Mwq2RqHamM4Gi2zkwKvq8oLnj8
XvW2SStOneVyw2o7e5KxfVOGRw+hmjflKh9XhzN4cmjsFzgK1uCaEU9SidmwC27c
8nXeZVBZYdLWW7Fixcisr5WZWSxYTJYOgQAfV4w4iP+q/kJYlz9af1VOeh584Wrd
PMzldJcFQ9sYAWe5IF8g+uO9rlP31fjY806t6oovjlbq7BRSZxE=
=pzVr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Using tomcat manager to deploy to several services
Posted by Jäkel,
Guido <G....@dnb.de>.
>Does it really ? If some tomcat code is at that time processing a client POST request,
>which potentially modifies data on the server (or a back-end database), is ditto tomcat
>code "informed" of the JVM shutdown, and does it have time to interrupt the processing in
>some predictable/recoverable way ?
In no other way than a Tomcat worker get informed about a Tomcat shutdown if you trigger this event e.g. by the shutdown port mechanism or JXM. OT a feature of Tomcat is that it will first stop accepting new requests by the connectors and let the servlet containers stop the applications afterwards. Therefore, a started request will be finished. And after all request workers are idle, the worker pool will terminate.
If you send a signal to a process, nothing is "interrupted" but just a consumer in the process get signaled - that's why it's called this way. And that's the reason why a process might not stop if you send a SIGTERM to it. It's just a request to please the process to terminate by itself. Some signals are handled outside the process, for simplification let's say by the process scheduler. If one send a SIGKILL, the scheduler will "hard kill" the process (and it's threads) at any point of execution path and just recover the reserved resources.
Re: Using tomcat manager to deploy to several services
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 05.12.2018 11:53, Jäkel, Guido wrote:
> Dear Frank,
>
> I don't agree that this is "better". It will trigger the same things in the backend in the end. And obviously don't need the Tomcat Connector to be available.
>
> This might be important in situation with some malfunctions caused by near-OOM or out-of-request-workers (caused by long running or blocked requests).
>
> In my Tomcat farm control scripts, I also never use the "shutdown port" mechanism to (graceful) stop the Tomcat but send a SIGTERM to the JVM. Again, this will do the same thing
(just asking)
Does it really ? If some tomcat code is at that time processing a client POST request,
which potentially modifies data on the server (or a back-end database), is ditto tomcat
code "informed" of the JVM shutdown, and does it have time to interrupt the processing in
some predictable/recoverable way ?
but need much less to be fuctional. And if a graceful shutdown will fail, one even need
to SIGKILL the JVM.
That's another matter I believe. If a nuclear reactor was heading for meltdown, one would
push the red button, even if someone is just brewing a cup of coffee nearby.
>
>> -----Original Message-----
>> From: Frank Schullerer [mailto:schullerer@googlemail.com.INVALID]
>> Sent: Tuesday, December 04, 2018 4:06 PM
>> To: users@tomcat.apache.org
>> Subject: Re: Using tomcat manager to deploy to several services
>>
>> Hello,
>>
>> thanks for the answer. That is exactly the way how we do this today (all
>> via a shell script and via Jenkins). But I thought the
>> "official" way to start/stop/deploy/reload applications via e.g. "curl
>> http://localhost:8080/manager/text/reload?... " is better
>>
>> Greetings
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
RE: Using tomcat manager to deploy to several services
Posted by Jäkel,
Guido <G....@dnb.de>.
Dear Frank,
I don't agree that this is "better". It will trigger the same things in the backend in the end. And obviously don't need the Tomcat Connector to be available.
This might be important in situation with some malfunctions caused by near-OOM or out-of-request-workers (caused by long running or blocked requests).
In my Tomcat farm control scripts, I also never use the "shutdown port" mechanism to (graceful) stop the Tomcat but send a SIGTERM to the JVM. Again, this will do the same thing but need much less to be fuctional. And if a graceful shutdown will fail, one even need to SIGKILL the JVM.
>-----Original Message-----
>From: Frank Schullerer [mailto:schullerer@googlemail.com.INVALID]
>Sent: Tuesday, December 04, 2018 4:06 PM
>To: users@tomcat.apache.org
>Subject: Re: Using tomcat manager to deploy to several services
>
>Hello,
>
>thanks for the answer. That is exactly the way how we do this today (all
>via a shell script and via Jenkins). But I thought the
>"official" way to start/stop/deploy/reload applications via e.g. "curl
>http://localhost:8080/manager/text/reload?... " is better
>
>Greetings
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Using tomcat manager to deploy to several services
Posted by Frank Schullerer <sc...@googlemail.com.INVALID>.
Hello,
thanks for the answer. That is exactly the way how we do this today (all
via a shell script and via Jenkins). But I thought the
"official" way to start/stop/deploy/reload applications via e.g. "curl
http://localhost:8080/manager/text/reload?... " is better
Greetings
Am Di., 4. Dez. 2018 um 15:40 Uhr schrieb Jäkel, Guido <G....@dnb.de>:
> Dear Frank,
>
> I guess you have configured autodeployment of the WARs. And it seems to me
> that you want to use a tree in a filesystem to place your deployments.
> Given that, you may use an arbitrary way to place the WARs to that
> location, because it's not the Tomcat Manager application that actually
> perform the deployment.
>
> You may trigger a restart of the application container by touching the WAR
> or (in case of an expanded deployment) touching a watched file (common
> WEB-INF/web.xml) and trigger undeploy by removing (or hiding by rename the
> extention) the WAR.
>
> >If there is a better way and have a tomcat manager to deploy all
> applications, please let me know!
>
>
> with greetings
>
> Guido
>
RE: Using tomcat manager to deploy to several services
Posted by Jäkel,
Guido <G....@dnb.de>.
Dear Frank,
I guess you have configured autodeployment of the WARs. And it seems to me that you want to use a tree in a filesystem to place your deployments. Given that, you may use an arbitrary way to place the WARs to that location, because it's not the Tomcat Manager application that actually perform the deployment.
You may trigger a restart of the application container by touching the WAR or (in case of an expanded deployment) touching a watched file (common WEB-INF/web.xml) and trigger undeploy by removing (or hiding by rename the extention) the WAR.
>If there is a better way and have a tomcat manager to deploy all applications, please let me know!
with greetings
Guido
Re: Using tomcat manager to deploy to several services
Posted by Frank Schullerer <sc...@googlemail.com.INVALID>.
Thanks!
Ok let me know if I can achive things in a better way. Now I have a
server.xml like this:
<Server port="8005" shutdown="SHUTDOWN">
<Listener ...
<Service name="Catalina">
<Connector port="8080" ...
<Engine name="Catalina" defaultHost="localhost">
<Realm ..
<Host name="localhost" appBase="webapps" ...
</Engine>
</Service>
<Service name="a">
<Connector port="11111" clientAuth="false"
keyAlias="aaaaaaaa" />
<Engine name="a" >
<Realm ...
<Host name="host1" appBase="services/a" >
</Host>
</Engine>
</Service>
<Service name="b">
<Connector port="222222" clientAuth="true"
keyAlias="bbbbbbbb" />
<Engine name="b" >
<Realm ...
<Host name="host2" appBase="services/b" >
</Host>
</Engine>
</Service>
<Service name="c">
<Connector port="333333" clientAuth="true"
keyAlias="ccccccc" />
<Engine name="c" >
<Realm ...
<Host name="host3" appBase="services/c" >
</Host>
</Engine>
</Service>
Please note that we need different ports and different configurations (like
clientAuth or keyAlias) for the applications.
If there is a better way and have a tomcat manager to deploy all
applications, please let me know!
Thank you in advance!
Am Di., 4. Dez. 2018 um 11:53 Uhr schrieb Mark Thomas <ma...@apache.org>:
> On 04/12/2018 10:19, Frank Schullerer wrote:
> > Hello,
> >
> > I think this question is independent from the tomcat version but I tried
> it
> > with Tomcat 9.0.13 on Windows.
> > We have several "service" tags in our server.xml because we have several
> > applications
> > running in one tomcat with several ports and different configuration
> > (clientAuth etc).
> > I tried to use the tomcat manager to deploy to different services but it
> > failed. It seems that the tomcat manager can only deploy within the same
> > service because when I deploy the tomcat manager itself to a different
> > service than it works. I can deploy to that service.
> >
> > Is this correct or can I configure the tomcat manager to deploy to other
> > services? I also tried to achive that with a configuration with
> > "context.xml" but failed.
> >
> > Please help!
>
> TL;DR you can't deploy services that way.
>
> The Tomcat Manager application only works with the Host to which it has
> been deployed.
>
> In Tomcat:
> - There is exactly one Server
> - A Server may contain 0 or more Services
> - A Service may contain 0 or more Connectors and no more than one Engine
> - An Engine may contain 0 or more Hosts
> - A host may contain 0 or more Contexts (Context == web application)
>
> (I left a few things like Valves and Executors out to keep it simple)
>
>
> The Tomcat Host Manager application only works with the Engine
> associated with the Host to which it has been deployed.
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
> For additional commands, e-mail: users-help@tomcat.apache.org
>
>
Re: Using tomcat manager to deploy to several services
Posted by Mark Thomas <ma...@apache.org>.
On 04/12/2018 10:19, Frank Schullerer wrote:
> Hello,
>
> I think this question is independent from the tomcat version but I tried it
> with Tomcat 9.0.13 on Windows.
> We have several "service" tags in our server.xml because we have several
> applications
> running in one tomcat with several ports and different configuration
> (clientAuth etc).
> I tried to use the tomcat manager to deploy to different services but it
> failed. It seems that the tomcat manager can only deploy within the same
> service because when I deploy the tomcat manager itself to a different
> service than it works. I can deploy to that service.
>
> Is this correct or can I configure the tomcat manager to deploy to other
> services? I also tried to achive that with a configuration with
> "context.xml" but failed.
>
> Please help!
TL;DR you can't deploy services that way.
The Tomcat Manager application only works with the Host to which it has
been deployed.
In Tomcat:
- There is exactly one Server
- A Server may contain 0 or more Services
- A Service may contain 0 or more Connectors and no more than one Engine
- An Engine may contain 0 or more Hosts
- A host may contain 0 or more Contexts (Context == web application)
(I left a few things like Valves and Executors out to keep it simple)
The Tomcat Host Manager application only works with the Engine
associated with the Host to which it has been deployed.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Using tomcat manager to deploy to several services
Posted by "André Warnier (tomcat)" <aw...@ice-sa.com>.
On 04.12.2018 11:19, Frank Schullerer wrote:
> Hello,
>
> I think this question is independent from the tomcat version but I tried it
> with Tomcat 9.0.13 on Windows.
> We have several "service" tags in our server.xml because we have several
> applications
> running in one tomcat with several ports and different configuration
> (clientAuth etc).
I think that an important piece of information here, to allow someone to really recommend
something, would be to give some details as to why you are using such a configuration, for
example instead of several separate tomcat instances, or several separate VirtualHosts.
If you have different ports and/or authentication methods, does your configuration as a
single instance bring any specific benefits in your case ?
> I tried to use the tomcat manager to deploy to different services but it
> failed. It seems that the tomcat manager can only deploy within the same
> service because when I deploy the tomcat manager itself to a different
> service than it works. I can deploy to that service.
>
> Is this correct or can I configure the tomcat manager to deploy to other
> services? I also tried to achive that with a configuration with
> "context.xml" but failed.
>
> Please help!
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org