是什么原因导致Arjuna 1603(找不到新的XAResource用于恢复不可序列化的XAResource) [英] What causes Arjuna 1603 (Could not find new XAResource to use for recovering non-serializable XAResource)

问题描述

我没有Arjuna的经验，但是我的日志文件充满了:

I have no experience with Arjuna, but my log file gets filled with:

2011-06-27 09:25:18,021 WARN  [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA-16037 Could not find new XAResource to use for recovering non-serializable XAResource  formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff0a2012b7:126a:4e006635:2ba0, node_name=1, branch_uid=0:ffff0a2012b7:126a:4e006635:2ba1, eis_name=unknown eis name

2011-06-27 09:25:18,021 WARN  [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA-16038 No XAResource to recover < formatId=131076, gtrid_length=29, bqual_length=28, tx_uid=0:ffff0a2012b7:126a:4e006635:2ba0, node_name=1, branch_uid=0:ffff0a2012b7:126a:4e006635:2ba1, eis_name=unknown eis name >

这两个消息总是在一起，并且会定期写入.这些消息的数量随着JBoss服务器实例的正常运行时间而增加.由于我的应用程序(它是一个MDB，它消耗来自远程ActiveMQ的消息)存在一些问题，而这是我收到的唯一日志消息，因此我真的很想知道原因.

Those two messages always come together, and they are written periodically. The count of these messages increases with the uptime of the JBoss server instance. Since my application (it's an MDB consuming messages from a remote ActiveMQ) has some issues and these are the only log messages I get, I really want to know the reason for it.

推荐答案

要摆脱错误，请停止jboss实例并删除文件夹$JBOSS/standalone/data/tx-object-store

To get rid of the error, stop the jboss instance and remove the folder $JBOSS/standalone/data/tx-object-store

这篇关于是什么原因导致Arjuna 1603(找不到新的XAResource用于恢复不可序列化的XAResource)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！