6 Replies Latest reply on Feb 2, 2007 9:47 PM by Ovidiu Feodorov

    Messaging 1.0.1SP2 problems

    Alfred Thomas Newbie

      Hi

      I have installed messaging 1.0.1 SP2 on JBoss 4.0.5GA. And I keep getting the following exception:

      20:14:23,921 ERROR [ServerThread] failed to process invocation.
      java.io.IOException: Can not read data for version 6. Supported versions: 1,2
      at org.jboss.remoting.transport.socket.ServerThread.versionedRead(ServerThread.java:426)
      at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:478)
      at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:631)
      at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:293)

      I have read somewhere that SP2's installer does not copy the right jboss-remoting.jar in the lib folder but I have tried replacing that manually and that still does not work. Does anyone have any ideas?
      I also see on JIRA that SP3 is finished. When will this be available?

      Regards
      Alfred Thomas

        • 1. Re: Messaging 1.0.1SP2 problems
          Ovidiu Feodorov Master

          The installer is not supposed to copy jboss-remoting.jar in lib, since in JBoss 4.0.5, Messaging is scoped. You probably refer to http://jira.jboss.org/jira/browse/JBMESSAGING-682 which was closed as "Won't Fix".

          Besides, before release, we run smoke tests that independenty perform the installation procedure and verify if the result is functional.

          Replacing lib/jboss-remoting.jar manually will break things even worse.

          Most likely, you're not using the right jboss-messaging-client.jar in your client path.

          • 2. Re: Messaging 1.0.1SP2 problems
            Ovidiu Feodorov Master

            SP3 is not released publicly. SP4 will be.

            • 3. Re: Messaging 1.0.1SP2 problems
              Alfred Thomas Newbie

              Hi Ovidiu

              Thanks for the response. Ok I started from scratch and this is what I did.
              - Uninstalled JBoss and deleted the JBoss directory.
              - Made sure that there isn't any jboss-messaging-client.jar lying around.
              - Installed JBoss 4.0.5 GA.
              - Installed JBM 1.0.1 SP2 and successfully ran the queue example.
              - Included the jboss-messaging-client.jar that is in the JBM 1.0.1 directory (After unpacking the JBM zip) in my application.

              When I run my application I still get "Failed to config client side AOP
              " on my client side and "Can not read data for version 6. Supported versions: 1,2" on the server side.

              I am stuck with this, any ideas where I'm going wrong?

              Regards
              Alfred

              • 4. Re: Messaging 1.0.1SP2 problems
                Garth Newbie

                It would be nice to get a warning that this service pack 2 does not work in JBoss 4.0.5 before someone like me spends hours on trying to make it work.
                Garth

                • 5. Re: Messaging 1.0.1SP2 problems
                  Tim Fox Master

                  As part of the release procedure, JBM is automatically tested against various configurations of JBAS, including 4.0.5.

                  So we know it works, what is your specific problem?

                  • 6. Re: Messaging 1.0.1SP2 problems
                    Ovidiu Feodorov Master

                     

                    "foxviewn2632" wrote:
                    It would be nice to get a warning that this service pack 2 does not work in JBoss 4.0.5 before someone like me spends hours on trying to make it work.
                    Garth


                    Garth

                    As Tim said, SP2 does work with 4.0.5.

                    If you don't want to take my word for it, just unzip a standard SP2 installation bundle, and go to the test-results directory. There you'll find a smoke-test-report.java-1.4.2_12.html and smoke-test-report.java-1.5.0_07.html, which are the results of our smoke test suite ran with Java 1.4.2_12 and Java 1.5.0_07 during the release process. You'll see that 4.0.5.GA (scoped) has a full green bar, for both java versions.

                    Now, it's more than possible that you've stumbled over a configuration or set up issues that we didn't test for. Bugs will be always part of our life as software developers. If you would be so kind to provide us with more info, all of us we could achieve two things:
                    1. You'll (possibly) get your problem solved.
                    2. We'll (possibly) add a new smoke test to our test suite that will make sure the error condition you ran into won't happen in the next releases.