5 Replies Latest reply on May 30, 2017 7:00 AM by Tristan Tarrant

    Migrating infinispan from Jboss 1.6 to Jboss 1.5

    Gurleen Kaur Newbie

      Hi,

       

      Can some one please help me in achieving the migration from JBOSS 1.6 to 1.5 especially use of infinispan.

      This infinispan cache is use for live chatting mechanism. Can some one please provide me an example or a way to achieve the same.

       

      Thanks,

        • 1. Re: Migrating infinispan from Jboss 1.6 to Jboss 1.5
          Tristan Tarrant Master

          Sorry Gurleen, but I don't understand what you are referring to.

          The first version of JBoss Application Server with Infinispan was 7.0. The version numbers you mention look more like JDK versions.

          Please add the details about what you are trying to do so we can help you

           

          Tristan

          • 2. Re: Migrating infinispan from Jboss 1.6 to Jboss 1.5
            Gurleen Kaur Newbie

            Hi Tristan,

             

            Currently our application is using JBOSS EAP 6.1 and jars -

            infinispan-cachestore-jdbc-5.2.6.Final-redhat-1.jar

            infinispan-cachestore-remote-5.2.6.Final-redhat-1.jar

            infinispan-client-hotrod-5.2.6.Final-redhat-1.jar

            infinispan-core-5.2.6.Final-redhat-1.jar

             

            Now we have requirement to downgrade from JBOSS EAP 6.1  to JBOSS EAP 5.1. When the same infinispan Jar (and jboss-logging-3.1.0.GA.jar) were added to JBOSS EAP 5.1 lib and the server started we are facing an exception -

             

            [org.jboss.detailed.classloader.ClassLoaderManager] Unexpected error during load of:org.jboss.logging.BasicLogger

            java.lang.SecurityException: class "org.jboss.logging.BasicLogger"'s signer information does not match signer information of other classes in the same package

                    at java.lang.ClassLoader.checkCerts(ClassLoader.java:806)

                    at java.lang.ClassLoader.preDefineClass(ClassLoader.java:487)

                    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:625)

                    at java.lang.ClassLoader.defineClass(ClassLoader.java:615)

                    at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:63)

                    at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:572)

                    at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:532)

                    at java.security.AccessController.doPrivileged(Native Method)

                    at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:530)

                    at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:507)

                    at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:134)

                    at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)

                    at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:452)

                    at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:267)

                    at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:166)

                    at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:265)

                    at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1119)

                    at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:798)

                    at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:441)

                    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)

                    at java.lang.ClassLoader.defineClass1(Native Method)

                    at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)

                    at java.lang.ClassLoader.defineClass(ClassLoader.java:615)

                    at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:63)

                    at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:572)

                    at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:532)

                    at java.security.AccessController.doPrivileged(Native Method)

             

            Can you please help us in resolving above exception.

            • 3. Re: Migrating infinispan from Jboss 1.6 to Jboss 1.5
              Tristan Tarrant Master

              Firstly: what you are trying to do will invalidate any kind of support.

              Also, the jars that come with the product have been signed. If you don't care about losing support and generally other possible breakage, you could remove any META-INF/MKSIGN.* files from the jars, but I would not recommend it.

              May I ask why you have to downgrade the application server ?

              • 4. Re: Migrating infinispan from Jboss 1.6 to Jboss 1.5
                Gurleen Kaur Newbie

                Actually we not downgrading it we are moving some feature to earlier version of our product which is in JBOSS 5.What is the feasiblity of using any other alternative for caching.

                • 5. Re: Migrating infinispan from Jboss 1.6 to Jboss 1.5
                  Tristan Tarrant Master

                  You can embed the jars in your deployment.