blocks|key|603408|text|如果您有定期的构建计划，那么您可以很容易地在cron中放入如下内容|type|unstyled|depth|inlineStyleRanges|entityRanges|data|603409|crontab+-e|code-block|syntax|javascript|603410|然后在凌晨1:30停止tomcat|603411|30+1+*+*+*+./path_to_tamcat/bin/catalina.sh+stop|603412|然后在2分钟后重新启动|603413|32+1+*+*+*+./path_to_tamcat/bin/catalina.sh+start|603414|诚然，这不是非常规部署的最佳选择，但您可以轻松地通过计划的重启来进行常规部署。|603415|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|V|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|W|8|@]|9|@]|A|$]]|$1|M|3|N|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

if you have regularly scheduled builds you could easily put something in the cron like this

<pre><code>crontab -e
</code></pre>

then stop tomcat at say 1:30 am

<pre><code>30 1 * * * ./path_to_tamcat/bin/catalina.sh stop
</code></pre>

then start it up again 2 mins later

<pre><code>32 1 * * * ./path_to_tamcat/bin/catalina.sh start
</code></pre>

granted this isn't the best for irregular deployment, but you could easily have regular deployment with scheduled restart.

blocks|key|3785143|text|如果您查看bin目录中的tomcat启动和关闭.bat+(或.sh)脚本，您将看到它们实际上运行了一个java进程来启动tomcat，或者在关闭的情况下，连接到tomcat关闭端口-参见conf目录中的server.xml。您可以将构建ant任务配置为以与脚本相同的方式调用tomcat+jar。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3785144|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you look at the tomcat startup and shutdown .bat (or .sh) scripts in the bin directory, you will see that they actually run a java process to start tomcat or in the case of shutting down, connects to tomcats shutdown port - see server.xml in the conf directory.
You could configure your build ant task to invoke the tomcat jars in the same way as the scripts do.

blocks|key|595410|text|tomcat是否注册为windows服务？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|595411|如果是，只需使用netstart和netstop编写一个.bat脚本，并将其作为部署过程的最后一步进行调用。|595412|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Is tomcat registered as a windows service?

If so, just write a .bat script using netstart and netstop and have the called as the last step of your deployment process.

blocks|key|4505|text|在我看来，您使用的是小Tomcat部署管理器。我基本上没有这方面的经验，只是想让你知道。也就是说，在我工作的地方，我们使用两种设置。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4506|在server.xml文件中，上下文的属性reloadable=为“true”。|4507|我们所要做的就是将WAR文件放在正确的位置，然后Tomcat将其解压并重新加载，这没有问题。|4508|现在当我查到它的时候，official+configuration+reference说：|offset|length|4509|4510|“此功能在应用程序开发期间非常有用，但它需要大量的运行时开销，不建议用于已部署的生产应用程序。”|blockquote|4511|4512|4513|就像我说的，我们从来没有遇到过问题。我们的系统处理大量的请求，我们似乎没有问题。不过，我们从未对这两种配置进行过基准测试。|4514|你可能想试一试。至少你会了解到，当你这样做的时候，它是不是很乐意重新加载东西。你也可以检查性能，看看这对你来说是不是有问题。|4515|我应该指出的是，每隔一段时间，事情就会变得不对劲，我们无论如何都必须重启Tomcat，但这种情况相对较少。|4516|如果这样做有效，您所需要做的就是让脚本将WAR复制到正确的位置并进行监视，以确保一切正常工作。在足够多的部署之后，Tomcat将耗尽permgen空间，因此您必须意识到，无论如何都可能需要手动重新启动Tomcat。|4517|其他随机猜测：|4518|4519|你是不是直接FTPing到了最后的战争地点？也许Tomcat只是试图过早地打开它？|ordered-list-item|4520|你有收到任何类型的错误消息吗？|4521|，你有没有尝试过其他版本的Tomcat+(如果有)？也许5.5没有这个问题(或者5.0，如果你使用5.5)？也许只是一个更新的点版本？？|4522|。|4523|entityMap|0|LINK|mutability|MUTABLE|url|http://tomcat.apache.org/tomcat-5.5-doc/config/context.html^0|0|0|0|B|W|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1J|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|1K|8|@]|9|@$H|1L|I|1M|1|1N]]|A|$]]|$1|J|3|-4|5|6|7|1O|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1P|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1R|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1S|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1T|8|@]|9|@]|A|$]]|$1|T|3|U|5|6|7|1U|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1V|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1W|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1X|8|@]|9|@]|A|$]]|$1|10|3|11|5|12|7|1Y|8|@]|9|@]|A|$]]|$1|13|3|14|5|12|7|1Z|8|@]|9|@]|A|$]]|$1|15|3|16|5|12|7|20|8|@]|9|@]|A|$]]|$1|17|3|18|5|6|7|21|8|@]|9|@]|A|$]]|$1|19|3|-4|5|6|7|22|8|@]|9|@]|A|$]]]|1A|$1B|$5|1C|1D|1E|A|$1F|1G]]]]

