7 Replies Latest reply on Jan 18, 2007 4:05 PM by Alan Feng

    JBoss 4.0.5.GA MySQL integration

    cinzia Newbie

      Hi, I've just installed jboss-4.0.5.GA, ran it once and all worked ok. I then

      1) added mysql connector mysql-connector-java-5.0.4-bin.jar to default/lib folder
      2) copied mysql-ds.xml to server/default/deploy and edited <connection-url>,<user-name>, and
      3) copied and edited mysql-jdbc2-service.xml to server/default/deploy/jms
      4) deleted hsqldb-jdbc2-service.xml from default\deploy\jms
      5) and I've also deleted hsqldb-jdbc-state-service.xml from default\deploy\jms
      6) restarted jboss.

      and I get this error:

      ===============================================================================

      JBoss Bootstrap Environment

      JBOSS_HOME: C:\Programs\jboss-4.0.5.GA\bin\\..

      JAVA: C:\Programs\Java\JDK1.5.0_04\bin\java

      JAVA_OPTS: -Dprogram.name=run.bat -server -Xms128m -Xmx512m -Dsun.rmi.dgc.cli
      ent.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000

      CLASSPATH: C:\Programs\Java\JDK1.5.0_04\lib\tools.jar;C:\Programs\jboss-4.0.5.
      GA\bin\\run.jar

      ===============================================================================

      19:44:31,217 INFO [Server] Starting JBoss (MX MicroKernel)...
      19:44:31,217 INFO [Server] Release ID: JBoss [Zion] 4.0.5.GA (build: CVSTag=Bra
      nch_4_0 date=200610162339)
      19:44:31,217 INFO [Server] Home Dir: C:\Programs\jboss-4.0.5.GA
      19:44:31,217 INFO [Server] Home URL: file:/C:/Programs/jboss-4.0.5.GA/
      19:44:31,217 INFO [Server] Patch URL: null
      19:44:31,217 INFO [Server] Server Name: default
      19:44:31,217 INFO [Server] Server Home Dir: C:\Programs\jboss-4.0.5.GA\server\d
      efault
      19:44:31,217 INFO [Server] Server Home URL: file:/C:/Programs/jboss-4.0.5.GA/se
      rver/default/
      19:44:31,233 INFO [Server] Server Log Dir: C:\Programs\jboss-4.0.5.GA\server\de
      fault\log
      19:44:31,233 INFO [Server] Server Temp Dir: C:\Programs\jboss-4.0.5.GA\server\d
      efault\tmp
      19:44:31,233 INFO [Server] Root Deployment Filename: jboss-service.xml
      19:44:31,858 INFO [ServerInfo] Java version: 1.5.0_04,Sun Microsystems Inc.
      19:44:31,858 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0_04-b05
      ,Sun Microsystems Inc.
      19:44:31,873 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
      19:44:33,076 INFO [Server] Core system initialized
      19:44:36,451 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resour
      ce:log4j.xml
      19:44:43,373 INFO [SocketServerInvoker] Invoker started for locator: InvokerLoc
      ator [socket://192.168.21.128:3873/]
      19:44:48,654 INFO [ServiceEndpointManager] WebServices: jbossws-1.0.3.SP1 (date
      =200609291417)
      19:44:50,576 INFO [SnmpAgentService] SNMP agent going active
      19:44:50,858 INFO [WebService] Using RMI server codebase: http://vp-winxppro:80
      83/
      19:44:52,139 INFO [CorbaNamingService] Naming: [IOR:000000000000002B49444C3A6F6
      D672E6F72672F436F734E616D696E672F4E616D696E67436F6E746578744578743A312E300000000
      0000200000000000000F0000102000000000F3139322E3136382E32312E31323800000DC80000000
      000114A426F73732F4E616D696E672F726F6F74000000000000050000000000000008000000004A4
      14300000000010000001C00000000000100010000000105010001000101090000000105010001000
      000210000006400000000000000010000000000000024000000220000007E0000000000000001000
      0000F3139322E3136382E32312E31323800000DC9004000000000000000000000001004010008060
      66781020101010000000000000000000000000000000000000000000000200000000400000000000
      0001F000000040000000300000001000000200000000000000002000000200000000400000000000
      0001F0000000400000003]
      19:45:07,373 INFO [CorbaTransactionService] TransactionFactory: [IOR:0000000000
      00003049444C3A6F72672F6A626F73732F746D2F69696F702F5472616E73616374696F6E46616374
      6F72794578743A312E30000000000200000000000000F0000102000000000F3139322E3136382E32
      312E31323800000DC80000000000144A426F73732F5472616E73616374696F6E732F460000000500
      00000000000008000000004A414300000000010000001C0000000000010001000000010501000100
      01010900000001050100010000002100000064000000000000000100000000000000240000002200
      00007E00000000000000010000000F3139322E3136382E32312E31323800000DC900400000000000
      00000000000010040100080606678102010101000000000000000000000000000000000000000000
      00002000000004000000000000001F00000004000000030000000100000020000000000000000200
      00002000000004000000000000001F0000000400000003]
      19:45:08,701 INFO [Embedded] Catalina naming disabled
      19:45:08,779 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in
      the classpath. Will load the default rule set.
      19:45:08,795 INFO [ClusterRuleSetFactory] Unable to find a cluster rule set in
      the classpath. Will load the default rule set.
      19:45:09,326 INFO [Http11BaseProtocol] Initializing Coyote HTTP/1.1 on http-0.0
      .0.0-8080
      19:45:09,342 INFO [Catalina] Initialization processed in 547 ms
      19:45:09,342 INFO [StandardService] Starting service jboss.web
      19:45:09,342 INFO [StandardEngine] Starting Servlet Engine: Apache Tomcat/5.5.2
      0
      19:45:09,389 INFO [StandardHost] XML validation disabled
      19:45:09,592 INFO [Catalina] Server startup in 250 ms
      19:45:09,920 INFO [TomcatDeployer] deploy, ctxPath=/invoker, warUrl=.../deploy/
      http-invoker.sar/invoker.war/
      19:45:10,373 INFO [WebappLoader] Dual registration of jndi stream handler: fact
      ory already defined
      19:45:10,936 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jbosswe
      b-tomcat55.sar/ROOT.war/
      19:45:11,529 INFO [TomcatDeployer] deploy, ctxPath=/jbossws, warUrl=.../tmp/dep
      loy/tmp45420jbossws-context-exp.war/
      19:45:12,311 INFO [TomcatDeployer] deploy, ctxPath=/jbossmq-httpil, warUrl=.../
      deploy/jms/jbossmq-httpil.sar/jbossmq-httpil.war/
      19:45:12,779 INFO [TomcatDeployer] deploy, ctxPath=/web-console, warUrl=.../dep
      loy/management/console-mgr.sar/web-console.war/
      19:45:13,467 INFO [[/web-console]] MonitorsFolder: Failed to init plugin, null
      19:45:13,498 INFO [[/web-console]] UCLs: Failed to init plugin, null
      19:45:13,514 INFO [[/web-console]] JMS Message: Failed to init plugin, null
      19:45:13,529 INFO [[/web-console]] JSR77 WebModule: Failed to init plugin, null

      19:45:13,529 INFO [[/web-console]] J2EEFolder: Failed to init plugin, null
      19:45:13,545 INFO [[/web-console]] AOPFolder: Failed to init plugin, null
      19:45:13,545 INFO [[/web-console]] SystemFolder: Failed to init plugin, null
      19:45:13,561 INFO [[/web-console]] MBeans: Failed to init plugin, null
      19:45:13,576 INFO [[/web-console]] JSR77 Domains and Servers: Failed to init pl
      ugin, null
      19:45:13,576 INFO [[/web-console]] JSR77 EJBModules and EJBs: Failed to init pl
      ugin, null
      19:45:13,592 INFO [[/web-console]] JSR77 J2EE Apps: Failed to init plugin, null

      19:45:17,639 INFO [MailService] Mail Service bound to java:/Mail
      19:45:18,061 INFO [RARDeployment] Required license terms exist, view META-INF/r
      a.xml in .../deploy/jboss-ha-local-jdbc.rar
      19:45:18,201 INFO [RARDeployment] Required license terms exist, view META-INF/r
      a.xml in .../deploy/jboss-ha-xa-jdbc.rar
      19:45:18,264 INFO [RARDeployment] Required license terms exist, view META-INF/r
      a.xml in .../deploy/jboss-local-jdbc.rar
      19:45:18,373 INFO [RARDeployment] Required license terms exist, view META-INF/r
      a.xml in .../deploy/jboss-xa-jdbc.rar
      19:45:18,545 INFO [RARDeployment] Required license terms exist, view META-INF/r
      a.xml in .../deploy/jms/jms-ra.rar
      19:45:18,608 INFO [RARDeployment] Required license terms exist, view META-INF/r
      a.xml in .../deploy/mail-ra.rar
      19:45:18,654 INFO [RARDeployment] Required license terms exist, view META-INF/r
      a.xml in .../deploy/quartz-ra.rar
      19:45:18,686 INFO [QuartzResourceAdapter] start quartz!!!
      19:45:18,764 INFO [SimpleThreadPool] Job execution threads will use class loade
      r of thread: main
      19:45:18,795 INFO [QuartzScheduler] Quartz Scheduler v.1.5.2 created.
      19:45:18,795 INFO [RAMJobStore] RAMJobStore initialized.
      19:45:18,795 INFO [StdSchedulerFactory] Quartz scheduler 'DefaultQuartzSchedule
      r' initialized from default resource file in Quartz package: 'quartz.properties'

      19:45:18,811 INFO [StdSchedulerFactory] Quartz scheduler version: 1.5.2
      19:45:18,811 INFO [QuartzScheduler] Scheduler DefaultQuartzScheduler_$_NON_CLUS
      TERED started.
      19:45:20,811 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca
      :service=DataSourceBinding,name=DefaultDS' to JNDI name 'java:DefaultDS'
      19:45:21,186 INFO [ConnectionFactoryBindingService] Bound ConnectionManager 'jb
      oss.jca:service=ConnectionFactoryBinding,name=JmsXA' to JNDI name 'java:JmsXA'
      19:45:22,186 INFO [WrapperDataSourceService] Bound ConnectionManager 'jboss.jca
      :service=DataSourceBinding,name=MySqlDS' to JNDI name 'java:MySqlDS'
      19:45:23,123 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../dep
      loy/jmx-console.war/
      19:45:23,483 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

      --- MBeans waiting for other MBeans ---
      ObjectName: jboss.mq:service=InvocationLayer,type=HTTP
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=Invoker
      jboss.web:service=WebServer

      ObjectName: jboss.mq.destination:service=Topic,name=testTopic
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      ObjectName: jboss.mq.destination:service=Topic,name=securedTopic
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

      ObjectName: jboss.mq.destination:service=Topic,name=testDurableTopic
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=DestinationManager
      jboss.mq:service=SecurityManager

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

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

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

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

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

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

      ObjectName: jboss.mq:service=Invoker
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=TracingInterceptor
      jboss:service=Naming
      Depends On Me:
      jboss.mq:service=InvocationLayer,type=HTTP
      jboss.mq:service=InvocationLayer,type=JVM
      jboss.mq:service=InvocationLayer,type=UIL2

      ObjectName: jboss.mq:service=TracingInterceptor
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=SecurityManager
      Depends On Me:
      jboss.mq:service=Invoker

      ObjectName: jboss.mq:service=SecurityManager
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=DestinationManager
      Depends On Me:
      jboss.mq.destination:service=Topic,name=testTopic
      jboss.mq.destination:service=Topic,name=securedTopic
      jboss.mq.destination:service=Topic,name=testDurableTopic
      jboss.mq.destination:service=Queue,name=testQueue
      jboss.mq:service=TracingInterceptor
      jboss.mq.destination:service=Queue,name=DLQ

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

      ObjectName: jboss.mq:service=InvocationLayer,type=JVM
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=Invoker

      ObjectName: jboss.mq:service=DestinationManager
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=MessageCache
      jboss.mq:service=PersistenceManager
      jboss.mq:service=StateManager
      Depends On Me:
      jboss.mq.destination:service=Topic,name=testTopic
      jboss.mq.destination:service=Topic,name=securedTopic
      jboss.mq.destination:service=Topic,name=testDurableTopic
      jboss.mq.destination:service=Queue,name=testQueue
      jboss.mq.destination:service=Queue,name=A
      jboss.mq.destination:service=Queue,name=B
      jboss.mq.destination:service=Queue,name=C
      jboss.mq.destination:service=Queue,name=D
      jboss.mq.destination:service=Queue,name=ex
      jboss.mq:service=SecurityManager
      jboss.mq.destination:service=Queue,name=DLQ

      ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
      State: CONFIGURED
      I Depend On:
      jboss.mq:service=Invoker

      --- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
      ObjectName: jboss.mq:service=StateManager
      State: NOTYETINSTALLED
      Depends On Me:
      jboss.mq:service=DestinationManager



      I guess I need to set/define this ObjectName: jboss.mq:service=StateManager somewhere, does anyone know how?

      thanks
      cinzia

        • 1. Re: JBoss 4.0.5.GA MySQL integration
          cinzia Newbie

          by the way, I've used ejb3 installation.

          • 2. Re: JBoss 4.0.5.GA MySQL integration
            Marco Novice

            hello,
            btw, why have you done those 2 steps?

            4) deleted hsqldb-jdbc2-service.xml from default\deploy\jms
            5) and I've also deleted hsqldb-jdbc-state-service.xml from default\deploy\jms


            mayb those deletions are the source of your problems..
            what r you trying to accomplish?
            why would you need to delete hsqldb?

            hth
            marco

            • 3. Re: JBoss 4.0.5.GA MySQL integration
              cinzia Newbie

              solved: I've wrongly removed the file which contained the definition of jboss.mq:service=StateManager, i.e. step
              5) and I've also deleted hsqldb-jdbc-state-service.xml from default\deploy\jms

              • 4. Re: JBoss 4.0.5.GA MySQL integration
                cinzia Newbie

                 

                "MmarcoM" wrote:
                why have you done those 2 steps?

                4) deleted hsqldb-jdbc2-service.xml from default\deploy\jms
                5) and I've also deleted hsqldb-jdbc-state-service.xml from default\deploy\jms



                well step 4 is outlined in http://wiki.jboss.org/wiki/Wiki.jsp?page=SetUpAMysqlDatasource under JBossMQ header, and I've assumed I should do 5) as well as it seemed related to hsdb.

                thanks
                cinzia

                • 5. Re: JBoss 4.0.5.GA MySQL integration
                  Marco Novice

                  Hi,
                  i see...
                  ok if you want just a MYSQL datasource foryour own purposes, it's enough to do step 1/2/3, configure mysql-ds.xml and proper authentication in login-config.
                  All jboss MQ that comes with default dist i gues it is using hsql as database, so if you would have gone to do steps 5/6 that mean to me that you want tocompletely replace hsql with mysql, having mysql db handling everything,
                  at least, that's what looks to me by checking the link you provide

                  i have been using mysql with jboss for over 3 years, and all i needed todo was to configure properly a mysql-ds.xml

                  that's what it seems to me you want to do

                  hth
                  marco

                  • 6. Re: JBoss 4.0.5.GA MySQL integration
                    cinzia Newbie

                    thanks a lot marco for clarifying :)

                    • 7. Re: JBoss 4.0.5.GA MySQL integration
                      Alan Feng Novice

                       

                      "MmarcoM" wrote:
                      Hi,
                      i see...
                      ok if you want just a MYSQL datasource foryour own purposes, it's enough to do step 1/2/3, configure mysql-ds.xml and proper authentication in login-config.
                      All jboss MQ that comes with default dist i gues it is using hsql as database, so if you would have gone to do steps 5/6 that mean to me that you want tocompletely replace hsql with mysql, having mysql db handling everything,
                      at least, that's what looks to me by checking the link you provide

                      i have been using mysql with jboss for over 3 years, and all i needed todo was to configure properly a mysql-ds.xml

                      that's what it seems to me you want to do

                      hth
                      marco


                      I was having the same issue because I removed the same hsqldb-jdbc-state-service.xml file when I switch to MySQL. Restore that file solved the problem.

                      I don't agree, though, that you only need step 1/2/3. Step 4 is necessary as it contains SQL statement only meant to be used with HS DB. And I got exceptions if I keep that file there.

                      Also note that the sample mysql-jdbc2-service.xml depends on "MysqlDS", which should be changed to "DefaultDS" to make it work.

                      I think in this case the SQL statements in the hsqldb-jdbc-state-service.xml happen to work with MySQL DB as well, that's why we kept that file. Had it contains HS DB specific statements, we won't be able to use it directly then.