"ejb3workshop" wrote:
I was trying out some standard user transactions using EJB3 entities and persistent message queues. During my tests I encountered several application exceptions which were caused by my code, which I was able to resolved.

However since then I am getting continous stream of messages on the console.

Searching the forum revealed that I need to write a recovery module. Seeing that I was merely using EJB3 I am wondering if there is a standard recovery model.

[com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] Could not find new XAResource to use for recovering non-serializable XAResource < 131075, 30, 28, 1--3f57fdc4:68f:46f90760:8c5d6-3f57fdc4:68

I'd be happy if I could get just rid of those messages as the cause of the problem has been resolved.

I've been facing the same issues for a month or so now and I'm not really sure how/where to start on writing a recovery module.

I've followed links from other forums to the docs for JBossTS but I guess I just don't "Get it."

How do I track down what is causing these failures n the first place? How do I, really, fix them in the recovery module? Is there a good, descriptive tutorial on all this? Anyone? Bueler?

There is this document on recovery modules: https://www.redhat.com/docs/manuals/jboss/jboss-eap-4.3/doc/jbossts/TX_Core_Failure_Recovery_Guide.pdf

But no extra module should be needed. Do you have a small test case that exhibits this problem? If so, open a Jira and attach it.

> But no extra module should be needed.

Actually that depends exactly what version of the server you are running and what the transaction encompasses. JBM has its own recovery module, but it's not enabled by default. The JCA used for database connections also has one, but it's only bundled in recent versions of the EAP and even then it's not turned on by default. In short, you probably don't need to write one, but you do need to hunt down one or two existing ones and wire them up.

A quick and dirty way of getting rid of the messages is: Shutdown JBoss (4.2.3), go to the directory:

<JBoss Path>\server\<Your selected instance>\data\tx-object-store\HashedActionStore\defaultStore\Recovery\TransactionStatusManager

Delete everything

Goto

<JBoss Path>\server\<Your selected instance>\data\tx-object-store\HashedActionStore\defaultStore\Recovery\TransactionStatusManager

Delete everything.

Restart JBoss. Messages are gone.