![]() You also might have configured connection-ttl and client-failure-check-period incorrectly. It is likely the client has exited or crashed without closing its connection, or the network between the server and client has failed. ![]() 17:02:36,083 WARN (Thread-0 (HornetQ-client-global-threads-143832278)) Notified of connection failure in xa discovery, we will retry on the next recovery: HornetQException at .(ClientSessionFactoryImpl.java:425) at .$Listener$1.run(InVMConnector.java:214) at $OrderedExecutor$1.run(OrderedExecutorFactory.java:105) at .runWorker(ThreadPoolExecutor.java:1145) at $n(ThreadPoolExecutor.java:615) at (Thread.java:745) ġ7:04:30,184 WARN (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. ![]() Please check user manual for more information. I'm using standalone-full and JRE 1.7.0_65.Ĭleared the data dir and restarted, same errors.ĭoesn't make sense - I don't have anything deployed.ġ7:01:14,759 INFO (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)ġ7:02:36,083 WARN (hornetq-failure-check-thread) HQ212037: Connection failure has been detected: HQ119014: Did not receive data from invm:0. 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. Started server, compiled/ran/tested the helloworld-mdb quickstart. Starting with brand new EAP 6.3 configuration. Do I need to change / add the parameters or is this a firewall / network issue. How can i figure out what is the problem. What does changes is just the port after the ip. I am running this on the server with following ip 10.64.0.102 and getting the whole time these warnings:ġ8:51:06,131 WARN HQ212037: Connection failure has been detected: HQ119014: Did not receive data from /10.64.0.102:38378.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |