-
1. Re: Jboss 7 ,how to migrate into infinispan 6
ctomc Feb 8, 2014 8:45 AM (in response to dinoop.p1)1 of 1 people found this helpfulEasiest way would be to migrate to WildFly 8 which already comes with Infinispan 6
-
2. Re: Jboss 7 ,how to migrate into infinispan 6
wdfink Feb 8, 2014 10:26 AM (in response to dinoop.p1)What is your use-case? If you run the library mode of infinispan you might pack it together with your applicaiton.
-
3. Re: Jboss 7 ,how to migrate into infinispan 6
dinoop.p1 Feb 8, 2014 3:08 PM (in response to dinoop.p1)I have got the method to migrate, Please look at this http://stackoverflow.com/questions/21644996/jboss-7-how-to-migrate-into-infinispan-6/
-
4. Re: Jboss 7 ,how to migrate into infinispan 6
rhusar Feb 19, 2014 10:27 AM (in response to dinoop.p1)Dinoop p wrote:
I have got the method to migrate, Please look at this http://stackoverflow.com/questions/21644996/jboss-7-how-to-migrate-into-infinispan-6/
Just two things to note:
- This is pretty much the same outcome as bundling with your application. If the added module is used by multiple deployments then there are advantages, otherwise shipping within one app seems more convenient.
- This will not replace the Infinispan version used for HTTP/SFSB/etc state replication.
-
5. Re: Jboss 7 ,how to migrate into infinispan 6
dinoop.p1 Feb 19, 2014 11:54 PM (in response to rhusar)Hi Radoslav,
My application has multiple deployments in the same Jboss and all are using Infinispan. As you said "This will not replace the Infinispan version used for HTTP/SFSB/etc state replication", will it make any issue if I use this manner?
Thank you,
Dinoop p
-
6. Re: Jboss 7 ,how to migrate into infinispan 6
rhusar Feb 27, 2014 7:41 AM (in response to dinoop.p1)Hmhm... I am thinking this shouldn't be a problem if you are not sharing caches accross deployments. As I said earlier, you might want to reduce the overall size and use the module approach instead of bundling with each deployment (i.e. library mode = you use Infinspan directly and not let it be managed by the AS7 container).
Rado
-
7. Re: Jboss 7 ,how to migrate into infinispan 6
dinoop.p1 Feb 28, 2014 12:28 AM (in response to rhusar)I am sharing cache across deployment and also want to cluster it across different servers. What will be the problem comes, when we share caches across deployment in this manner?
-
8. Re: Jboss 7 ,how to migrate into infinispan 6
wdfink Feb 27, 2014 3:55 PM (in response to dinoop.p1)I think the problem is that if you share the same cache in different deployments you will have a high memory use in the same JVM as you duplicate the entries for each depend on the cache distribution.
-
9. Re: Jboss 7 ,how to migrate into infinispan 6
dinoop.p1 Feb 28, 2014 12:50 AM (in response to wdfink)Wolf-Dieter Fink, my application structure is like, a static EmbeddedCacheManager instance is shared among all deployments via a class file resides in JBOSS/modules/com/mycompany/main/myapp.jar file. I have added the global dependency to this modules for all deployments. Only a single CacheManager instance is assured by using a AtomicBoolean in the same class. In this case how the duplicate entries will come, because only single cache manager is created.
If I misunderstood the concept, please advice me.
-
10. Re: Jboss 7 ,how to migrate into infinispan 6
rhusar Mar 18, 2014 11:34 AM (in response to dinoop.p1)Dinoop p wrote:
Wolf-Dieter Fink, my application structure is like, a static EmbeddedCacheManager instance is shared among all deployments via a class file resides in JBOSS/modules/com/mycompany/main/myapp.jar file. I have added the global dependency to this modules for all deployments. Only a single CacheManager instance is assured by using a AtomicBoolean in the same class. In this case how the duplicate entries will come, because only single cache manager is created.
If I misunderstood the concept, please advice me.
If I read correctly, I don't see any entry duplication in this case, there is just one cache per JVM.