While rewriting client channel usage it was found that TxFunctionalTest would fail the write version check for the update test.

This is due to the server using a VersionGenerator that does not think it is clustered, even though it should be. The underlying cause appears to be the start method is never invoked on the component retrieved at https://github.com/infinispan/infinispan/blob/e9d227d6df1e9a1a5034737dbab2c37b2c82a7d1/server/hotrod/src/main/java/org/infinispan/server/hotrod/HotRodServer.java#L632 so the isClustered variable is never set.

You can reproduce this on main by commenting out https://github.com/infinispan/infinispan/blob/e9d227d6df1e9a1a5034737dbab2c37b2c82a7d1/client/hotrod-client/src/main/java/org/infinispan/client/hotrod/impl/transaction/operations/PrepareTransactionOperation.java#L91 and always invoking on a random server and running TxFunctionalTest.