websphere，针对 Active Directory 进行身份验证时为 100%
我已经将 Websphere 6.0.29 设置为针对 Active Directory 进行身份验证，但是当我使用有效用户登录 Web 应用程序时，CPU 会达到 100% 并且无法恢复，如果我使用无效用户登录，那么我正如预期的那样得到 403。
websphere 日志中没有任何线索。
我对下一步应该做什么感到困惑。
谁能建议我接下来应该去哪里？ 或者还有其他人看到过这个问题吗？
杰夫·波特
I've got Websphere 6.0.29 setup to authenticate against Active Directory, but when I log in to my Webapp with a valid user the CPU goes to 100% and doesn't recover, if I log in with an invalid user, then I get a 403 as expected.
There is no clues in the websphere logs.
And I'm stumped as to what the next step should be.
Can anyone suggest where I should look next?
Or has anyone else seen this problem?
Jeff Porter
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
正如 Rick 建议的那样，查看线程转储以了解 CPU 处于 100% 时发生的情况。
最好查看 Must Gathers 中的相应场景。既然你提到了 AD，我假设你正在 Windows Box 上运行。
请参阅本文档并查找“手动收集数据”部分
http://www-01.ibm.com/support/docview。 wss?uid=swg21111364
这在 PMR 过程中通常是必需的，但您应该能够执行相同的操作并尝试分析捕获的数据。
如果您在分析这些数据后无法取得进展，您应该考虑开设 PMR。
如果您注意到本文档的内容，它确实需要线程转储，这可以让您深入了解 JVM 在这 100% CPU 时间内正在做什么。
华泰
曼鲁
As Rick suggested look at the thread dumps to see what is happening when the CPU is at 100%.
It is a good idea to look at Must Gathers for the corresponding scenario. Since you mentioned AD, i am assuming you are running on a Windows Box.
Refer to this document and look for the section (Collecting Data manually)
http://www-01.ibm.com/support/docview.wss?uid=swg21111364
This is typically required during a PMR process but you should be able to do the same and try and analyze the data that is captured.
If you cannot make progress after analyzing this data you should consider opening up a PMR.
if you notice the contents of this doc, it would indeed take thread dumps which would give insight to what the JVM is doing during these 100% CPU time.
HTH
Manglu
进行线程转储以查看登录线程发生了什么情况。
Take a thread dump to see what is going on with the login thread.