Weblogic 在 5 分钟后重播请求
我们正在调查特定 Web 请求处理在 Weblogic 10.3 服务器上持续很长时间的问题。恰好 5 分钟后，服务器开始处理完全相同的请求，导致应用程序逻辑出现错误。这种情况甚至发生3、4次。您能帮我看看哪个服务器设置或其他可能导致此问题的原因吗？
在日志中我们可以看到这些条目：
<BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "667" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@2f35bea[
.......
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-65 "[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
}
we're investigating an issue where a specific web request processing lasts long on our Weblogic 10.3 server. Exactly after 5 minutes the server starts processing the very same request, causing an error in the application logic. This happens even 3 or 4 times. Can you help me which server setting or whatever might cause this?
In the logs we can see these entries:
<BEA-000337> <[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)' has been busy for "667" seconds working on the request "weblogic.servlet.internal.ServletRequestImpl@2f35bea[
.......
]", which is more than the configured time (StuckThreadMaxTime) of "600" seconds. Stack trace:
Thread-65 "[STUCK] ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'" <alive, in native, suspended, priority=1, DAEMON> {
}
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
解决方案：如果连接超时，客户端软件会循环重新发送请求。
The solution: the client software was resending the request in a loop if the connection timed out.