Invalid value xa for transaction warning on WildFly-16

valsaraj007 Jun 27, 2019 4:21 AM

WARN [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 24) WFLYMSGAMQ0101: Invalid value xa for transaction, legal values are [local, none, xa], default value is applied.

Found the following warning on startup. What might be wrong?

1. Re: Invalid value xa for transaction warning on WildFly-16

pbarate Jun 27, 2019 6:10 AM (in response to valsaraj007)

This is a known issue in wildfly 16 and it is addressed in [WFLY-11827] Broken validation for pooled-connection-factory's transaction attribute. - JBoss Issue Tracker.
The fix for this issue is available in wildfly 17.0.0.
Actions
2. Re: Invalid value xa for transaction warning on WildFly-16

jaikiran Jun 27, 2019 7:14 AM (in response to valsaraj007)

This was fixed in [WFLY-11827] Broken validation for pooled-connection-factory's transaction attribute. - JBoss Issue Tracker and is available as part of the latest released 17.0.0.Final of WildFly.
1 of 1 people found this helpful
Actions
3. Re: Invalid value xa for transaction warning on WildFly-16

valsaraj007 Jun 27, 2019 10:25 AM (in response to jaikiran)

Thanks!
What is the impact of this issue? Is this just warning on startup?
Is wildFly-17 supports OpenJDK 8?
Actions
4. Re: Invalid value xa for transaction warning on WildFly-16

jaikiran Jun 27, 2019 11:58 PM (in response to valsaraj007)

In this case it's a harmless WARN message since it anyway defaults to the "xa" value.

Is wildFly-17 supports OpenJDK 8?
Java 8 is supported, yes.
Actions
5. Re: Invalid value xa for transaction warning on WildFly-16

valsaraj007 Jun 28, 2019 2:59 AM (in response to jaikiran)

Thanks for clarification!

Would you confirm this, if possible?
Is enable-http2 = true production ready?
Actions

Go to original post