了解 Websphere 内部结构
我很不幸必须帮助解决在 Websphere 6.0.2 上运行的古老应用程序中的一些性能问题。它在使用 IBM JDK 1.4.2 的 SLES9 上运行。该应用程序没有任何一个部分可以被认为表现良好，但这不是我的问题的目的。
我的问题是，是否有任何好的链接可以解释 WAS 的一些内部结构，例如，NotificationServiceDispatcher 线程是做什么的？它与 LocalNotificationServiceDispatcher 有何关系？它到底发送了什么通知？ WAS 如何管理 WebContainer 线程（它们在什么情况下死亡？什么消耗了它们？）？
由此不可避免地会产生更多的问题，所以我真的在寻找讨论上述问题的链接，而不是具体的答案。我浏览过 IBM 网站，但我发现它与 Oracle 竞争“无用的搜索，无法导航”。
I have the misfortune of having to help troubleshoot some performance issues in an ancient application running on Websphere 6.0.2. It runs on an SLES9 using the IBM JDK 1.4.2. There is not a single part of this application that could be considered well behaved however that's not what my Q is about.
My Q is whether there are any good links that explain what some of the WAS internals are, for instance what does the NotificationServiceDispatcher thread do? How does it relate to LocalNotificationServiceDispatcher? What notifications is it dispatching anyway? How does WAS manage WebContainer threads (in what circumstances do they die? what consumes them?)?
There are inevitably lots more Qs that could result from this so I was really looking for links that discuss the above rather than specific answers. I have looked on the IBM site but I find it competes with oracle for "useless search, impossible to navigate".
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
IBM 的红皮书通常都不错。这是 WAS 6 的一个。我不知道它是否回答了您的具体问题，但听起来比您现在得到的更多。祝你好运。
IBM's redbooks are usually decent. Here's the one for WAS 6. I don't know if it answers your specific questions or not, but it sounds like its more than you've got now. Good luck.
我知道您没有要求具体答案，但万一有人发现这个问题并正在寻找具体答案...
NotificationServiceDispatcher 线程池用于向进程外 JMX 侦听器发送通知，LocalNotificationServiceDispatcher 也做同样的事情用于进程内 JMX 侦听器。
WebContainer 线程使用ThreadPool 进行管理。 线程池设置 信息中心主题提供了一些用于管理线程的设置的简要介绍。总之，当池中的线程数量超过最小数量并且线程在指定的时间间隔内没有完成任何工作时，线程就会死亡。
I know you didn't ask for specific answers, but in case someone finds this question and is looking for specific answers...
The NotificationServiceDispatcher thread pool is used for sending notifications to out-of-process JMX listeners, and the LocalNotificationServiceDispatcher does likewise for in-process JMX listeners.
WebContainer threads are managed using a ThreadPool. The Thread pool settings InfoCenter topic provides a brief introduction to some of the settings used to manage the threads. In summary, threads will die when the pool has more than the minimum number and the thread has not done any work for a specified interval.