tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Gamache <cgama...@gmail.com>
Subject Re: Help! parallel deployment problem.
Date Wed, 26 Nov 2014 04:48:04 GMT
Indeed, the affected nodes don't have the newer war at all.

If you don't mind me asking-- if not FarmWebDeployer, what scheme do you use to deploy a war
across a cluster?


> On Nov 25, 2014, at 11:11 PM, Christopher Schultz <chris@christopherschultz.net>
wrote:
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
> 
> Chris,
> 
>> On 11/24/14 10:55 PM, Chris Gamache wrote:
>> So first, I'd be glad to. Just to be clear-- I'm not in need of a
>> lecture, but will willingly take one if anyone can help me get down
>> to a solution. My first attempt at asking for some assistance was
>> met with crickets. I haven't figured out why when I post (what I
>> think are) well written, well researched and discussion-provoking
>> questions they get no traction but if I cry "the sky is falling"
>> folks are more willing to attempt to lend a hand. Here's my go at
>> attempt #3:
>> 
>> I have a tomcat cluster. It is set up with much care according to 
>> http://tomcat.apache.org/tomcat-7.0-doc/cluster-howto.html.
>> 
>> It mostly works fine. On occasion (twice a week or so) there will
>> be one or more servers which didn't get the message that a new war
>> was deployed (continuous deployment using the tomcat parallel
>> deployment scheme. e.g. theapp##007.war) and they happily continue
>> to run the old version of the war.
> 
> I presume you have checked that the "affected" nodes are running only
> the old version and not the new version simultaneously, right?
> 
>> In a farm deployment scenario, the master node will announce to the
>> cluster a new artifact is available and then the clustered tomcats
>> will retrieve and deploy the new artifact. I can't pin down the
>> problem, but let just say for argument's sake it is a true
>> link-down situation. There doesn't seem to exist a mechanism to
>> re-announce, or announce at regular intervals. This seems like a
>> real weakness in the scheme. That makes me think I'm missing 
>> something obvious. If it works like it says it should in the docs
>> I shouldn't be having this issue. Either there's something wrong
>> with my config or there's a problem with tomcat. Based on the hair
>> I have left after pulling mine out, I'm leaning toward a problem
>> with tomcat. Is anyone leveraging FarmWebDeployer and Parallel
>> Deployment in their architecture successfully? If so, DenverCoder9,
>> what did you see?!?
> 
> Sorry, we don't use the FarmWebDeployer, so I can only give you
> theoretical advice.
> 
> - -chris
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
> Comment: GPGTools - http://gpgtools.org
> 
> iQIcBAEBCAAGBQJUdVLXAAoJEBzwKT+lPKRYtA0P/2mRSjJAoDGkAGeYxJX+2kAI
> ttgljunyS4HfzEJnujaqrkr4ljF+v3Vex8gzjkPe6bM8iatJZL1xtNOun67RyWL8
> /QJuzBzhfZBw9esPyLHKvptK6VzvgvsQFWKilwflQbl34NT8avMz4mfJEJZUBmGu
> DS+Yc9kYL1UiNxOtC/QJuMASCtZQ8yq1yZvX9qTZ6mxT4DEZOXKVazmCAwp/vWED
> LuU7UJc1xujsg7b/xR3TxrXS1kv/o+LvfbIPNIbFmJDXOUq4NkfT88SBiQcU/RL5
> 82QiZ+sZSSMUUlxdBmYO17t8Y1DWS0Bs0wQ4D70EYXumoEmE81GZTUIRPiLBr7wg
> yqoopXdIXV9mfxKwdrqFrqE6yIO1uxN3QL/0E2ycdq+stR8WwuIZ1yA7t4Bl/MPJ
> uqH2Mjh8oBBX9H+X4JEduZhXPFTOYIJMIOSdE9VKxW0BVMcEmoXMKbuqb0ZwdulK
> QGA/+b5y9FGO+zne1DTC4KTDVqCrBULfhfobCO4XA1x61JXiBGNdVJZX/ifTamS0
> h7o9BusfICldbNBaJNXFDhsH7KoyPUj+hp6qVNmCSpyNFuhkwj+MJ549z4j711NN
> 26rDJySiVXTgpkSGg9m/M1HstkomLdscPKti6S9esuclK1PXod5mJJD6zH7tKcJG
> a7OOhexas0v2sN+OMcX7
> =SW8s
> -----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


Mime
View raw message