2 Replies Latest reply on Mar 2, 2009 3:07 PM by Mark Weldon

    installing esb4.4 on jboss4.2.3 minimal profile

    Mark Weldon Newbie

      Hello All,
      I'm working with the following:

      JBoss AS 4.2.3.GA
      JBoss Messaging 1.4.2.GA
      JBoss ESB 4.4.GA

      on an Windows XP Pro OS.


      I started with minimal server profile and successfully added the following:
      ->Tomcat (jboss-web.deployer from the JBoss AS 4.2.3.GA default profile)
      ->JBoss Messaging 1.4.2.GA (using the ANT installer in the util directory)

      As I installed each part, I restarted the server and fixed problems as they appeared in the start-up log and added mbeans, JARs, WARs, SARs, etc. as needed. I repeat this process until no more errors show.

      Now the error I haven't been able to solve:
      I installed JBoss ESB 4.4.GA using the ANT build file in the install directory and the result was a successful build.

      I started-up JBoss AS and commenced to fix problems such as Java exceptions due to missing JARs, missing mbeans, etc. The one problem I cannot resolve is the following:

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.jca:service=DataSourceBinding,name=juddiDB
      State: NOTYETINSTALLED
      Depends On Me:
      jboss.esb:service=JuddiRMI

      Does anyone know how to resolve this particular issue?

      Thanks in advance.

        • 1. Re: installing esb4.4 on jboss4.2.3 minimal profile
          Mark Weldon Newbie

          An additional note:

          Up to and including installing JBoss Messaging 1.4.2.GA (and making the necessary adjustments), everything works perfectly ...

          I wrote a program to deploy a queue and a producer to send xml data from an eXist DB to a receiver ... and another program to destroy the queue ... works like a charm.

          Also, the JMX console (JMX Agent View) is showing in a browser.

          • 2. Re: installing esb4.4 on jboss4.2.3 minimal profile
            Mark Weldon Newbie

            To solve the particular problem above, copy/paste the org.jboss.deployment.MainDeployer-xmbean.xml file from
            jboss-4.2.3.GA\server\default\conf\xmdesc\

            to

            jboss-4.2.3.GA\server\<NEW PROFILE>\conf\xmdesc\

            However, a new list of problems will appear.

            Those can be solved by placing org.jboss.deployment.JARDeployer-xmbean.xml in the same directory mentioned above,

            AND

            placing the following JARs in the jboss-4.2.3.GA\server\<NEW PROFILE>\lib\ directory:
            antlr.jar
            bsh.jar
            commons-codec.jar
            hibernate3.jar
            quartz.jar

            I now have a server profile built from the provided minimal profile in which Tomcat, JMX, JBM1.4.2 and JBESB4.4 are installed.

            I have a couple of warnings:

            14:50:31,140 WARN [ConnectionFactoryJNDIMapper] supportsFailover attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support failover

            AND

            14:50:31,140 WARN [ConnectionFactoryJNDIMapper] supportsLoadBalancing attribute is true on connection factory: jboss.messaging.connectionfactory:service=ClusteredConnectionFactory but post office is non clustered. So connection factory will *not* support load balancing


            BUT, I can send messages from a producer that pulls data from an eXist db to a queue / ESB / queue to a receiver with no immediate problems.