为什么 RAD 在调试模式下跳转到 Object.wait 调用?

发布于 2024-11-27 00:40:02 字数 1148 浏览 3 评论 0原文

如果我使用 Rapid Application Developer 在“调试”模式下启动 WebSphere 7 Portal 服务器,线程将被挂起,RAD 会要求我切换到调试模式。然后我可以在调试视图中看到例如以下堆栈跟踪:

Daemon Thread [wpsDefaultWorkManager.Alarm Pool : 1] (Suspended)    
    Object.wait(long, int) line: not available [native method]  
    Object.wait(long) line: 196 
    <unknown receiving type>(BoundedBuffer).waitGet_(long) line: 187    
    BoundedBuffer.take() line: 549  
    ThreadPool.getTask(boolean) line: 865   
    ThreadPool$Worker.run() line: 1557

或者这个:

Daemon Thread [WorkManager.PortalSearchIndexWorkManager : 1] (Suspended)    
    <unknown receiving type>(Object).wait(long, int) line: not available [native method]    
    <unknown receiving type>(Object).wait(long) line: 196   
    <unknown receiving type>(BoundedBuffer).waitGet_(long) line: 187    
    <unknown receiving type>(BoundedBuffer).take() line: 549    
    <unknown receiving type>(ThreadPool).getTask(boolean) line: 865 
    <unknown receiving type>(ThreadPool$Worker).run() line: 1557

然后我可以恢复执行,一切看起来都很好,但为什么 RAD 会跳转到那里,就好像我设置了断点一样?

If I start up my WebSphere 7 Portal Sever in "Debug" using the Rapid Application Developer, threads are suspended, RAD asks me to switch to debug mode. Then I can see in the debug view for example the following stack trace:

Daemon Thread [wpsDefaultWorkManager.Alarm Pool : 1] (Suspended)    
    Object.wait(long, int) line: not available [native method]  
    Object.wait(long) line: 196 
    <unknown receiving type>(BoundedBuffer).waitGet_(long) line: 187    
    BoundedBuffer.take() line: 549  
    ThreadPool.getTask(boolean) line: 865   
    ThreadPool$Worker.run() line: 1557

Or this one:

Daemon Thread [WorkManager.PortalSearchIndexWorkManager : 1] (Suspended)    
    <unknown receiving type>(Object).wait(long, int) line: not available [native method]    
    <unknown receiving type>(Object).wait(long) line: 196   
    <unknown receiving type>(BoundedBuffer).waitGet_(long) line: 187    
    <unknown receiving type>(BoundedBuffer).take() line: 549    
    <unknown receiving type>(ThreadPool).getTask(boolean) line: 865 
    <unknown receiving type>(ThreadPool$Worker).run() line: 1557

I can then just resume execution and everything seems fine, but why does RAD jump in there as if I had set a breakpoint?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

jJeQQOZ5 2024-12-04 00:40:02

希望您的代码中没有断点,或者在发生异常时您给出的断点。如果情况并非如此。

试试这个
可能是因为存在未捕获的异常,并且您可能已启用 RAD 选项以在异常时挂起。

在RAD
转到Windows>首选项>Java>调试,取消选中“在未捕获的异常上暂停执行”选项,

然后尝试启动服务器。

Hope there are no breakpoints from your code or breakpoints that you gave when some exception happens.If that is not the case.

Try this
Might be because there is an uncaught exception and you might have enabled the RAD option to suspend on exception.

In RAD
Go to Windows>Preference>Java>Debug ,uncheck the option "Suspend execution on uncaught exceptions"

Try starting the server after that .

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文