11 Replies Latest reply on Sep 28, 2006 3:07 PM by Kurt Stam

    Trailblazer deployment problem

    Randy Beck Newbie

      I have installed the jbossesb-4.0Beta1.zip binary and have run the test example successfully.
      I then ran ant configure in bankloanbrokerdemo without error, and ant deploy went fine.
      I did have to edit the paths in build.xml and loanbroker.properties, as mentioned in other posts. I can browse to myhost:8080/jbossws/services and see that I have a web service running:
      jboss.ws:di=loanbroker.war,port=LoanBrokerWSPort,service=LoanBrokerWSService

      But when I try to run ant runListener, I get a failure:

      [java] Using configFile=conf/LoanBrokerConfig.xml
      [java] 15:51:32,657 INFO [ParamFileRepository] Setting parameter repository root dir to [/usr/local/JBossESB4.0Beta1/docs/samples/trailblazer/bankloanbrokerdemo/.]
      [java] 15:51:32,872 FATAL [GpListener] Problems with initial parameter load - <conf/LoanBrokerConfig.xml>
      [java] javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.jms.client.JBossConnectionFactory

      I cannot figure out why the class is not found. I can see that loanbroker.jar is in build/dist/lib

        • 1. Re: Trailblazer deployment problem
          Kurt Stam Master

          Hi Rob,

          It is missing a jms library. Can you check your loanbroker.properties and make sure the home of your JBoss Appserver Install
          org.jboss.soa.esb.samples.loanbroker.jboss_home is set correctly, pointing to the the root of your JBossAS? For example mine is set to:

          org.jboss.soa.esb.samples.loanbroker.jboss_home=C:/cygwin/home/kstam/apps/jboss-4.0.4.GA/

          Let me know if that fixes things.

          thx,

          --Kurt

          • 2. Re: Trailblazer deployment problem
            Kurt Stam Master

            Hey Randy, sorry for calling you Rob. It's still early for me..

            • 3. Re: Trailblazer deployment problem
              Kurt Stam Master

              Something is weird is going on. I don't think jboss-4.0.4 has this class anymore. Are you using jboss-4.0.4.GA? It really shouldn't be looking for this class. Can you make sure you don't don't have some JBOSS_HOME variable still pointing somewhere else?

              • 4. Re: Trailblazer deployment problem
                Daniel Brum Novice

                Randy, Rob, all the same thing in Dutch no? ;-)

                Definetely config error - there is missing JAR in the classpath, or a wrong JAR in the classpath that it's trying to find in the JBOSS_HOME.

                You should have JBoss AS 4.0.4 with the EJB3 installer. You need to use the installer version of JBoss AS, and it will install the proper JDK 1.5 JBoss Messaging JAR.

                • 5. Re: Trailblazer deployment problem
                  Randy Beck Newbie

                  Kurt and Daniel,
                  My loanbroker.properties:
                  org.jboss.soa.esb.samples.loanbroker.jboss_home=/usr/local/jboss
                  which does point to my jboss root directory

                  I used the installer
                  jboss-4.0.4.GA-Patch1-installer.jar
                  to install jboss, and selected EJB3 during the install. I also copied the two missing files, properties-service.xml and properties-plugin.jar, from jboss-4.0.4.GA.zip per the JBoss ESB Getting Started guide. This is the first and only install on this server, so no cruft from previous installs.

                  I also installed jboss-messaging-1.0.1.CR4.zip if that matters, and run jboss using that configuration.

                  During the install of JBoss ESB, I was a little confused as to what I was supposed to do. I finally figured out that the instructions in the Getting Started guide apply to using the svn distribution, and the README.TXT instructions apply to the binary distribution. I followed the README.TXT instructions, allowing for differences in the file paths. I also had to create the file jbossEsbObjstore.xml in JBOSS_HOME/server/messaging/conf

                  So my JBoss ESB install actually amounted to:
                  copy jbossesb-appl.ear to JBOSS_HOME/server/messaging/deploy
                  copy jbossEsb.properties to JBOSS_HOME/server/messaging/conf
                  edit jbossEsb.properties
                  create jbossEsbObjstore.xml in JBOSS_HOME/server/messaging/conf
                  I had already configured jboss to use mysql as the database.

                  Hope that helps you help me.

                  Thanks,
                  Randy

                  • 6. Re: Trailblazer deployment problem
                    Kurt Stam Master

                    Currently we do not support jboss-messaging. I think this is what the problem is. We will in support it in the future. Is there any particular reason why you want to use it now?

                    --Kurt

                    • 7. Re: Trailblazer deployment problem
                      Kurt Stam Master

                      Hi Randy,

                      Note that our code only references the jms API, it should not care which provider is used. However jboss-4.0.4.GA comes with jboss-mq and messaging and mq don't play nice togther: see
                      http://labs.jboss.com/file-access/default/members/jbossmessaging/freezone/docs/guide-1.0.1.CR5/html/installation.html#install4

                      I'm sure one of the problems is the jbossall-client.jar we checked in as part of the ESB project, which will probably reference mq. So you should replace this library with the version you get after to install jboss-messaging. Let me know how you fare getting this to work. It shouldn't be too terribly hard :).

                      Also you need to make sure you got the ESB installed in the 'messaging' server (not default).

                      Hope that helps.

                      --Kurt

                      • 8. Re: Trailblazer deployment problem
                        Randy Beck Newbie

                        I backed out of the messaging install and went back to the default JBoss. I had also configured mysql as the datastore, but that was causing a few issues as well. I was getting persistence errors when starting the server. In addition to the instructions for using MySQL as the default datastore in the Getting Started with JBoss 4.0 Release 5 guide, I had to copy the file mysql-jdbc-service.xml from JBOSS_HOME/docs/examples/jms to my deploy directory.

                        I finally got the trailblazer to build and deploy. I was able to submit the sample form with my web browser. However, I failed to see anything happen besides the web acknowledgement page. Should I have seen some files created, or activity in the database or something?

                        Thanks for your help,
                        Randy

                        • 9. Re: Trailblazer deployment problem
                          Daniel Brum Novice

                          Hi Randy, if configured your SMTP/email settings correctly, you should have received an email with a "quote" from the 2 banks.

                          Did you see any exceptions anywhere, in any of the consoles? Check for anything in the JBoss AS logs? If you want, you can also check your database, you should have entries inside the object_snap table.

                          • 10. Re: Trailblazer deployment problem
                            Kurt Stam Master

                            Yeah hopefully you see logging coming by in the banks, listener and the appserver. Also the fileBank is easy to check up on. It will move processed files into a 'processed' subdir. Then like Daniel said, when all the responses are in an email should generated and send out to the email address you specified in the request.

                            --Kurt

                            • 11. Re: Trailblazer deployment problem
                              Kurt Stam Master

                              Hi Randy,

                              Double check your loanbrokerconfig.xml for the values:

                              loanbrokerRequestDir="/cygwin/home/kstam/dev/loanbroker_MP1/TrailBlazer-rtfiles/BankInput"
                              loanbrokerEmailTemplatePath="/cygwin/home/kstam/dev/loanbroker_MP1/template"


                              It appears these are still not dymically configured in MP1. I opened http://jira.jboss.com/jira/browse/JBESB-155 for it.

                              The first on should point to the BankInput directory on your system (check case). The second one points to where it can find the email template.

                              good luck.

                              --Kurt