3 Replies Latest reply on Mar 10, 2008 7:02 AM by Srinivasu Nidadavolu

    Why the error message NOTYETINSTALLED?

    Luiz Antonio Falaguasta Barbosa Novice

      Hi people,

      I extract JBossESB-4.2.1.GA in my computer and started it, running run.bat.

      When it starts, it shows the following:

      16:52:58,086 INFO [JBoss4ESBDeployer] create esb service, spring.esb
      16:52:58,102 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.esb:deployment=jbossesb.esb
      State: FAILED
      Reason: java.lang.RuntimeException: java.lang.IllegalStateException: ESB file
      had validation errors.
      I Depend On:
      jboss.esb:service=MessageStoreDatabaseInitializer
      jboss.esb.destination:service=Queue,name=DeadMessageQueue
      jboss.jca:service=DataSourceBinding,name=JBossESBDS
      Depends On Me:
      jboss.esb:deployment=jbpm.esb
      jboss.esb:deployment=jbrules.esb
      jboss.esb:deployment=management.esb
      jboss.esb:deployment=smooks.esb
      jboss.esb:deployment=soap.esb
      jboss.esb:deployment=spring.esb

      ObjectName: jboss.esb:deployment=jbpm.esb
      State: NOTYETINSTALLED
      I Depend On:
      jboss.esb:deployment=jbossesb.esb

      ObjectName: jboss.esb:deployment=jbrules.esb
      State: NOTYETINSTALLED
      I Depend On:
      jboss.esb:deployment=jbossesb.esb

      ObjectName: jboss.esb:deployment=management.esb
      State: NOTYETINSTALLED
      I Depend On:
      jboss.esb.console.destination:service=Queue,name=InvokerFilerQueue
      jboss.esb:deployment=jbossesb.esb
      jboss.esb.console.destination:service=Queue,name=OperationsFilerQueue
      jboss.esb.console.destination:service=Queue,name=DataFilerQueue
      jboss.jca:service=DataSourceBinding,name=ManagementDS
      jboss.jca:service=DataSourceBinding,name=juddiDB

      ObjectName: jboss.esb:deployment=smooks.esb
      State: NOTYETINSTALLED
      I Depend On:
      jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Up
      date
      jboss.esb:deployment=jbossesb.esb

      ObjectName: jboss.esb:deployment=soap.esb
      State: NOTYETINSTALLED
      I Depend On:
      jboss.esb:deployment=jbossesb.esb

      ObjectName: jboss.esb:deployment=spring.esb
      State: NOTYETINSTALLED
      I Depend On:
      jboss.esb:deployment=jbossesb.esb

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.esb:deployment=jbossesb.esb
      State: FAILED
      Reason: java.lang.RuntimeException: java.lang.IllegalStateException: ESB file
      had validation errors.
      I Depend On:
      jboss.esb:service=MessageStoreDatabaseInitializer
      jboss.esb.destination:service=Queue,name=DeadMessageQueue
      jboss.jca:service=DataSourceBinding,name=JBossESBDS
      Depends On Me:
      jboss.esb:deployment=jbpm.esb
      jboss.esb:deployment=jbrules.esb
      jboss.esb:deployment=management.esb
      jboss.esb:deployment=smooks.esb
      jboss.esb:deployment=soap.esb
      jboss.esb:deployment=spring.esb


      16:52:58,305 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-127.0.0.1-8
      080
      16:52:58,336 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-127.0.0.1-8009
      16:52:58,445 INFO [Server] JBoss (MX MicroKernel) [4.2.1.GA (build: SVNTag=JBos
      s_4_2_1_GA date=200707131605)] Started in 1m:15s:399ms
      16:53:06,226 INFO [ConnectionManager] Using JNDI to aquire a JDBC DataSource wi
      th name: java:/juddiDB
      16:53:06,242 INFO [Loader] Using the Context ClassLoader

      Please, what may I do to get run it without errors?

      Thanks on advance!

      Luiz

        • 1. Re: Why the error message NOTYETINSTALLED?
          Jiri Pechanec Apprentice

          Hi,

          this part of message is the problem

          --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
          ObjectName: jboss.esb:deployment=jbossesb.esb
          State: FAILED
          Reason: java.lang.RuntimeException: java.lang.IllegalStateException: ESB file
          had validation errors.
          

          The deploy/jbossesb.esb/META-INF/jboss-esb.xml file is not probably well-formed, maybe it was corrupted. Can you try to validate it in an XML editor or parser?

          • 2. Re: Why the error message NOTYETINSTALLED?
            Burr Sutter Master

            I suspect your "unzip" was unsuccessful. I've been through this process with well over 130 people at this stage so I know it works.

            Make sure the zip is clean, the unzip completes successfully. You are using Java 1.5 (not Java 1.6) and Ant 1.6.5 to run the quickstarts.

            When in learning/newbie mode always use the JBoss ESB Server first as everything is pre-configured and ready to go "out-of-the-box".

            Burr

            • 3. Re: Why the error message NOTYETINSTALLED?
              Srinivasu Nidadavolu Newbie

              Hi All,
              I also got the following error when I am configuring cluster on JbossESB.

              my environment is like this

              JbossAS : Jboss4.2.2.GA and config all
              JbossESB : jbossesb-4.2.1GA

              I ran the node 1 and it went well and MBeans are deployed. I started second node I got the following error.

              I understood all these Mbeans are failed because of the DestinationManager is not available on the second node.
              It's correct because the configuration of the DestinationManager is available in deploy-hasingleton folder, so its not deployed on the second node. If I am moving the jbossesb.esb to the HASingleton folder, then other esb are failing because they are depending on the jbossesb.esb.

              What to do?

              Is there any one configured JbossESB on cluster?

              Shall I need to move all esb on the HA-Singleton, then only these services are available in master node(first node)?

              Please help me out to solve the issue

              thanks
              Srini

              --- MBeans waiting for other MBeans ---
              ObjectName: jboss.esb.destination:service=Queue,name=DeadMessageQueue
              State: CONFIGURED
              I Depend On:
              jboss.mq:service=DestinationManager
              Depends On Me:
              jboss.esb:deployment=jbossesb.esb

              ObjectName: jboss.esb.destination:service=Queue,name=DataCollectorQueue
              State: CONFIGURED
              I Depend On:
              jboss.mq:service=DestinationManager

              ObjectName: jboss.esb.destination:service=Queue,name=OperationsCollectorQueue
              State: CONFIGURED
              I Depend On:
              jboss.mq:service=DestinationManager

              ObjectName: jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue
              State: CONFIGURED
              I Depend On:
              jboss.mq:service=DestinationManager

              ObjectName: jboss.esb:deployment=jbossesb.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:service=MessageStoreDatabaseInitializer
              jboss.esb.destination:service=Queue,name=DeadMessageQueue
              jboss.jca:service=DataSourceBinding,name=JBossESBDS
              Depends On Me:
              jboss.esb:deployment=jbpm.esb
              jboss.esb:deployment=jbrules.esb
              jboss.esb:deployment=smooks.esb
              jboss.esb:deployment=soap.esb
              jboss.esb:deployment=spring.esb

              ObjectName: jboss.esb:deployment=jbpm.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:deployment=jbossesb.esb

              ObjectName: jboss.esb:deployment=jbrules.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:deployment=jbossesb.esb

              ObjectName: jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Update
              State: CONFIGURED
              I Depend On:
              jboss.mq:service=DestinationManager
              Depends On Me:
              jboss.esb:service=SmooksService
              jboss.esb:deployment=smooks.esb

              ObjectName: jboss.esb:service=SmooksService
              State: CONFIGURED
              I Depend On:
              jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Update

              ObjectName: jboss.esb:deployment=smooks.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Update
              jboss.esb:deployment=jbossesb.esb

              ObjectName: jboss.esb:deployment=soap.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:deployment=jbossesb.esb

              ObjectName: jboss.esb:deployment=spring.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:deployment=jbossesb.esb

              --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
              ObjectName: jboss.mq:service=DestinationManager
              State: NOTYETINSTALLED
              Depends On Me:
              jboss.esb.destination:service=Queue,name=DeadMessageQueue
              jboss.esb.destination:service=Queue,name=DataCollectorQueue
              jboss.esb.destination:service=Queue,name=OperationsCollectorQueue
              jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue
              jboss.esb.destination:service=Topic,name=org.jboss.soa.esb.transformation.Update