-
15. Re: Infinispan : cache not found on node 2 issue
anupshandilya Nov 14, 2017 8:43 AM (in response to pferraro)Ok Thanks. We will upgrade above listed jars only then.
-
16. Re: Infinispan : cache not found on node 2 issue
anupshandilya Nov 21, 2017 1:02 PM (in response to pferraro)Hi Paul,
We upgraded infinispan jars stated above on wildfly 10.
After that, transport channel created for a replicated cache container is not forming cluster with corresponding replicated cache on another node.
This seems to work with wildfly 11 though.
I created a sample application where application on node1 writes data into replicated cache while another application on node2 consumes it. Both use "tcp"
It seems to work on wildfly 11. Please check logs attached of both 11 and 10
Testcase:widfly 11 and 10
1. started wfly11_node1. data written to cache
2. started wfly11_node2. data read successfully from cache
Outcome : works on 11 but not on 10
Could you please tell what other jars should we upgrade for this to work without any impacts ? Or is it essential to upgrade to wildfly 11 ?
2017-11-21 23:20:27,563 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "InfinispanRetrieveData-0.0.1-SNAPSHOT.jar")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined} 2017-11-21 23:20:27,567 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "infinispan"), ("cache-container" => "InfinispanContainer"), ("replicated-cache" => "if-cache") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined} 2017-11-21 23:20:27,569 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "infinispan"), ("cache-container" => "InfinispanContainer"), ("replicated-cache" => "if-cache-2") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined} 2017-11-21 23:20:27,569 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "infinispan"), ("cache-container" => "InfinispanContainer"), ("replicated-cache" => "if-cache"), ("component" => "backup-for") ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => undefined} 2017-11-21 23:20:27,570 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "infinispan"), ("cache-container" => "InfinispanContainer"), ("replicated-cache" => "if-cache"), ("component" => "backups") ....
Data push application
@Singleton @Startup @ConcurrencyManagement public class InfinispanCacheManager { @Resource(name="ReplicatedCache") Cache<String,String> cache; @Resource(name="ReplicatedCache-2") Cache<String,String> cache2; public InfinispanCacheManager() { System.out.println("constructing IC manager :"+cache); } @PostConstruct public void init() { System.out.println("Inserting data to infinispan replicated cache"); cache.put("ThisIsTheKey","HereIsTheValueForKey"); System.out.println("Insertion successfull "+cache.get("ThisIsTheKey")); }
@PreDestroy public void destroy() { }
Data retrieve application
@Singleton @Startup @ConcurrencyManagement public class InfinispanDataRetrieve { @Resource(name="ReplicatedCache") Cache<String,String> cache; @Resource(name="ReplicatedCache-2") Cache<String,String> cache2; public InfinispanDataRetrieve() { System.out.println("constructing IC manager :"+cache); } @PostConstruct public void init() { System.out.println("Getting data for key ThisIsTheKey "); System.out.println(cache.get("ThisIsTheKey")); } @PreDestroy public void destroy() { } }
-
17. Re: Infinispan : cache not found on node 2 issue
anupshandilya Nov 22, 2017 7:07 AM (in response to anupshandilya)Hi Paul,
Please ignore above query of mine. I had misconfigured application on node2.
Thanks