Reg: Context.xml

2013-10-18 Thread Anu Prab
Hi,

I am using Tomcat version 7.0.40.

Whenever there is an entry to context.xml, the context.xml reloads and
redeploys the webapps since it is configured that way and is required to be
that way. When a user hits a URL at this point, the page will be blank
since reloading is still underway. My concern is - is there a way to
determine when the reload is complete? Also, is there a way to display a
meaningful message when the user hits a page during reload?

- Anu


Re: Reg: Context.xml

2013-10-18 Thread Mark Thomas
On 18/10/2013 08:25, Anu Prab wrote:
 Hi,
 
 I am using Tomcat version 7.0.40.
 
 Whenever there is an entry to context.xml, the context.xml reloads and
 redeploys the webapps since it is configured that way and is required to be
 that way. When a user hits a URL at this point, the page will be blank
 since reloading is still underway. My concern is - is there a way to
 determine when the reload is complete? Also, is there a way to display a
 meaningful message when the user hits a page during reload?

Editing the context.xml triggers an undeploy followed by a deploy rather
than a reload. Currently, the brief period between the undeploy and the
deploy will be treated as if no web application exists.

Handling this the same way a context reload is handled (essentially
pausing the request until the redeploy is complete) might be possible
but that would require code changes. The problem is non-trivial because
of the interactions between the Mapper, the Host, the HostConfig and the
Context objects that would need to be coordinated. I suspect the
complexity would not be worth the benefit when there is a simpler
solution available.

Using parallel deployment and deploying a new version would mean the new
version is deployed without any downtime and the old version can be
removed at your leisure.

Mark


-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org



Re: Reg: Context.xml

2013-10-18 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Mark,

On 10/18/13 3:55 AM, Mark Thomas wrote:
 On 18/10/2013 08:25, Anu Prab wrote:
 Hi,
 
 I am using Tomcat version 7.0.40.
 
 Whenever there is an entry to context.xml, the context.xml
 reloads and redeploys the webapps since it is configured that way
 and is required to be that way. When a user hits a URL at this
 point, the page will be blank since reloading is still underway.
 My concern is - is there a way to determine when the reload is
 complete? Also, is there a way to display a meaningful message
 when the user hits a page during reload?
 
 Editing the context.xml triggers an undeploy followed by a deploy
 rather than a reload. Currently, the brief period between the
 undeploy and the deploy will be treated as if no web application
 exists.
 
 Handling this the same way a context reload is handled
 (essentially pausing the request until the redeploy is complete)
 might be possible but that would require code changes. The problem
 is non-trivial because of the interactions between the Mapper, the
 Host, the HostConfig and the Context objects that would need to be
 coordinated. I suspect the complexity would not be worth the
 benefit when there is a simpler solution available.
 
 Using parallel deployment and deploying a new version would mean
 the new version is deployed without any downtime and the old
 version can be removed at your leisure.

IIRC there was a bug in the past that during a *reload*, the webapp
was temporarily unavailable and the ROOT context would be used. I
modified our deployment procedure (which typically deploys a single
webapp to a single Tomcat instance) to also deploy a trivial ROOT
webapp with /* mapped to a temporarily unavailable page.

Would such a strategy cover the case above?

- -chris
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.14 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCAAGBQJSYV+7AAoJEBzwKT+lPKRYgp0P+gMkv6wE+d493vFxFamOoZFT
h/WDZqbvdr5/hA2A5JFG0ihURE0umjfdGXCJEbjZ1uFrEKWbfML4gsCT00O6kwxW
fNK9QBFL2zr1QEyfo+1p2DA/3Ebc0wGpAicpr3N478hCDZAQ6ZvaA4b2NwcKtHSG
pzwv/fzfYXycJjPxT1xM/zAMM5pCKwV6NWqGcFZYW6jRBQDQHi04M0JBcW6c/B5X
XLWBcauCw3gbNsq4/MVesSWDBtgt+lY111OlyD+qxbcPamNEZy6txewAUYrVyjxC
kboXpwvL5hoBXzJat7PBiyY1y9M2YzAGefceQUnpXiSqFWQUpPCDGzPoKEGx9MWB
WFdtn79L5gaXH7DOEHg6Z5MwSLjZUUJKYOOhybaPCuxclgfpH0VZf2ZU9hT4Cy0X
PIF/FsI7l4tJYoQWyE5z+cBeJOLgmVMnLENrBGEYcD3b3E/9YRcv/BHou82Yigbq
Blu/1NDTqGQ6+K4jADEv7OASxYBPYKTodr8mQcgFpo/2dpcRYO5lISOEzg0FznAT
2tM5VChhqigl0PhLAQ2abQG8P4w4+Er1gfBIZkWMIq7wAgRCF3d1q/PrUqM45pko
heP5Ti5sr8r/bc4lRRJKf0OB+GBPT9eWnbwD6ngMqjb6UR5P+YnTZvhiIMaRk0To
H8WgDF+au1jkdC5RcVRK
=PXe5
-END PGP SIGNATURE-

-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org