1 2 Previous Next 22 Replies Latest reply on Sep 21, 2006 12:59 PM by ovidiu.feodorov Go to original post
      • 15. Re: JBoss Messaging locked up
        timfox

        Your environment sounds pretty messed up.

        You get this error when you attempt to run JDK1.5 compiled classes using JDK1.4

        The actual class is java.lang.Object (!), so you probably have the JDK1.5 rt.jar on your classpath.

        • 16. Re: JBoss Messaging locked up
          etolson

          We use 1.5, so yes I have the JDK 1.5 rt.jar on my classpath - does JBoss messaging require Java 1.4?

          • 17. Re: JBoss Messaging locked up
            anshah1

            Nope not really, I;ve been running it with Java 1.5 all this while..

            Anuj

            • 18. Re: JBoss Messaging locked up
              timfox

              This is nothing to do with JBoss Messaging.

              This is a JVM error, you are attempting to run classes compiled using JDK1.5 inside a version 1.4 JVM.

              The JVM won't allow you to do that.

              • 19. Re: JBoss Messaging locked up
                timfox

                Actually this is happening at the compile stage, but the principle is the same.

                Solution:

                Use JDK1.5 compiler, OR use JDK1.4 compiler and remove the JDK 1.5 rt.jar from your classpath.

                Also, next time you get an error you don't understand, try googling for it first. :)

                In this case you would have found the solution very quickly.......

                • 20. Re: JBoss Messaging locked up
                  ovidiu.feodorov

                  Regarding your initial issue, the fact that you're getting JBossMQ instead of Messaging, your startup log shows clearly you're running a clustered configuration:

                  15:01:18,212 INFO [STDOUT]
                  -------------------------------------------------------
                  GMS: address is as4:49654 (additional data: 18 bytes)
                  -------------------------------------------------------
                  15:01:20,260 INFO [com] Number of cluster members: 1
                  15:01:20,260 INFO [com] Other members: 0



                  What probably happens is that your "default" configuration is modified and the messaging istallation script gets confused.

                  If you want to see Messaging running, do this:

                  1. Dowload a fresh JBoss 4.0.3 (or newer) installation bundle
                  2. Perform Messaging installation on that
                  3. run.sh -c messaging

                  • 21. Re: JBoss Messaging locked up
                    etolson

                    Oh ok, thanks.
                    Obviously, it's unfortunate that the installation doesn't work for clustered configurations.

                    • 22. Re: JBoss Messaging locked up
                      ovidiu.feodorov

                      There's nothing fundamental that precludes the installation script from working with the clustered configurations, it's just we didn't have time to do it.

                      Want to give it a try, and then contribute the patch?

                      1 2 Previous Next