ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From roar109 <roar...@gmail.com>
Subject Re: Cache put operation blocked in cluster
Date Thu, 13 Aug 2015 21:55:19 GMT
Yes Val,

I pasted here:
https://gist.github.com/roar109/8d9a39b6b424cf3cd465
This is from node 01 after I start node 02 and hit the HealthCheck in node
02.

The output of the node 02 is only this:
2015-08-13 16:47:39,488 33047      INFO  [http-/0.0.0.0:8082-4     ]
rest.HealthCheckRest      (     HealthCheckRest.java:   53) - Calling Rest
healthCheckTest method...
2015-08-13 16:47:40,408 33967      WARN  [ignite-#70%p2p-datafabric]
log4j.Log4JLogger         (         Log4JLogger.java:  463) - Failed to find
local deployment for peer request: GridDeploymentRequest
[rsrcName=org/apache/activemq/ActiveMQConnectionFactory.class,
ldrId=40038092f41-cca96f76-2f61-4817-97e3-788bbc060f68, isUndeploy=false,
nodeIds=null]

To refresh the main idea behind this is that the Healthcheck writes to the
cache, and we register an event listener so when detect a PUT event to the 
cache it rises an event that only print and sends a jms message.

The ActiveMQ jars we only have that ones in the HealthCheck war not the
other that is the on in charge or create "Ignite.start".



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Cache-put-operation-blocked-in-cluster-tp955p964.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Mime
View raw message