It sounds a bit to me like you are using the little Tomcat deployment manager thing. I basically have no experience with that, just so you know. That said, where I work we use two settings.

In the server.xml file, the context has the attribute reloadable="true".

All we have to do is place the WAR file in the right spot and Tomcat unpacks it and reloads it, no problem.

Now when I looked it up, the <a href="http://tomcat.apache.org/tomcat-5.5-doc/config/context.html" rel="nofollow noreferrer">official configuration reference</a> says:

<blockquote>
 "This feature is very useful during application development, but it requires significant runtime overhead and is not recommended for use on deployed production applications."
</blockquote>

Like I said, we've never had problems. Our systems process a large number of requests and we don't seem to have a problem. We've never benchmarked the two configurations against each other though.

You might want to give it a try. At least you would learn if it is happy enough to reload things when done that way. You can check the performance as well to see if it's a problem for you.

I should note that every once in a while things just don't go right and we have to restart Tomcat anyway, but that's relatively rare.

If this works, all you need to do is have a script copy the WAR in the right spot and monitor to make sure things work. After enough deploys Tomcat will run out of permgen space, so you have to be aware that you might need to restart Tomcat by hand anyway.

Other random guesses:

<ol>
<li>Are you FTPing directly into the final WAR location? Maybe Tomcat is just trying to open it too early?</li>
<li>Are you getting any kind of error message? Maybe that could help you track the problem down?</li>
<li>Have you tried other versions of Tomcat (if available to you)? Maybe 5.5 doesn't have the problem (or 5.0 if you're on 5.5)? Maybe just a newer point release?</li>
</ol>

blocks|key|603422|text|您使用的是哪个版本的tomcat？到底是什么让它看起来好像“热”部署不起作用？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|603423|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

What version of tomcat are you using?
What exactly happens to make it appear as if a "hot" deploy doesn't work?

blocks|key|2514563|text|reloadable="true“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2514564|不允许重新部署war文件(这将自动工作)，它允许监视WEB-INF/classes和WEB-INF/lib中的文件更改，这可能不是您想要的。|2514565|大多数时候，当Tomcat中war文件的重新部署冻结时，我能够将其追溯到类加载器泄漏，请参阅Classloader+leaks:+the+dreaded+"java.lang.OutOfMemoryError:+PermGen+space"+exception|offset|length|2514566|entityMap|0|LINK|mutability|MUTABLE|url|http://blogs.oracle.com/fkieviet/entry/classloader_leaks_the_dreaded_java^0|0|0|1A|2C|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@$F|S|G|T|1|U]]|A|$]]|$1|H|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

reloadable="true"

does not enable re-deployment of war-files (this will work automatically), it enables monitoring of changes of files in WEB-INF/classes and WEB-INF/lib, which is probably not what you want.

