Doesn't anyone have any idea?
Didn't I provide enough information? Is the problem too hard to help out with?
It would really help to get some thoughts on disabling the XA recovery. Whether
this is a problem, and whether we're doing it in the right way?
See my last post.
On 16/12/2019, 16:00, "Robbert de Vries" <robbert.devr...@triodos.com.INVALID>
wrote:
Also, I discovered this warning in the startup of JBoss.
15:47:36,686 WARN [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC
service thread 1-7) IJ020016: Missing <recovery> element. XA recovery disabled
for: java:/activemq/ConnectionFactory
I even get that when I explicitly add <recovery no-recovery="true"/> to the
connection-definition.
So I guess XA recovery is disabled anyway, for this connection factory...
Is it save to just disable periodic recovery in this setup? Like so
-DRecoveryEnvironmentBean.periodicRecoveryPeriod=0
-DRecoveryEnvironmentBean.recoveryBackoffPeriod=0
We don't want tx management between datasource and jms messages anyway. Any
millisecond in the app will count, and XA takes performance penalty.
