You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Chris Gamache <cg...@gmail.com> on 2014/11/25 00:48:59 UTC
Help! parallel deployment problem.
Tomcat 7 ... Working with parallel deployment, tomcat servers in my farm
are getting out-of-sync, not getting new versions of war files deployed to
the main tomcat. What could be going wrong and how can I fix it?
Pleez Help!
Re: Help! parallel deployment problem.
Posted by Mark Thomas <ma...@apache.org>.
On 25/11/2014 03:55, 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.
Your first question was very specific:
<quote>
My question is directed to other tomcat admins out there who are
handling this scenario gracefully. What are you doing to handle this
problem?
</quote>
I'd take the lack of response as meaning no other admins are handling
this scenario gracefully. That doesn't surprise me the feature isn't
that widely used.
> 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
It got no traction as you asked a specific question that I suspect
no-one had an answer to.
> but if I
> cry "the sky is falling" folks are more willing to attempt to lend a hand.
Because you are asking much broader, less specific question.
You have gone from "How are other folks handling this?" to "Is this the
expected behaviour? Is there a bug here?". Those are very different
questions.
> 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.
>
> 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.
You could always check the source code to be sure. From memory, it
should be fairly obvious from the message types whether or not such a
feature exists.
> This seems like a real weakness in the scheme.
Agreed.
> That makes me think I'm missing something obvious.
Probably not.
> If it works like it says it should in the docs I
> shouldn't be having this issue.
The docs don't appear to cover this scenario.
> 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?!?
I know the parallel deployment works with the FarmWarDeployer since I
tested that when I wrote the parallel deployment implementation. I
didn't test behaviour with failed nodes.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Help! parallel deployment problem.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Chris,
On 11/25/14 11:48 PM, Chris Gamache wrote:
> 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?
We have a small cluster with slightly different configuration on each
one (IP addresses, etc.) so we use ant to build the artifact on each
server at deployment time. That is, there is no cluster-wide
auto-deployment of any kind going on over here.
- -chris
>> On Nov 25, 2014, at 11:11 PM, Christopher Schultz
>> <ch...@christopherschultz.net> wrote:
>>
> 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
>>
>> ---------------------------------------------------------------------
>>
>>
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-----
Version: GnuPG v1
Comment: GPGTools - http://gpgtools.org
iQIcBAEBCAAGBQJUdfzUAAoJEBzwKT+lPKRYb4IP+gJ31QuRNX1nmmyWvAY7IMso
az1ZF8V3i4BYPHFB4pc+QN2D2aW8OQes5aLReHYtk4jrCdiWtFsKCYejjgYDrZkl
sqEIXAiFgJNO5pcVPsND0TTzpSTy0NlGrLn2PT39cBZZJDtWaJp/pXaYXJY63SSy
j94ZOFfuw2Zz2yW4ibZlXPoCq82hmk9xD1Sa44PTQmVBuEzvBYXk9SyP3vFhteAz
SQqFz6wjX2VjpuJ0eGnAjr60ffyb2Ea5gGST4k0lDN4BUOm/QaBstMQ8s1C+jK5F
REldc6sVCvxZg3vudtMUmYris1madRkJimwZvPBFQU0wxuSGxMwXLjsfA3ncrPiG
bUYVtatRlEhBgFPfqqKUMioeLLClc+Qu+n3DsB5qsX41WROj8Tu8apWHR8sNgW0B
N4YFgeRkf7zJnRqtXKBAKZNJY83tiIsQ/Vzm4KGRTezPqSTjE8vNfu0r17JUboRj
Hovrma+371Nvc7DpqfPR28mlvTNn7OfnrbjUuWO8cFpLXFLgTDbVPb4PFVSYfRlU
aghB4Xa8eo2GV5vAQ7jXxCpFwDWYZFBuIC/MYi8xVG7lPZALN0pnYAH3JgBKH9aj
YvNPdIVWESsjp+xdmH/hvUFj17hdBtJgFd/b5hsfcjbD/Xf9HOqaq0mwJMCWW2va
LV4sQZsVwr+v/52PQTpY
=Psx8
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Help! parallel deployment problem.
Posted by Chris Gamache <cg...@gmail.com>.
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 <ch...@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
Re: Help! parallel deployment problem.
Posted by Christopher Schultz <ch...@christopherschultz.net>.
-----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
Re: Help! parallel deployment problem.
Posted by Mark Eggers <it...@yahoo.com.INVALID>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris G,
On 11/24/2014 7: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.
>
> 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?!?
>
> TIA
>
> P.S. the sky is falling :)
>
>
>
> On Mon, Nov 24, 2014 at 7:36 PM, Leo Donahue <do...@gmail.com>
> wrote:
>
>> On Mon, Nov 24, 2014 at 5:48 PM, Chris Gamache
>> <cg...@gmail.com> wrote:
>>
>>> Tomcat 7 ... Working with parallel deployment, tomcat servers
>>> in my farm are getting out-of-sync, not getting new versions of
>>> war files deployed
>> to
>>> the main tomcat. What could be going wrong and how can I fix
>>> it?
>>>
>>> Pleez Help!
>>>
>> Before anyone lectures you on your type of question and lack of
>> specifics, re-submit a better question to get a better response.
>>
>
As Leo has pointed out, we do need a bit more information in order to
hazard a guess (or ask more questions).
Let's start with the basics.
1. Which version of Tomcat 7?
2. What operating system?
3. If the OS is Linux, did you install Tomcat from the distro or
tomcat.apache.org?
4. What JVM are you using (specific version and bits)?
Now for your infrastructure:
1. How are the clustered machines connected (network, multicast, etc.)?
Now for your Tomcat configuration:
1. Where is your watchDir set?
I have found that setting watchDir = deployDir to not be a good thing.
It's been a while since I've run a cluster, but my archived
configuration has them separate.
2. What is your processDeployFrequency?
Lower is better, at the cost of some performance. I had mine set at 4.
The default is 2.
When the error happens (ie., no updates to slave nodes):
1. What were the events leading up to the failure (errored slave gets
removed and re-added to the cluster, perhaps)?
2. Can you increase the logging level to determine what may be going on?
See some of my posts in this mailing list concerning cluster logging
on how to do this.
Finally, post (in-line) your cluster configuration (both your deployer
and your slave).
That's a start. I'm sure we'll have more questions.
However, without some information I'm afraid we'll have to fall back
to Pid's crystal ball. Sometimes it's spot on, and other times it
leads to a rather interesting goose chase.
As an aside - while I've run clustering and farm deployment with
Tomcat 7, I've not tried it in combination with parallel deployment.
As another aside - I don't know how the farm deployer recovers from a
failure mode (Tomcat absent from the cluster at time of deployment). I
should look at the code (or you can).
. . . just my two cents.
/mde/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBAgAGBQJUdAajAAoJEEFGbsYNeTwt++kIAIhH90vPnNamWKEuqxujpiGI
oQ+GFkTOlNLWUiAFzipODgyoYDfnksIm/U7KPekIIEFe+lD7eyyDrHcD0J+qHJGJ
byhhsPvjwomtKMmSVQMun5F2adk/Q5bKvwMeKOekTO+qPHlYo7A0yPgoL00yMLwG
mfE/Vpzwer+uFQ1TfseVoBoct8NQ3ewv4a45v1lPYgQgtffR/WUwYuDNrBOgpkho
byOs2qCnz4KBJ7LGxyEcd+Ekraq7VXpK+8NXVNTOUIU0Iw6sGfq1xcJNmDN15NDc
aXZiwkzT/cN1UqmrNrcariCNR4Qb8AWvzZf8zmIt/4j4CCIWnK0Kmnf0Y3ZDgks=
=817Y
-----END PGP SIGNATURE-----
---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
Re: Help! parallel deployment problem.
Posted by Chris Gamache <cg...@gmail.com>.
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.
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?!?
TIA
P.S. the sky is falling :)
On Mon, Nov 24, 2014 at 7:36 PM, Leo Donahue <do...@gmail.com> wrote:
> On Mon, Nov 24, 2014 at 5:48 PM, Chris Gamache <cg...@gmail.com> wrote:
>
> > Tomcat 7 ... Working with parallel deployment, tomcat servers in my farm
> > are getting out-of-sync, not getting new versions of war files deployed
> to
> > the main tomcat. What could be going wrong and how can I fix it?
> >
> > Pleez Help!
> >
> Before anyone lectures you on your type of question and lack of specifics,
> re-submit a better question to get a better response.
>
Re: Help! parallel deployment problem.
Posted by Leo Donahue <do...@gmail.com>.
On Mon, Nov 24, 2014 at 5:48 PM, Chris Gamache <cg...@gmail.com> wrote:
> Tomcat 7 ... Working with parallel deployment, tomcat servers in my farm
> are getting out-of-sync, not getting new versions of war files deployed to
> the main tomcat. What could be going wrong and how can I fix it?
>
> Pleez Help!
>
Before anyone lectures you on your type of question and lack of specifics,
re-submit a better question to get a better response.