6 Replies Latest reply on Dec 17, 2004 5:50 AM by . .

    Problem with JBossMQ+MySQL standalone, no problem with Defau

    . . Newbie

      Hello,

      I'm currently running out of ideas of why JBossMQ (JBoss 4.0.0) standalone isn't workinng with MySQL.
      Besides, with server/default config of JBoss 4.0.0+MySQL, no problem at all !!!

      I explain what I've done:
      Configured JBoss to use MySQL instead of hsqldb using FAQ

      - Added MySQL driver to /server/default/lib
      - Added /docs/examples/jca/mysql-ds.xml to /server/default/deploy
      - Modified DefaultDS to MySqlDS in STANDARDJAWS.XML
      - Modified <type-mapping/> to mySql in STANDARDJAWS.XML
      - Modified DefaultDS to MySqlDS in STANDARDJBOSSCMP-JDBC.XML
      - Modified DefaultDS to MySqlDS in LOGIN-CONFIG.XML
      - Added mysql-jdbc2-service.xml to /server/default/deploy/jms
      - Deleted hsqldb-jdbc2-service.xml
      - Added /docs/examples/jms/mysql-jdbc2-service.xml to /server/default/deploy/jms
      - Modified hsqldb-jdbc2-state-service.xml to use MySqlDS
      (- Renamed hsqldb-jdbc2-state-service.xml to mysqldb-jdbc2-state-service.xml -> No harm, isn't it ? )

      I do a ./run.sh -> everything runs like a charm ...

      I do a ant in /docs/examples/jms/standalone directory
      -> jbossmq directory created in /server -> OK

      Check configuration files to see if all is configured to use MySqlDS -> OK

      I do a ./run.sh -c jbossmq

      and I have this :

      =========================================================================
      
       JBoss Bootstrap Environment
      
       JBOSS_HOME: /usr/local/jboss-4.0.0
      
       JAVA: /usr/java/jdk1.5.0/bin/java
      
       JAVA_OPTS: -server -Xms128m -Xmx128m -Dprogram.name=run.sh
      
       CLASSPATH: /usr/local/jboss-4.0.0/bin/run.jar:/usr/java/jdk1.5.0/lib/tools.jar
      
      =========================================================================
      
      18:31:35,672 INFO [Server] Starting JBoss (MX MicroKernel)...
      18:31:35,674 INFO [Server] Release ID: JBoss [Zion] 4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)
      18:31:35,675 INFO [Server] Home Dir: /usr/local/jboss-4.0.0
      18:31:35,675 INFO [Server] Home URL: file:/usr/local/jboss-4.0.0/
      18:31:35,676 INFO [Server] Library URL: file:/usr/local/jboss-4.0.0/lib/
      18:31:35,678 INFO [Server] Patch URL: null
      18:31:35,678 INFO [Server] Server Name: jbossmq
      18:31:35,679 INFO [Server] Server Home Dir: /usr/local/jboss-4.0.0/server/jbossmq
      18:31:35,679 INFO [Server] Server Home URL: file:/usr/local/jboss-4.0.0/server/jbossmq/
      18:31:35,680 INFO [Server] Server Data Dir: /usr/local/jboss-4.0.0/server/jbossmq/data
      18:31:35,680 INFO [Server] Server Temp Dir: /usr/local/jboss-4.0.0/server/jbossmq/tmp
      18:31:35,681 INFO [Server] Server Config URL: file:/usr/local/jboss-4.0.0/server/jbossmq/conf/
      18:31:35,681 INFO [Server] Server Library URL: file:/usr/local/jboss-4.0.0/server/jbossmq/lib/
      18:31:35,682 INFO [Server] Root Deployment Filename: jboss-service.xml
      18:31:35,687 INFO [Server] Starting General Purpose Architecture (GPA)...
      18:31:36,178 INFO [ServerInfo] Java version: 1.5.0,Sun Microsystems Inc.
      18:31:36,178 INFO [ServerInfo] Java VM: Java HotSpot(TM) Server VM 1.5.0-b64,Sun Microsystems Inc.
      18:31:36,178 INFO [ServerInfo] OS-System: Linux 2.6.9-1.667smp,i386
      18:31:37,059 INFO [Server] Core system initialized
      18:31:38,681 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      18:31:39,184 INFO [NamingService] Started jnpPort=1099, rmiPort=0, backlog=50, bindAddress=null, Client SocketFactory=null, Server SocketFactory=org.jboss.net.sockets.DefaultSocketFactory@ad093076
      18:31:40,956 ERROR [URLDeploymentScanner] Incomplete Deployment listing:Packages waiting for a deployer:
      org.jboss.deployment.DeploymentInfo@a95c6f66 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/jboss-local-jdbc.rar }
       deployer: null
       status: null
       state: INIT_WAITING_DEPLOYER
       watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/jboss-local-jdbc.rar
       altDD: null
       lastDeployed: 1103131899475
       lastModified: 1103131899000
       mbeans:
      
      org.jboss.deployment.DeploymentInfo@1ae9d639 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/hsqldb-ds.xml }
       deployer: null
       status: null
       state: INIT_WAITING_DEPLOYER
       watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/hsqldb-ds.xml
       altDD: null
       lastDeployed: 1103131899484
       lastModified: 1103131899000
       mbeans:
      
      org.jboss.deployment.DeploymentInfo@a91bffa1 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/mysql-ds.xml }
       deployer: null
       status: null
       state: INIT_WAITING_DEPLOYER
       watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/mysql-ds.xml
       altDD: null
       lastDeployed: 1103131899488
       lastModified: 1103131899000
       mbeans:
      
      Incompletely deployed packages:
      org.jboss.deployment.DeploymentInfo@a95c6f66 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/jboss-local-jdbc.rar }
       deployer: null
       status: null
       state: INIT_WAITING_DEPLOYER
       watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/jboss-local-jdbc.rar
       altDD: null
       lastDeployed: 1103131899475
       lastModified: 1103131899000
       mbeans:
      
      org.jboss.deployment.DeploymentInfo@1ae9d639 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/hsqldb-ds.xml }
       deployer: null
       status: null
       state: INIT_WAITING_DEPLOYER
       watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/hsqldb-ds.xml
       altDD: null
       lastDeployed: 1103131899484
       lastModified: 1103131899000
       mbeans:
      
      org.jboss.deployment.DeploymentInfo@a91bffa1 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/mysql-ds.xml }
       deployer: null
       status: null
       state: INIT_WAITING_DEPLOYER
       watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/mysql-ds.xml
       altDD: null
       lastDeployed: 1103131899488
       lastModified: 1103131899000
       mbeans:
      
      MBeans waiting for other MBeans:
      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=Queue,name=ToValidate
       jboss.mq.destination:service=Queue,name=ToCheck
       jboss.mq.destination:service=Queue,name=ToNotify
       jboss.mq.destination:service=Queue,name=ToProcess
       jboss.mq.destination:service=Topic,name=SynchronousResponse
       jboss.mq.destination:service=Queue,name=ToLog
       jboss.mq:service=SecurityManager
       jboss.mq.destination:service=Queue,name=DLQ
      
      ObjectName: jboss.mq:service=PersistenceManager
       state: CONFIGURED
       I Depend On: jboss.jca:service=DataSourceBinding,name=MySqlDS
      
       Depends On Me: jboss.mq:service=DestinationManager
      
      ObjectName: jboss.mq:service=InvocationLayer,type=UIL2
       state: CONFIGURED
       I Depend On: jboss.mq:service=Invoker
      
       Depends On Me:
      ObjectName: jboss.mq.destination:service=Queue,name=ToValidate
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
       Depends On Me:
      ObjectName: jboss.mq.destination:service=Queue,name=ToCheck
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
       Depends On Me:
      ObjectName: jboss.mq.destination:service=Queue,name=ToNotify
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
       Depends On Me:
      ObjectName: jboss.mq.destination:service=Queue,name=ToProcess
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
       Depends On Me:
      ObjectName: jboss.mq.destination:service=Topic,name=SynchronousResponse
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
       Depends On Me:
      ObjectName: jboss.mq.destination:service=Queue,name=ToLog
       state: CONFIGURED
       I Depend On: jboss.mq:service=DestinationManager
       jboss.mq:service=SecurityManager
      
       Depends On Me:
      ObjectName: jboss.mq:service=Invoker
       state: CONFIGURED
       I Depend On: jboss.mq:service=TracingInterceptor
      
       Depends On Me: 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=Queue,name=ToValidate
       jboss.mq.destination:service=Queue,name=ToCheck
       jboss.mq.destination:service=Queue,name=ToNotify
       jboss.mq.destination:service=Queue,name=ToProcess
       jboss.mq.destination:service=Topic,name=SynchronousResponse
       jboss.mq.destination:service=Queue,name=ToLog
       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
      
       Depends On Me:
      ObjectName: jboss.mq:service=StateManager
       state: CONFIGURED
       I Depend On: jboss.jca:service=DataSourceBinding,name=MySqlDS
      
       Depends On Me: jboss.mq:service=DestinationManager
      
      
      MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM:
       ObjectName: jboss.jca:service=DataSourceBinding,name=MySqlDS
       state: NOTYETINSTALLED
       I Depend On:
       Depends On Me: jboss.mq:service=PersistenceManager
       jboss.mq:service=StateManager
      
      
      18:31:41,177 INFO [Server] JBoss (MX MicroKernel) [4.0.0 (build: CVSTag=JBoss_4_0_0 date=200409200418)] Started in 5s:490ms


      I'm afraid I don't understand what's going on ... MySqlDS should be INSTALLED, cause it is installed if I run the Default config ...

      If someone out there has the solution ... well ... I'd like to share it with you, LOL

      Thanks

      Have a nice day !!!

        • 1. Re: Problem with JBossMQ+MySQL standalone, no problem with D
          Jing Yang Newbie

          I got almost same problem EVEN at default sever setting !


          -Jing

          • 2. Re: Problem with JBossMQ+MySQL standalone, no problem with D
            Adrian Brock Master

             


            org.jboss.deployment.DeploymentInfo@a91bffa1 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy
            /mysql-ds.xml }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/mysql-ds.xml
            altDD: null
            lastDeployed: 1103131899488
            lastModified: 1103131899000
            mbeans:

            Incompletely deployed packages:
            org.jboss.deployment.DeploymentInfo@a95c6f66 { url=file:/usr/local/jboss-4.0.0/server/jbossmq/deploy
            /jboss-local-jdbc.rar }
            deployer: null
            status: null
            state: INIT_WAITING_DEPLOYER
            watch: file:/usr/local/jboss-4.0.0/server/jbossmq/deploy/jboss-local-jdbc.rar
            altDD: null
            lastDeployed: 1103131899475
            lastModified: 1103131899000
            mbeans:


            Looks pretty obvious to me.

            You have neither the rar deployer or the connection factory deployer (for -ds.xml files)
            deployed.

            Which probably means you don't have jbossjca-service.xml in the deploy directory.

            jing58 stop posting "ME TOO" nobody is impressed with your redundant post.

            • 3. Re: Problem with JBossMQ+MySQL standalone, no problem with D
              . . Newbie

              First of all, thanks for your answer adrian

              Sorry to bother again, I'm new to JBoss as you could have guessed ;-)

              My first thought was that my jbossmq config didn't deployed all the necessary packages, but i didn't want to mess with the files "by hand" cause there is a ant script that does it all for me.
              I thought that this ant will build me a "workable" jbossmq IF my default conf was ALREADY "workable".

              My guess is now the ant build.xml is looking for files that do not exist
              - lib/jboss-jaas.jar
              - transaction-service.xml
              - deploy/jboss-jca.sar

              Am I wrong/right ?

              Actually, all the files that exist, are copied to the jbossmq conf and still, I must agree with you, something is missing.

              I'm gonna do the "by hand method", but adding only the jbossjca-service.xml doesn't solve my problem ... now a rar is missing cause jboss can't find a class ... I'm gonna try working this out ... :S LOL

              I give you the result of my ant (files in directories), this way you can tell me what's missing, more easily, if you wish.

              /usr/local/jboss-4.0.0/server/jbossmq
              ????conf
              ? ? login-config.xml
              ? ? log4j.xml
              ? ? jboss-service.xml
              ? ? jndi.properties
              ? ? jbossmq-state.xml
              ? ?
              ? ????xmdesc
              ? ClientUserTransaction-xmbean.xml
              ? TransactionManagerService-xmbean.xml
              ? JNDIView-xmbean.xml
              ? org.jboss.deployment.MainDeployer-xmbean.xml
              ? AttributePersistenceService-xmbean.xml
              ?
              ????log
              ? boot.log
              ? server.log
              ?
              ????lib
              ? jboss-j2ee.jar
              ? log4j.jar
              ? jboss-common-jdbc-wrapper.jar
              ? hsqldb.jar
              ? jbosssx.jar
              ? jboss-management.jar
              ? jboss.jar
              ? mysql-connector-java-3.0.16-ga-bin.jar
              ? jnpserver.jar
              ? jbossmq.jar
              ? hsqldb-plugin.jar
              ? jboss-transaction.jar
              ?
              ????tmp
              ????deploy
              ? jboss-local-jdbc.rar
              ? hsqldb-ds.xml
              ? mysql-ds.xml
              ?
              ????jms
              mysql-jdbc2-service.xml
              uil2-service.xml
              jbossmq-destinations-service.xml
              jbossmq-service.xml
              mysqldb-jdbc-state-service.xml

              Again, I'm sorry if this is obvious, you can move this to newbie section if it fits better there :-P ... I've never tried to modify JBoss config until yesterday. So, yes, I think you can describe me as a newbie in this.

              Have a nice day ;-)

              • 4. Re: Problem with JBossMQ+MySQL standalone, no problem with D
                . . Newbie

                Sorry, can't edit ... preview seemed fine ... I try with All HTPL/BBCode, OFF

                /usr/local/jboss-4.0.0/server/jbossmq
                +---conf
                | | login-config.xml
                | | log4j.xml
                | | jboss-service.xml
                | | jndi.properties
                | | jbossmq-state.xml
                | |
                | +---xmdesc
                | ClientUserTransaction-xmbean.xml
                | TransactionManagerService-xmbean.xml
                | JNDIView-xmbean.xml
                | org.jboss.deployment.MainDeployer-xmbean.xml
                | AttributePersistenceService-xmbean.xml
                |
                +---log
                | boot.log
                | server.log
                |
                +---lib
                | jboss-j2ee.jar
                | log4j.jar
                | jboss-common-jdbc-wrapper.jar
                | hsqldb.jar
                | jbosssx.jar
                | jboss-management.jar
                | jboss.jar
                | mysql-connector-java-3.0.16-ga-bin.jar
                | jnpserver.jar
                | jbossmq.jar
                | hsqldb-plugin.jar
                | jboss-transaction.jar
                |
                +---tmp
                +---deploy
                | jboss-local-jdbc.rar
                | jbossjca-service.xml
                | hsqldb-ds.xml
                | mysql-ds.xml
                |
                +---jms
                mysql-jdbc2-service.xml
                uil2-service.xml
                jbossmq-destinations-service.xml
                jbossmq-service.xml
                mysqldb-jdbc-state-service.xml

                • 5. Re: Problem with JBossMQ+MySQL standalone, no problem with D
                  Adrian Brock Master

                  I see, you are using docs/examples/jms/standalone

                  It hasn't been updated for jboss4. This works for with the current JBoss4 codebase - JBoss-4.0.1RC3

                  jboss-service.xml

                  <?xml version="1.0" encoding="UTF-8"?>
                  
                  <!-- $Id: jboss-service.xml,v 1.2 2004/03/06 19:42:45 ejort Exp $ -->
                  
                  <!-- ===================================================================== -->
                  <!-- -->
                  <!-- A minimal JBoss Server Configuration -->
                  <!-- -->
                  <!-- ===================================================================== -->
                  
                  <server>
                  
                   <!-- Load all jars from the JBOSS_DIST/server/<config>/lib directory. This
                   can be restricted to specific jars by specifying them in the archives
                   attribute.
                   -->
                   <classpath codebase="lib" archives="*"/>
                  
                   <!-- ==================================================================== -->
                   <!-- Log4j Initialization -->
                   <!-- ==================================================================== -->
                   <mbean code="org.jboss.logging.Log4jService"
                   name="jboss.system:type=Log4jService,service=Logging">
                   <attribute name="ConfigurationURL">resource:log4j.xml</attribute>
                   </mbean>
                  
                   <!-- ==================================================================== -->
                   <!-- JNDI -->
                   <!-- ==================================================================== -->
                  
                   <mbean code="org.jboss.naming.NamingService"
                   name="jboss:service=Naming">
                   <!-- The listening port for the bootstrap JNP service. Set this to -1
                   to run the NamingService without the JNP invoker listening port.
                   -->
                   <attribute name="Port">1099</attribute>
                   </mbean>
                  
                   <!-- ==================================================================== -->
                   <!-- Security -->
                   <!-- ==================================================================== -->
                  
                   <mbean code="org.jboss.security.plugins.SecurityConfig"
                   name="jboss.security:service=SecurityConfig">
                   <attribute name="LoginConfig">jboss.security:service=XMLLoginConfig</attribute>
                   </mbean>
                   <mbean code="org.jboss.security.auth.login.XMLLoginConfig"
                   name="jboss.security:service=XMLLoginConfig">
                   <attribute name="ConfigResource">login-config.xml</attribute>
                   </mbean>
                  
                   <!-- JAAS security manager and realm mapping -->
                   <mbean code="org.jboss.security.plugins.JaasSecurityManagerService"
                   name="jboss.security:service=JaasSecurityManager">
                   <attribute name="SecurityManagerClassName">
                   org.jboss.security.plugins.JaasSecurityManager
                   </attribute>
                   </mbean>
                  
                   <!-- ==================================================================== -->
                   <!-- Transactions -->
                   <!-- ==================================================================== -->
                   <!-- The configurable Xid factory. For use with Oracle, set pad to true -->
                   <mbean code="org.jboss.tm.XidFactory"
                   name="jboss:service=XidFactory">
                   <!--attribute name="Pad">true</attribute-->
                   </mbean>
                  
                   <!--
                   | The fast in-memory transaction manager.
                   -->
                   <mbean code="org.jboss.tm.TransactionManagerService"
                   name="jboss:service=TransactionManager"
                   xmbean-dd="resource:xmdesc/TransactionManagerService-xmbean.xml">
                   <attribute name="TransactionTimeout">300</attribute>
                  
                   <depends optional-attribute-name="XidFactory">jboss:service=XidFactory</depends>
                   </mbean>
                  
                   <!-- ==================================================================== -->
                   <!-- Invokers to the JMX node -->
                   <!-- ==================================================================== -->
                  
                   <!-- RMI/JRMP invoker -->
                   <mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker"
                   name="jboss:service=invoker,type=jrmp">
                   <attribute name="RMIObjectPort">4444</attribute>
                   <attribute name="ServerAddress">${jboss.bind.address}</attribute>
                   <!--
                   <attribute name="RMIClientSocketFactory">custom</attribute>
                   <attribute name="RMIServerSocketFactory">custom</attribute>
                   <attribute name="RMIServerSocketAddr">custom</attribute>
                   <attribute name="SecurityDomain">ssl-domain-name</attribute>
                   -->
                   <depends>jboss:service=TransactionManager</depends>
                   </mbean>
                  
                   <mbean code="org.jboss.invocation.local.LocalInvoker"
                   name="jboss:service=invoker,type=local">
                  
                   <depends>jboss:service=TransactionManager</depends>
                   </mbean>
                  
                   <!-- ==================================================================== -->
                   <!-- An MBean that is a registry for JDBC type-mapping metadata -->
                   <!-- ==================================================================== -->
                  
                   <mbean code="org.jboss.ejb.plugins.cmp.jdbc.metadata.MetaDataLibrary"
                   name="jboss.jdbc:service=metadata"/>
                  
                   <!-- ==================================================================== -->
                   <!-- Deployment Scanning -->
                   <!-- ==================================================================== -->
                  
                   <!-- An mbean for hot deployment/undeployment of archives.
                   -->
                   <mbean code="org.jboss.deployment.scanner.URLDeploymentScanner"
                   name="jboss.deployment:type=DeploymentScanner,flavor=URL">
                  
                   <depends optional-attribute-name="Deployer">jboss.system:service=MainDeployer</depends>
                  
                   <!-- The URLComparator can be used to specify a deployment ordering
                   for deployments found in a scanned directory. The class specified
                   must be an implementation of java.util.Comparator, it must be able
                   to compare two URL objects, and it must have a no-arg constructor.
                   Two deployment comparators are shipped with JBoss:
                   - org.jboss.deployment.DeploymentSorter
                   Sorts by file extension, as follows:
                   "sar", "service.xml", "rar", "jar", "war", "wsr", "ear", "zip",
                   "*"
                   - org.jboss.deployment.scanner.PrefixDeploymentSorter
                   If the name portion of the url begins with 1 or more digits, those
                   digits are converted to an int (ignoring leading zeroes), and
                   files are deployed in that order. Files that do not start with
                   any digits will be deployed last, and they will be sorted by
                   extension as above with DeploymentSorter.
                   -->
                   <attribute name="URLComparator">org.jboss.deployment.DeploymentSorter</attribute>
                   <!-- The Filter specifies a java.io.FileFilter for scanned
                   directories. Any file not accepted by this filter will not be
                   deployed. The org.jboss.deployment.scanner.DeploymentFilter
                   rejects the following patterns:
                   "#*", "%*", ",*", ".*", "_$*", "*#", "*$", "*%", "*.BAK",
                   "*.old", "*.orig", "*.rej", "*.bak", "*,v", "*~", ".make.state",
                   ".nse_depinfo", "CVS", "CVS.admin", "RCS", "RCSLOG", "SCCS",
                   "TAGS", "core", "tags"
                   -->
                   <attribute name="Filter">org.jboss.deployment.scanner.DeploymentFilter</attribute>
                  
                   <attribute name="ScanPeriod">5000</attribute>
                  
                   <!-- URLs are comma seperated and unprefixed arguments are considered
                   file URLs and resolve relative to server home(JBOSS_DIST/server/default)
                   unless the given path is absolute. Any referenced directories cannot
                   be unpackaged archives, use the parent directory of the unpacked
                   archive.
                   -->
                   <attribute name="URLs">
                   deploy/
                   </attribute>
                   </mbean>
                  
                  
                  </server>
                  


                  build.xml
                  <?xml version="1.0" encoding="UTF-8"?>
                  <!-- This is an Ant build script that creates a minimal jbossmq
                  configuration based on the default configuration
                  -->
                  <project name="Mininal JBossMQ configuration script" default="config">
                  
                   <!-- Override if the script is not run from within the
                   dist/docs/examples/jms/standalone directory.
                   -->
                   <property name="jboss.dist" value="../../../.."/>
                  
                   <target name="config">
                  
                   <!-- We are mainly based on the minimal configuration -->
                   <copy todir="${jboss.dist}/server/jbossmq">
                   <fileset dir="${jboss.dist}/server/minimal">
                   <exclude name="conf/jboss-service.xml"/>
                   <exclude name="lib/jboss-minimal.jar"/>
                   </fileset>
                   </copy>
                  
                   <!-- We need the following from the default configuration -->
                   <copy todir="${jboss.dist}/server/jbossmq">
                   <fileset dir="${jboss.dist}/server/default">
                   <!-- configuration -->
                   <include name="conf/login-config.xml"/>
                   <include name="conf/xmdesc/*"/>
                   <!-- the main jboss jar -->
                   <include name="lib/jboss.jar"/>
                   <!-- jaas -->
                   <include name="lib/jbosssx.jar"/>
                   <!-- transactions -->
                   <include name="lib/jboss-transaction.jar"/>
                   <!-- jms interfaces -->
                   <include name="lib/jboss-j2ee.jar"/>
                   <!-- local db support -->
                   <include name="lib/jboss-common-jdbc-wrapper.jar"/>
                   <include name="lib/xalan.jar"/>
                   <include name="lib/jboss-jca.jar"/>
                   <include name="deploy/jbossjca-service.xml"/>
                   <include name="deploy/jboss-local-jdbc.rar"/>
                   <include name="conf/standardjbosscmp-jdbc.xml"/>
                   <!-- hypersonic -->
                   <include name="lib/hsqldb*"/>
                   <include name="deploy/hsqldb-ds.xml"/>
                   <include name="deploy/jms/hsqldb-jdbc2-service.xml"/>
                   <include name="deploy/jms/hsqldb-jdbc-state-service.xml"/>
                   <!-- jbossmq -->
                   <include name="lib/jbossmq.jar"/>
                   <include name="deploy/jms/jbossmq-service.xml"/>
                   <include name="deploy/jms/jbossmq-destinations-service.xml"/>
                   <include name="deploy/jms/uil2-service.xml"/>
                   </fileset>
                   </copy>
                  
                   <!-- This is our main configuration -->
                   <copy todir="${jboss.dist}/server/jbossmq/conf/">
                   <fileset dir="${jboss.dist}/docs/examples/jms/standalone">
                   <include name="jboss-service.xml"/>
                   </fileset>
                   </copy>
                  
                   </target>
                  </project>
                  


                  • 6. Re: Problem with JBossMQ+MySQL standalone, no problem with D
                    . . Newbie

                    I've tried the build.xml and jboss-service.xml you gave me, with still no luck, I think it's a DeployException, ClassNotFound, anyway. I could try to get 4.0.1 RC3 from CVS but I am a little in a hurry, so I don't have time to play with it now.

                    I don't want to bother you more ... so I think i'll stick with full JBoss 4.0.0
                    and wait for 4.0.1 final to be released, i'll then try the new JBossMQ standalone ant ;-)

                    Thanks a lot for your help.