Most of the time when re-deployement of war-files in Tomcat freezes, I was able to trace it back to classloader leaks, see see <a href="http://blogs.oracle.com/fkieviet/entry/classloader_leaks_the_dreaded_java" rel="nofollow noreferrer">Classloader leaks: the dreaded "java.lang.OutOfMemoryError: PermGen space" exception</a>

blocks|key|603482|text|你没有详细说明为什么热部署“不能正常工作”，但如果它实际上是由/WEB-INF/lib中的资源被锁定引起的(这并不是一个罕见的原因；在webapp的mail.jar中经常会看到这种情况)，那么只需将Context的antiResourceLocking属性设置为true即可。下面是一个why应用程序的/META-INF/context.xml的示例：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|603483|<Context+antiResourceLocking="true">
++++
</Context>|code-block|syntax|javascript|603484|entityMap^0|V|C|22|8|2R|7|2Z|J|3N|4|47|L|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@$9|N|A|O|B|C]|$9|P|A|Q|B|C]|$9|R|A|S|B|C]|$9|T|A|U|B|C]|$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|Z|8|@]|D|@]|E|$I|J]]|$1|K|3|-4|5|6|7|10|8|@]|D|@]|E|$]]]|L|$]]

You didn't give much detail why your hot deploys "doesn't work properly", but if it's actually been caused by a resource in <code>/WEB-INF/lib</code> been locked (which is not an uncommon cause; you see this often with the <code>mail.jar</code> of the JavaMail API), then just set the <code>Context</code>'s <code>antiResourceLocking</code> attribute to <code>true</code>. Here's an example how the webapp's <code>/META-INF/context.xml</code> would look like:

<pre><code>&lt;Context antiResourceLocking="true"&gt;
 &lt;!-- Your stuff here. --&gt;
&lt;/Context&gt;
</code></pre>

blocks|key|595460|text|在启动时启动tomcat的一种方法是使用cron并使用@reboot属性运行它：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|595461|打开终端并输入：|595462|sudo+crontab+-e|code-block|syntax|javascript|595463|在文件末尾输入命令：|595464|@reboot+/`PATH_TO_WHERE_TOMCAT_INSTALLED`/bin/startup.sh|595465|保存文件并退出。|595466|上述命令将在每次计算机启动时运行一次该命令。|595467|entityMap^0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|X|8|@]|9|@]|A|$]]|$1|O|3|P|5|6|7|Y|8|@]|9|@]|A|$]]|$1|Q|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|R|$]]

One way to start the tomcat on the startup is to run it using cron using the @reboot attribute:
open up a terminal and type :
<pre><code>sudo crontab -e
</code></pre>
at the end of the file enter the command:
<pre><code>@reboot /`PATH_TO_WHERE_TOMCAT_INSTALLED`/bin/startup.sh
</code></pre>
save the file and exit.
The above command will run the command once everytime computer boots up.

Our project uses Cruise Control to both build and hot deploy a web application to a remote server (via FTP) running Tomcat in the form of a .war file. Unfortunately, "hot" deploys don't appear to work properly, causing us to reboot Tomcat in response to each deployment. We would really like to do this auto-magically, much like the build itself. Is there an easy way to do this?

Side note: both machines are running Windows (XP or server, I think).

Side note 2: Performance doesn't really matter. This is an integration box.

Is there an easy way to get Apache Tomcat to reboot automatically after a deployment?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们的项目使用Cruise Control构建web应用程序，并以.war文件的形式将其热部署到运行Tomcat的远程服务器(通过FTP)。不幸的是，“热”部署似乎不能正常工作，导致我们重新启动Tomcat以响应每个部署。我们真的想自动魔术地完成这件事，就像构建本身一样。有什么简单的方法可以做到这一点吗？附注:两台机器都运行Windows (我认为是XP或服务器)。附注2:性能并不重要。这是一个集

问有没有一种简单的方法让Apache Tomcat在部署后自动重启？
EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有一种简单的方法让Apache Tomcat在部署后自动重启？EN

回答 8

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问有没有一种简单的方法让Apache Tomcat在部署后自动重启？
EN