websphere 服务器停止导致正在进行的 ejb 事务回滚
当 Websphere 服务器实例从管理控制台停止时，我观察到如下错误
Caused by: javax.ejb.TransactionRolledbackLocalException: ;嵌套异常 是：javax.transaction.TransactionRolledbackException：事务因超时而结束 在 com.ibm.ws.Transaction.JTA.TranManagerImpl.completeTxTimeout（TranManagerImpl.java:576） at com.ibm.ws.Transaction.JTA.TranManagerSet.completeTxTimeout(TranManagerSet.java:625)
这些是服务器停止期间的正在进行的 txns。 增加“应用程序服务器->服务器->事务服务”的超时似乎没有帮助。
这与服务器静默超时有关吗？如果是的话有没有办法配置这些。
此外，当我从管理控制台“终止”服务器时，不会观察到回滚，只有当我“停止”服务器时才会观察到回滚。
任何调试这个问题的想法都会很棒。
I observe errors as below when Websphere server instance is stopped from admin console
Caused by: javax.ejb.TransactionRolledbackLocalException: ; nested exception
is: javax.transaction.TransactionRolledbackException: Transaction is ended due to timeout
at com.ibm.ws.Transaction.JTA.TranManagerImpl.completeTxTimeout(TranManagerImpl.java:576)
at com.ibm.ws.Transaction.JTA.TranManagerSet.completeTxTimeout(TranManagerSet.java:625)
These are inflight txns during server stop.
Increasing the timeouts from "Application servers->server->Transaction Service" does not seem to help.
Is this to do with the server quiesce timeouts? if yes is there a way to configure those.
Also the rollbacks are not observed when I "terminate" the server from the Admin Console, only observed when I "stop" the server.
Any ideas to debug this issue would be great.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
您想要的可能是 事务高可用性部署。描述方法是唯一可用于完成这些事务而不会出现实际错误的产品功能。
您会遇到的情况是，WebSphere 应用程序服务器给每个容器一些时间来关闭。关闭超时后将强制使用。交易被回滚。那么，您还可以更改 启发式策略例如 COMMIT。这取决于事务中的所有内容都丢失还是仅事务的其余部分丢失对您的应用程序是否更好。
What you want is probably Deployment for transactional high availability. The describe method is the only product feature that is available for finishing those transactions without getting actual errors.
What happens for you is that the WebSphere Application server gives each container some time to shut down. After the shutdown timeouts it will use force. The transactions get rolled back. Well, you could also change the heurestic policy to for instance COMMIT. That depends on whether it is better for your application that everything in the transaction gets lost or whether only the rest of the transaction gets lost.