Thanks. That worked
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=4232509#4232509
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=4232509
___
jboss-user mailing list
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
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
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.
View the original
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?
No, not yet
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4157727#4157727
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4157727
___
jboss-user mailing list
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
