[ https://issues.jboss.org/browse/WFLY-11750?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-11750: ------------------------------------- [~tomekadamski] Thanks for elaborating - I think I understand the issue now. {quote}But if I understand correctly HA features and correct transaction recovery are independent. {quote} Correct. {quote}As a result, the client has a record in its permanent object store and tries to finish the transaction. As the record contains the IP address of the failed node the client will wait till the server is up again to finish the transaction.{quote} The address would have been obtained from the service URL of the ejb client connection. {quote}That node will have the new cluster identity. My understanding is that it has no effect on transaction recovery which will work fine.{quote} Correct. {quote}But the key thing here IMO is, the way remoting gets node information.{quote} Agreed. The server supplies this information via client mappings, the destination address for which is stored and supplied as a string. Thus the server *should* already be capable of seeding the client with a hostname instead of an IP address. However, I suspect that the address used by the transaction client is taken from the remote connection itself - which likely use the resolved destination address (as the established connection will have already resolved the host name), rather than preferring the host name over the address, if it exists. {quote}Another thing: does clustering takes care of replicating Narayana object store? If this is the case then the problem would be different.{quote} Clustering does not currently perform any state replication on behalf of the the Narayana object store. -- This message was sent by Atlassian Jira (v7.12.1#712002)