1 2 Previous Next 21 Replies Latest reply on Dec 2, 2010 11:53 AM by galder.zamarreno Go to original post
      • 15. Re: NPE with Infinispan 4.1.0-Final and Hib-infinispan-3.5.5-Final
        galder.zamarreno

        Hmmm, that's odd. The default factory used should be DefaultSharedScheduledExecutorFactory. Could you create a JIRA issue in https://jira.jboss.org/browse/ISPN so that we can investigate this? If you're using a different Infinispan config to the one shipped by default with Infinispan Hibernate 2LC, please attach it.

         

        Please also give us a rough idea of the number of entites/collections that your system uses and attach a thread dump log file so that we can inspect those eviction threads.

        • 16. Re: NPE with Infinispan 4.1.0-Final and Hib-infinispan-3.5.5-Final
          galder.zamarreno

          Chris, I think there's something not working fully as expected here, see https://jira.jboss.org/browse/ISPN-766

          • 17. Re: NPE with Infinispan 4.1.0-Final and Hib-infinispan-3.5.5-Final
            galder.zamarreno

            Chris, there was a lapsus, the issue should be fixed now. If you wanna have another go, clone our Infinispan Git repo and build the 4.2.x branch. More info in http://community.jboss.org/docs/DOC-16089

            • 18. Re: NPE with Infinispan 4.1.0-Final and Hib-infinispan-3.5.5-Final
              tlvenn

              Thanks Galder, just did it and it works now !

              Building for GIT was easy however I had to tweak the parent pom to add jboss nexus public repo as artifact repo and plugin repo, you might want to add it to the parent pom directly so people can checkout IS from GIT and build it right away.

               

              Aside from that, there is one more thing I think that could be improved is the time it takes to create/register caches. Before with EhCache, we barely noticed it but now, we got a 10seconds pause each time we start the JVM. Obvisouly this is a dev issue not a production one but nonetheless it would be very nice to see if there is a few tweaks that would speed up our startup time.

               

              Here is the snippet of my dev log:

              12:14:16,115 [main] INFO  infinispan.factories.GlobalComponentRegistry - [No session]Infinispan version: Infinispan 'Ursus' 4.2.0-SNAPSHOT
              12:14:26,995 [main] INFO  core.controller.IndexManagerImpl - [No session]Building indices for com.xxx

              --> Almost 10 seconds to create 370 caches

               

              Thanks !

              • 19. Re: NPE with Infinispan 4.1.0-Final and Hib-infinispan-3.5.5-Final
                galder.zamarreno

                Chris Meunier wrote:

                 

                Thanks Galder, just did it and it works now !

                Building for GIT was easy however I had to tweak the parent pom to add jboss nexus public repo as artifact repo and plugin repo, you might want to add it to the parent pom directly so people can checkout IS from GIT and build it right away.

                 

                We're aware of this, hence we have a wiki on Infinispan and Maven: http://community.jboss.org/docs/DOC-15189

                Aside from that, there is one more thing I think that could be improved is the time it takes to create/register caches. Before with EhCache, we barely noticed it but now, we got a 10seconds pause each time we start the JVM. Obvisouly this is a dev issue not a production one but nonetheless it would be very nice to see if there is a few tweaks that would speed up our startup time.

                 

                Here is the snippet of my dev log:

                12:14:16,115 [main] INFO  infinispan.factories.GlobalComponentRegistry - [No session]Infinispan version: Infinispan 'Ursus' 4.2.0-SNAPSHOT
                12:14:26,995 [main] INFO  core.controller.IndexManagerImpl - [No session]Building indices for com.xxx

                --> Almost 10 seconds to create 370 caches

                 

                Thanks !

                 

                Hmmm, we use the same API for retrieval/creation of caches and this is via CacheContainer.getCache(). Due to potential concurrent requests for caches, we had to add some locks to avoid issues with concurrent creation of same caches. In your case though, I imagine all the caches are created first, by a single thread, and then, when the app is loaded, they're retrieved.

                 

                I wonder if you could share your use case with us? I'd like to run your use case here so that I can see in more detail what is going on and see if we can optimise it a better.

                • 20. Re: NPE with Infinispan 4.1.0-Final and Hib-infinispan-3.5.5-Final
                  galder.zamarreno

                  Chris, for 4.2.0.CR3, we've added some optimizations around cache creation. It'd be interesting to see how they work for your use case. It'd be good as well if you could share your use case with us to be able to optimise things further

                  • 21. Re: NPE with Infinispan 4.1.0-Final and Hib-infinispan-3.5.5-Final
                    galder.zamarreno
                    1 2 Previous Next