RAD中的Websphere在启动时挂起 [英] Websphere in RAD hangs on startup

问题描述

我们在带有Websphere 7的RAD 7中遇到了这个问题，这是一个不一致的麻烦，但我们正在转向使用Websphere 8.5.5的RAD 9，这是一个更加一致的问题。

We've had this problem in RAD 7 with Websphere 7, and it's been an inconsistent nuisance, but we are moving to RAD 9 with Websphere 8.5.5 and it is a MUCH more consistent problem.

当启动应用程序服务器时，它声称已完成启动，但服务器选项卡中的状态未完成，并且RAD似乎几乎失去与服务器的对话。最终它报告服务器无法在300秒内启动，并尝试停止它，但是，在失去通信后，它实际上并没有停止。

What happens is that when starting the application server, it claims to finish starting, but the status from the servers tab doesn't finish, and RAD seems to almost lose conversation with the server. Eventually it reports that the server failed to start within 300 seconds, and tries to stop it, but, having lost communication, it doesn't actually stop.

如果你看起来事实上，在任务管理器中，服务器确实已启动并正在运行。浏览器与webapps对话（假设它们是在之前的会话中发布的）。如果你重新启动RAD，RAD会收到与服务器的通信，一切运行正常。但是你必须重新开始才能到达那里。

If you look at Task Manager, in fact, the server did start and is running. The browser talks to the webapps (assuming they were published in a prior session). If you restart RAD, RAD picks up the communication to the server and everything runs fine. But you had to restart to get there.

在RAD 7下，这种情况间歇性地发生。现在我们正在使用RAD 9进行测试，它每次都会发生。这是什么修复/解决方法？

Under RAD 7, this happened intermittently. Now that we're testing with RAD 9, it happens EVERY time. What's the fix/workaround for this?

推荐答案

您可以增加服务器启动时间限制：双击服务器（在Servers选项卡中） ，展开超时并将启动超时从默认值增加300秒。

You can increase server startup time limits: double click on server (in Servers tab), expand "Timeouts" and increase start timeout from default 300 seconds.

这篇关于RAD中的Websphere在启动时挂起的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！