-
1. XARecovery errors in JBoss 5.1.0GA
mmusgrov May 13, 2011 9:54 AM (in response to sergiu_pienar)The user still needs to configure recovery. We were hoping to have dynamic registration of recovery modules in EAP5 which would have addressed your issue but we require support from the JCA project.
It will be there for EAP6.
-
2. XARecovery errors in JBoss 5.1.0GA
sergiu_pienar May 13, 2011 11:12 AM (in response to mmusgrov)Hi Michael,
Thank you for the quick reply.The question still remains though ... are the settings described in John's post on the blog still correct?(i.e. do they still apply to JBoss 5.1.0 GA).
If so I must be doing something wrong as I have followed all those steps and I still do get XARecovery Errors.
On a second note, I noticed that deleting the tx-object folder in hornetq does remove the XA Errors. Do you think that by removing that folder the integrity of the server is put in question ?
Thx,
Sergiu.
-
3. XARecovery errors in JBoss 5.1.0GA
mmusgrov May 13, 2011 12:18 PM (in response to sergiu_pienar)Thank you for the quick reply.The question still remains though ... are the settings described in John's post on the blog still correct?(i.e. do they still apply to JBoss 5.1.0 GA).
I am not familiar with the blog you quote. The best source of information is the product documentation http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/index.html - in particular the Transactions Administrators Guide
On a second note, I noticed that deleting the tx-object folder in hornetq does remove the XA Errors. Do you think that by removing that folder the integrity of the server is put in question ?
Yes. That is where we put the transaction logs. Removing the log entry means the transaction manager will have no knowledge of the transaction (and therefore will not be able to recover it), hence you no longer get the warnings.
-
4. XARecovery errors in JBoss 5.1.0GA
jhalliday May 15, 2011 9:06 PM (in response to sergiu_pienar)Recovery config for xa-datasource instances in -ds.xml files is automatic in the current platform release. You still need manual config for other cases, including messaging/hornetq.