3 Replies Latest reply on Feb 19, 2009 8:43 AM by bate

    JBossESB+Oracle+JBMessaging successfuly deployed?

    bate Newbie

      hi
      has any body successfuly deployed JBossESB4.4.GA with JBoss messaging 1.4.2.GA using Oracle DB instead of hypersonic database?

      Thank you for your help

        • 1. Re: JBossESB+Oracle+JBMessaging successfuly deployed?
          Ryan Hochstetler Newbie

          I've successfully deployed JBoss 4.2.3 + JBossESB + Oracle 11g+ JBMQ. JBossMessaging undoubtedly works with Oracle, which leads me to believe that such a configuration is possible. You must change the references to the DDL files for JUDDI from Hypersonic to Oracle. You'll still want to modify the Oracle DDL to add tablespaces and constraint/index names. Also you must strip out the HSQL MBeans and configure proper datasources, but this is easy.

          JBossMessaging is in our plan. We're just waiting for a known issue to disappear in a service pack release.

          • 2. Re: JBossESB+Oracle+JBMessaging successfuly deployed?
            bate Newbie

            thank you Ryanhos for your reply.
            can you tell me the changes i need to do to run
            JBoss 4.2.3 + JBossESB + Oracle 11g+ JBMQ.
            i will need JBossMessaging because i wan to cluster the ESB.
            But in the mean time jbossMQ will do but i definitively need oracle, so i am glad to hear that it works.
            Thank you

            • 3. Re: JBossESB+Oracle+JBMessaging successfuly deployed?
              bate Newbie

              i managed to get JBossESB 4.5 + JBM+Oracle to get deployed but i get the following Exception
              Your Help is very much appreciated



              14:01:21,811 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

              --- MBeans waiting for other MBeans ---
              ObjectName: jboss.esb:deployment=Quickstart_helloworld.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:deployment=jbossesb.esb
              jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_esb
              jboss.esb.quickstart.destination:service=Queue,name=quickstart_helloworld_Request_gw

              ObjectName: jboss.esb:deployment=Quickstart_publish_as_webservice.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb.quickstart.destination:service=Queue,name=quickstart_publish_as_webservice_Request_esb
              jboss.esb:deployment=jbossesb.esb
              jboss.esb:deployment=soap.esb
              jboss.esb.quickstart.destination:service=Queue,name=quickstart_publish_as_webservice_Request_esb_reply

              ObjectName: jboss.esb:deployment=jbossesb.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:service=MessageStoreDatabaseInitializer
              jboss.esb.destination:service=Queue,name=OperationsCollectorQueue
              jboss.esb.destination:service=Queue,name=DataCollectorQueue
              jboss.esb.destination:service=Queue,name=DeadMessageQueue
              jboss.jca:service=DataSourceBinding,name=JBossESBDS
              jboss.esb.destination:service=Queue,name=OperationsResultCollectorQueue
              Depends On Me:
              jboss.esb:deployment=Quickstart_helloworld.esb
              jboss.esb:deployment=Quickstart_publish_as_webservice.esb
              jboss.esb:deployment=jbrules.esb
              jboss.esb:deployment=management.esb
              jboss.esb:deployment=slsb.esb
              jboss.esb:deployment=smooks.esb
              jboss.esb:deployment=soap.esb
              jboss.esb:deployment=spring.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.console.destination:service=Queue,name=OperationsFilerQueue
              jboss.esb:deployment=jbossesb.esb
              jboss.jca:service=DataSourceBinding,name=juddiDB
              jboss.jca:service=DataSourceBinding,name=ManagementDS
              jboss.esb.console.destination:service=Queue,name=DataFilerQueue

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

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

              ObjectName: jboss.esb:deployment=soap.esb
              State: NOTYETINSTALLED
              I Depend On:
              jboss.esb:deployment=jbossesb.esb
              Depends On Me:
              jboss.esb:deployment=Quickstart_publish_as_webservice.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.destination:service=Queue,name=OperationsCollectorQueue
              State: NOTYETINSTALLED
              Depends On Me:
              jboss.esb:deployment=jbossesb.esb

              ObjectName: jboss.esb.console.destination:service=Queue,name=InvokerFilerQueue
              State: NOTYETINSTALLED
              Depends On Me:
              jboss.esb:deployment=management.esb


              14:01:21,966 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-vmjboss10i01.bfi.admin.ch%2F10.135.27.159-8080
              14:01:22,019 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-8443
              14:01:22,070 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-vmjboss10i01.bfi.admin.ch%2F10.135.27.159-8009
              14:01:22,122 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 1m:4s:730ms
              14:01:29,854 INFO [ConnectionManager] Using JNDI to aquire a JDBC DataSource with name: java:/juddiDB
              14:01:29,950 INFO [RegistryEngine] Initializing jUDDI database from listed sql files
              14:01:32,644 INFO [Loader] Using the Context ClassLoader

              14:01:32,920 ERROR [DataFilerJob]
              org.jboss.soa.esb.services.registry.ServiceNotFoundException: Could not find service with category=JBossESB-Internal and serviceName=DataCollectorService
              at org.jboss.internal.soa.esb.services.registry.JAXRRegistryImpl.findEPRs(JAXRRegistryImpl.java:275)
              at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
              at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
              at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
              at java.lang.reflect.Method.invoke(Method.java:597)
              at org.jboss.internal.soa.esb.services.registry.RegistryService$1.invoke(RegistryService.java:61)
              at $Proxy36.findEPRs(Unknown Source)
              at org.jboss.internal.soa.esb.services.registry.InVMRegistryInterceptor.findEPRs(InVMRegistryInterceptor.java:160)
              at org.jboss.soa.esb.services.registry.RegistryFactory$HeadRegistryInterceptor.findEPRs(RegistryFactory.java:229)
              at org.jboss.soa.esb.listeners.RegistryUtil.getEprs(RegistryUtil.java:226)
              at org.jboss.soa.esb.monitoring.server.DataFilerJob.execute(DataFilerJob.java:70)
              at org.quartz.core.JobRunShell.run(JobRunShell.java:203)
              at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)