The error message itself contains a fairly detailed explanation of the cause and what to do about it:

Connection failure has been detected: HQ119014: Did not receive data from /10.64.0.102:38378. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information.

Here are some follow-up questions based on this information:

• Are any of your clients crashing?
• Are all of your clients closing their JMS connections properly?
• Are you having any network failures or latency issues?
• What are you connection-ttl and client-failure-check-period settings and have you tried adjusting them?

I recommend a more thorough investigation of the network infrastructure that is used for your HornetQ client/server connections.

Also, read this.

Tip: if you modify connection-ttl it's almost always a good idea to modify client-failure-check-period as well.

I'm getting same err.  Starting with brand new EAP 6.3 configuration.  Started server, compiled/ran/tested the helloworld-mdb quickstart.  Used mvn jboss-as:undeploy to get rid of it, and a restart shows the server starts find but then after a few seconds the same errors as above show up.

I'm using standalone-full and JRE 1.7.0_65.

Cleared the data dir and restarted, same errors.

Doesn't make sense - I don't have anything deployed....

17:01:14,759 INFO  [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.3.0.GA (AS 7.4.0.Final-redhat-19) started in 3965ms - Started 190 of 227 services (67 services are lazy, passive or on-demand)

17:02:36,083 WARN  [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]
17:02:36,083 WARN  [org.hornetq.jms.server] (Thread-0 (HornetQ-client-global-threads-143832278)) Notified of connection failure in xa discovery, we will retry on the next recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119006: Channel disconnected]
at org.hornetq.core.client.impl.ClientSessionFactoryImpl.connectionDestroyed(ClientSessionFactoryImpl.java:425) [hornetq-core-client-2.3.20.Final-redhat-1.jar:2.3.20.Final-redhat-1]
at org.hornetq.core.remoting.impl.invm.InVMConnector$Listener$1.run(InVMConnector.java:214) [hornetq-server-2.3.20.Final-redhat-1.jar:2.3.20.Final-redhat-1]
at org.hornetq.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105) [hornetq-core-client-2.3.20.Final-redhat-1.jar:2.3.20.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_65]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_65]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_65]

17:04:30,184 WARN  [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

17:04:30,184 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222061: Client connection failed, clearing up resources for session a512b403-7048-11e4-8332-4f4846b3b419

17:04:30,184 WARN  [org.hornetq.core.server] (hornetq-failure-check-thread) HQ222107: Cleared up resources for session a512b403-7048-11e4-8332-4f4846b3b419

17:04:30,184 WARN  [org.hornetq.core.client] (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. You also might have configured connection-ttl and client-failure-check-period incorrectly. Please check user manual for more information. The connection will now be closed. [code=CONNECTION_TIMEDOUT]

17:04:30,184 WARN  [org.hornetq.jms.server] (Thread-0 (HornetQ-client-global-threads-143832278)) Notified of connection failure in xa discovery, we will retry on the next recovery: HornetQException[errorType=NOT_CONNECTED message=HQ119006: Channel disconnected]

You should be able to fix this with either an upgrade to Wildfly or a configuration adjustment (see previously linked documentation for more on that).

By the way, whether you deploy any application(s) or not the failed XA transaction recovery process still runs and uses a connection.