1 2 Previous Next 15 Replies Latest reply on Jul 2, 2007 10:20 AM by Kevin Conner

    Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3

    toby saville Novice

      Installed JBoss AS 4.2.0.GA
      Installed JBoss ESB 4.2MR2
      Installed JBossMessaging 1.3.0.GA

      I deployed the helloworld sample successfully. Then attempted to run the ant target ?runtest? but got the following exception:
      Root exception is java.io.InvalidClassException: org.jboss.jms.client.delegate.DelegateSupport; local class incompatible: stream classdesc serialVersionUID = -1362079381836473747, local class serialVersionUID = -1723908125830723356

      I then followed the thread here:
      http://www.jboss.org/index.html?module=bb&op=viewtopic&t=105433
      and copied jboss-messaging-client.jar from my JBossMessaging folder into $ESB_HOME/lib/ext
      I then got the following error:
      java.lang.NoClassDefFoundError: org/jboss/aop/Advised

      I could find this class and put it on the client classpath, but I want to understand why this error arose. Any suggestions?

      thanks,
      - toby

        • 1. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
          Kurt Stam Master

          MR2 does not have the right client jars for JBossMessaging 1.3.0 GA. You can either figure out on you own which jars to upgrade, or use the current trunk, or JBossMessaging 1.2.

          --Kurt

          • 2. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
            Burr Sutter Master

            I ran into a similar situation. I just updated jboss-messaging.jar AND recompiled and all was well. You'll obviously need source to pull this trick off.

            You might stick with JBossMQ if you are using AS (App Server). If you are using ESB Server (ES) then JBoss Messaging is the default.

            You'll need to tweak the quickstart code in 4.2MR2 to correctly use the right JMS destination syntax. In SVN, Kevin (I think) was kind enough to fix up our base-build.xml (quickstarts/conf) to handle the deliver of the correct JMS destination config file.

            • 3. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
              Mark Little Master

              JBoss Messaging can be deployed in AS 4.2, so you may want to look at that too.

              • 4. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                toby saville Novice

                Hi,

                thanks for the responses.

                im the first to admit that the problems i am experiencing is due to my own inability but nothing about this ESB seems straightforward.

                i installed JBoss Messaging 1.2 into its own server config (as per the ant script), then deployed the ESB to this config, then the helloworld.esb archive to the same config but the AS didnt seem to notice this deployment, and hence no queues were created and subsequently the runtest failed.

                so i tried running the esb server on its own, but i get an error when running the ant script, telling me: JBossESB must be built.

                so i try to build from the source but i get Illegal character warnings for the file default/deploy/jbossesb.sar/esb.juddi.properties (trying to create a url from this filename?) when the server is starting

                so i revert back to trying with JBossMQ (which im assuming is discouraged due to JBossMessaging being the default implementation going forward?) and had to edit the ant scripts and deployed files to get the hellowrld to work.

                whilst im the first to admit im not a whiz, i thought it would be easier to get the helloworld sample working.

                but it has to be said, you guys are excellent support.

                - toby

                • 5. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                  Mark Little Master

                   

                  "tobysaville" wrote:
                  Hi,

                  thanks for the responses.

                  im the first to admit that the problems i am experiencing is due to my own inability but nothing about this ESB seems straightforward.


                  Well once we get you over this hurdle let us know specifics so we can address them.


                  i installed JBoss Messaging 1.2 into its own server config (as per the ant script), then deployed the ESB to this config, then the helloworld.esb archive to the same config but the AS didnt seem to notice this deployment, and hence no queues were created and subsequently the runtest failed.

                  so i tried running the esb server on its own, but i get an error when running the ant script, telling me: JBossESB must be built.

                  so i try to build from the source but i get Illegal character warnings for the file default/deploy/jbossesb.sar/esb.juddi.properties (trying to create a url from this filename?) when the server is starting

                  so i revert back to trying with JBossMQ (which im assuming is discouraged due to JBossMessaging being the default implementation going forward?) and had to edit the ant scripts and deployed files to get the hellowrld to work.

                  whilst im the first to admit im not a whiz, i thought it would be easier to get the helloworld sample working.


                  It should be. Can I just confirm that you're using the latest trunk? As Burr and Kurt pointed out, we've made a lot of progress (or so we thought!) since the last MR2 release and definitely since the last GA release. Particularly around the quickstarts.


                  but it has to be said, you guys are excellent support.

                  - toby


                  Hey, at least we get one thing right ;-)

                  • 6. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                    toby saville Novice

                    Hi Mark,

                    I am using the following SVN repo, and updated and recompiled just before posting that last message:

                    http://anonsvn.labs.jboss.com/labs/jbossesb/trunk

                    this means im using the latest trunk doesnt it?

                    cheers,
                    Toby

                    • 7. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                      Mark Little Master

                      Yes, that's the latest and should support JBoss Messaging out-of-the-box. I think Kevin was working on improving the quickstarts a while back and did work around the JMS based ones, so I'll ask him to double check this. Thanks.

                      • 8. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                        Kevin Conner Master

                         

                        "mark.little@jboss.com" wrote:
                        Yes, that's the latest and should support JBoss Messaging out-of-the-box. I think Kevin was working on improving the quickstarts a while back and did work around the JMS based ones, so I'll ask him to double check this. Thanks.

                        The quickstarts should still be functioning but I will double check.

                        • 9. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                          Kevin Conner Master

                          I have just done the following to test this out (based on svn revision 12947).

                          - install clean version of 4.2.0.GA
                          - installed jboss messaging 1.3.0 (ant -f release-admin.xml)

                          From within jbossesb/product
                          - edit install/deployment.properties to reflect 4.2.0.GA location and messaging server
                          - ant clean deploy

                          From within a separate console
                          - bring up 4.2.0.GA (./run.sh -c messaging)

                          From within jbossesb/product/samples/quickstarts/helloworld
                          - ant clean deploy
                          - ant runtest

                          No need to initialise the quickstarts.properties file as the information is picked up from the deployment.properties.

                          Everything worked as expected.

                          I also did a similar test (again from a clean install) using the built jbossesb distribution. Installation of the ESB and execution of the quickstart went as expected.

                          • 10. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                            Kevin Conner Master

                            Toby, can you try again using the steps I have just posted?

                            Thanks.

                            • 11. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                              toby saville Novice

                              ill try them out now, and get back to you shortly

                              thanks for your help Kevin and Mark

                              - tobes

                              • 12. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                                toby saville Novice

                                Hi Kevin,

                                I was able to run helloworld sample perfectly thanks to your help. I can see now where i was going wrong.

                                thanks again!

                                oh, and while im here, thanks for the maven2 plugin, that is really useful to.

                                - tobes

                                • 13. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                                  Mark Little Master

                                  Is where you made a mistake something you think others would do? If so, let us know and we'll see if we should modify the docs.

                                  • 14. Re: Helloworld quickstart problem - ESB4.2, AS4.2 JBM1.3
                                    toby saville Novice

                                    i think it was two issues.

                                    i was trying to run the server that i had built from the source as standalone from

                                    <SRC_ROOT>\product\build\jbossesb-server-4.2MR2.
                                    

                                    Instructions i read said to build with ant dist, i then assumed that we could run from this location. However i get the error:
                                     Illegal character in path at index 18: <src_root>/product/build/jbossesb-server-4.2MR2/server/default/deploy/jbossesb.sar/esb.juddi.properties
                                    


                                    the other issue was because i wasnt running the messaging server config (run.sh -c messaging) created by default when installing JBossMessaing from the ant script, simply because i didnt understand how it was activated (i dont think others would make that mistake)

                                    basically, my problems were caused by me, not you guys.

                                    perhaps wiki entries could be made that provide obtuse step-by-step guides to getting the configuration right? I don't have much experience in any aspect of JBoss so trying to get everything working together can be tricky at times.

                                    also i modified the build script a bit to check whether JBossMessaging or JBMQ was being used. I added the following property


                                    <condition property="jms.destinations.file.individual"
                                     value="jbm-queue-service.xml" else="jbmq-queue-service.xml">
                                     <available file="${org.jboss.esb.server.deploy.dir}/jboss-messaging.sar"/>
                                    </condition>
                                    


                                    I then changed the target called package-deployment so that it included that property value instead of the static file name jbm-queue-service.xml
                                    <fileset dir="${basedir}" includes="${jms.destinations.file.individual}"/>
                                    

                                    The only thing remaining is to change the values in the deployment.xml file between jboss.mq.destination and jboss.messaging.destination. I do this by hand, only because of limited ant knowledge - if this could be done on the fly at build time, you wouldnt know what JMS implementation you were using for the helloworld sample.

                                    hope that makes sense.
                                    - tobes

                                    1 2 Previous Next