[ https://issues.redhat.com/browse/WFLY-14284?page=com.atlassian.jira.plugi... ] Adriano Teixeira de Souza commented on WFLY-14284: -------------------------------------------------- [~ochaloup] I did this change and tested de start/stop operations on Wildfly 18.0.1 and 20.0.1 {code:java} cat > ${JBOSS_HOME}/domain/configuration/wildfly-config.xml <<EOF <?xml version="1.0" encoding="UTF-8"?> <configuration> <authentication-client xmlns="urn:elytron:1.0"> <authentication-rules> <rule use-configuration="jta"> <match-abstract-type name="jta" authority="jboss" /> </rule> </authentication-rules> <authentication-configurations> <configuration name="jta"> <sasl-mechanism-selector selector="DIGEST-MD5" /> <providers> <use-service-loader /> </providers> <set-user-name name="ejbserver" /> <credentials> <clear-password password="ejb" /> </credentials> <set-mechanism-realm name="ApplicationRealm" /> </configuration> </authentication-configurations> </authentication-client> </configuration> EOF {code} {code:java} SECURITY_OPTIONS="-Dwildfly.config.url=$JBOSS_HOME/domain/configuration/wildfly-config.xml" {code}   {code:java} # Change remote outbout protocol /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-workflow-connection:write-attribute(name=protocol,value=remote+http) /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-emissor-email-connection:write-attribute(name=protocol,value=remote+http) /profile=$PROFILE_NAME/subsystem=remoting/remote-outbound-connection=remote-erp-connection:write-attribute(name=protocol,value=remote+http) {code}   {code:java} # Set tx node id as unique /host=$HOSTNAME/server-config=$SERVER_NAME/system-property=jboss.tx.node.id:add(value=$SERVER_NAME,boot-time=true) {code} And after stop and start de Wildfly instance I got this log after start and the server didn't stop again. {code:java} 07:01,462 WARN [com.arjuna.ats.jta] (Periodic Recovery) ARJUNA016027: Local XARecoveryModule.xaRecovery got XA exception ARJUNA016099: Unknown error code:0: javax.transaction.xa.XAException: WFHTTP000008: Authentication failed at org.wildfly.http-client.transaction@1.0.21.Final//org.wildfly.httpclient.transaction.HttpRemoteTransactionPeer.recover(HttpRemoteTransactionPeer.java:107) at org.wildfly.transaction.client@1.1.11.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:213) at org.wildfly.transaction.client@1.1.11.Final//org.wildfly.transaction.client.SubordinateXAResource.recover(SubordinateXAResource.java:209) at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.xaRecoveryFirstPass(XARecoveryModule.java:659) at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:240) at org.jboss.jts//com.arjuna.ats.internal.jta.recovery.arjunacore.XARecoveryModule.periodicWorkFirstPass(XARecoveryModule.java:182) at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.doWorkInternal(PeriodicRecovery.java:770) at org.jboss.jts//com.arjuna.ats.internal.arjuna.recovery.PeriodicRecovery.run(PeriodicRecovery.java:382) Caused by: java.lang.SecurityException: WFHTTP000008: Authentication failed at org.wildfly.http-client.common@1.0.21.Final//org.wildfly.httpclient.common.HttpTargetContext$1$1.lambda$null$0(HttpTargetContext.java:198) at org.wildfly.http-client.common@1.0.21.Final//org.wildfly.httpclient.common.HttpConnectionPool.runPending(HttpConnectionPool.java:134) at org.wildfly.http-client.common@1.0.21.Final//org.wildfly.httpclient.common.HttpConnectionPool.getConnection(HttpConnectionPool.java:83) at org.wildfly.http-client.common@1.0.21.Final//org.wildfly.httpclient.common.HttpTargetContext$1$1.lambda$null$1(HttpTargetContext.java:193) at org.jboss.xnio@3.8.1.Final//org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92) at org.jboss.xnio@3.8.1.Final//org.xnio.ChannelListeners$DrainListener.handleEvent(ChannelListeners.java:1145) at org.jboss.xnio@3.8.1.Final//org.xnio.ChannelListeners$DrainListener.handleEvent(ChannelListeners.java:1125) at org.wildfly.http-client.common@1.0.21.Final//org.wildfly.httpclient.common.HttpTargetContext$1$1.lambda$completed$4(HttpTargetContext.java:203) at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1348) at java.base/java.lang.Thread.run(Thread.java:834) {code}   The server just works fine after delete data and temp folders {code:java} sudo rm -rf /app/wildfly/domain/data/servers/{server-name} sudo rm -rf /app/wildfly/domain/tmp/servers/{server-name} {code} it looks like there's something broken on persisted transaction data. I don't know what could be the consequences of doing this on production enviroments after undeployment or stop operations.   -- This message was sent by Atlassian Jira (v8.13.1#813001)