5 Replies Latest reply on Apr 13, 2004 3:24 AM by santarr

    Jboss and Mysql, xxxDS not bound problem

    santarr Newbie

      I am not sure in which topic my problem should be posted, so if in the wrong forum, then please move my topic to the correct one and notify me.

      The problem that I am having is with Jboss-3.0.3 and Mysql 4.0.xx, receiving a xxxDS not bound message.

      I received a legacy application from my boss to look into and to get it started once more, unpacked it to find a jboss application. Installed the application with it's configuration files and jboss, made a mysql database for it, changed the config files to point to the new database and activated the default_run that was supplied.

      Since then I tried and searched for quite some time about the xxxDS not bound problem that I received.

      The jboss server is started with a property file :
      %JBOSS_HOME%\bin\run -P properties.prop -L %JBOSS_HOME%\server\lib\jdom.jar

      The property file states among other things :
      database.jndi.name=java:/MySqlDS

      Then I have a mysql-ds.xml file :

      <local-tx-datasource>
      <jndi-name>MySqlDS</jndi-name>
      <connection-url>jdbc:mysql://localhost:3306/xxx</connection-url>
      <driver-class>com.mysql.jdbc.Driver</driver-class>
      <user-name>xxx</user-name>
      xxx
      </local-tx-datasource>


      Recently I tried and just added a mysql-service.xml file to the project tho another file called jboss-service.xml inside the Meta-inf dir of the project also states the same things, just to see if perhaps something was not loaded.. now I receive this full warning : (Note before this it would stop at the xxx DS not bound message)

      C:\jboss-3.0.3\server\default>c:\jboss-3.0.3\bin\run.bat -P c:\jboss-3.0.3\server\default\conf\xxx.properties -L jdom.jar
      ===============================================================================
      .
      JBoss Bootstrap Environment
      .
      JBOSS_HOME: c:\jboss-3.0.3\bin\\..
      .
      JAVA: c:\j2sdk1.4.1_02\bin\java
      .
      JAVA_OPTS: -Dprogram.name=run.bat
      .
      CLASSPATH: ;c:\j2sdk1.4.1_02\lib\tools.jar;c:\jboss-3.0.3\bin\\run.jar
      .
      ===============================================================================
      .
      10:01:54,069 INFO [Server] JBoss Release: JBoss-3.0.3 CVSTag=JBoss_3_0_3
      10:01:54,079 INFO [Server] Home Dir: C:\jboss-3.0.3
      10:01:54,079 INFO [Server] Home URL: file:/C:/jboss-3.0.3/
      10:01:54,079 INFO [Server] Library URL: file:/C:/jboss-3.0.3/lib/
      10:01:54,089 INFO [Server] Patch URL: null
      10:01:54,089 INFO [Server] Server Name: default
      10:01:54,089 INFO [Server] Server Home Dir: C:\jboss-3.0.3\server\default
      10:01:54,089 INFO [Server] Server Home URL: file:/C:/jboss-3.0.3/server/default/
      10:01:54,089 INFO [Server] Server Data Dir: C:\jboss-3.0.3\server\default\db
      10:01:54,089 INFO [Server] Server Temp Dir: C:\jboss-3.0.3\server\default\tmp
      10:01:54,089 INFO [Server] Server Config URL: file:/C:/jboss-3.0.3/server/default/conf/
      10:01:54,099 INFO [Server] Server Library URL: file:/C:/jboss-3.0.3/server/default/lib/
      10:01:54,099 INFO [Server] Root Deployemnt Filename: jboss-service.xml
      10:01:54,099 INFO [Server] Starting General Purpose Architecture (GPA)...
      10:01:54,309 INFO [ServerInfo] Java version: 1.4.1_02,Sun Microsystems Inc.
      10:01:54,309 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.4.1_02-b06,Sun Microsystems Inc.
      10:01:54,309 INFO [ServerInfo] OS-System: Windows 2000 5.0,x86
      10:01:54,350 INFO [ServiceController] Controller MBean online
      10:01:54,410 INFO [MainDeployer] Creating
      10:01:54,430 INFO [MainDeployer] Created
      10:01:54,440 INFO [MainDeployer] Starting
      10:01:54,440 INFO [MainDeployer] Started
      10:01:54,450 INFO [JARDeployer] Creating
      10:01:54,450 INFO [JARDeployer] Created
      10:01:54,450 INFO [JARDeployer] Starting
      10:01:54,450 INFO [MainDeployer] Adding deployer: org.jboss.deployment.JARDeployer@20be79
      10:01:54,450 INFO [JARDeployer] Started
      10:01:54,460 INFO [SARDeployer] Creating
      10:01:54,460 INFO [SARDeployer] Created
      10:01:54,460 INFO [SARDeployer] Starting
      10:01:54,460 INFO [MainDeployer] Adding deployer: org.jboss.deployment.SARDeployer@482923
      10:01:54,490 INFO [SARDeployer] Started
      10:01:54,490 INFO [Server] Core system initialized
      10:01:54,490 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/conf/jboss-service.xml
      10:01:54,600 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/mysql-connector-java-3.0.11-stable-bin.jar
      10:01:54,670 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/mysql-connector-java-3.0.11-stable-bin.jar
      10:01:54,670 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/aqapi.jar
      10:01:54,730 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/aqapi.jar
      10:01:54,730 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jbossmx.jar
      10:01:54,750 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jbossmx.jar
      10:01:54,750 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jboss-jsr77.jar
      10:01:54,770 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jboss-jsr77.jar
      10:01:54,780 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/log4j.jar
      10:01:54,840 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/log4j.jar
      10:01:54,840 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jaas.jar
      10:01:54,880 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jaas.jar
      10:01:54,880 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/activation.jar
      10:01:54,910 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/activation.jar
      10:01:54,910 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/tyrex.jar
      10:01:54,960 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/tyrex.jar
      10:01:54,970 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/mail-plugin.jar
      10:01:54,980 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/mail-plugin.jar
      10:01:54,980 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jboss.jar
      10:01:55,171 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jboss.jar
      10:01:55,171 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jpl-util.jar
      10:01:55,191 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jpl-util.jar
      10:01:55,191 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jmxtools.jar
      10:01:55,221 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jmxtools.jar
      10:01:55,221 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/castor.jar
      10:01:55,421 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/castor.jar references URL file:/C:/jboss-3.0.3/server/default/lib/xerces.jar, which could not be opened, entry ignored
      10:01:55,421 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/castor.jar references URL file:/C:/jboss-3.0.3/server/default/lib/jdbc-se2.0.jar, which could not be opened, entry ignored
      10:01:55,421 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/castor.jar references URL file:/C:/jboss-3.0.3/server/default/lib/jndi.jar, which could not be opened, entry ignored
      10:01:55,421 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/castor.jar references URL file:/C:/jboss-3.0.3/server/default/lib/jta1.0.1.jar which could not be opened, entry ignored
      10:01:55,431 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/castor.jar
      10:01:55,431 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/scheduler-plugin.jar
      10:01:55,481 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/scheduler-plugin.jar
      10:01:55,481 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jts.jar
      10:01:55,521 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jts.jar
      10:01:55,521 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/hsqldb.jar
      10:01:55,561 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/hsqldb.jar
      10:01:55,561 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jbossha.jar
      10:01:55,591 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jbossha.jar
      10:01:55,591 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jbosssx.jar
      10:01:55,631 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jbosssx.jar
      10:01:55,631 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jsse.jar
      10:01:55,721 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jsse.jar
      10:01:55,721 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jnpserver.jar
      10:01:55,742 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jnpserver.jar
      10:01:55,742 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/scheduler-plugin-example.jar
      10:01:55,762 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/scheduler-plugin-example.jar
      10:01:55,762 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jcert.jar
      10:01:55,782 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jcert.jar
      10:01:55,782 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/commons-digester.jar
      10:01:55,812 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/commons-digester.jar
      10:01:55,812 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/javax.servlet.jar
      10:01:55,882 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/javax.servlet.jar
      10:01:55,882 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/commons-logging.jar
      10:01:55,902 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/commons-logging.jar references URL file:/C:/jboss-3.0.3/server/default/lib/log4j-core.jar which could not be opened, entry ignored
      10:01:55,902 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/commons-logging.jar
      10:01:55,902 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jboss-jca.jar
      10:01:55,932 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jboss-jca.jar
      10:01:55,932 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/commons-beanutils.jar
      10:01:55,972 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/commons-beanutils.jar
      10:01:55,972 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/hsqldb-plugin.jar
      10:01:55,992 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/hsqldb-plugin.jar
      10:01:55,992 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/xalan.jar
      10:01:56,112 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/xalan.jar references URL file:/C:/jboss-3.0.3/server/default/lib/jaxp.jar which could not be opened, entry ignored
      10:01:56,112 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/xalan.jar references URL file:/C:/jboss-3.0.3/server/default/lib/xerces.jar which could not be opened, entry ignored
      10:01:56,112 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/xalan.jar references URL file:/C:/jboss-3.0.3/server/default/lib/crimson.jar which could not be opened, entry ignored
      10:01:56,112 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/xalan.jar
      10:01:56,112 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/bcel.jar
      10:01:56,182 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/bcel.jar
      10:01:56,182 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jboss-management.jar
      10:01:56,212 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jboss-management.jar
      10:01:56,212 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/ant.jar
      10:01:56,272 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/ant.jar references URL file:/C:/jboss-3.0.3/server/default/lib/jaxp.jar which could not be opened, entry ignored
      10:01:56,272 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/ant.jar references URL file:/C:/jboss-3.0.3/server/default/lib/parser.jar which could not be opened, entry ignored
      10:01:56,272 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/ant.jar references URL file:/C:/jboss-3.0.3/server/default/lib/crimson.jar which could not be opened, entry ignored
      10:01:56,272 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/ant.jar references URL file:/C:/jboss-3.0.3/server/default/lib/optional.jar which could not be opened, entry ignored
      10:01:56,282 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/ant.jar
      10:01:56,282 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/mmx-logger.jar
      10:01:56,312 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/mmx-logger.jar
      10:01:56,312 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/commons-collections.jar
      10:01:56,352 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/commons-collections.jar
      10:01:56,352 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/properties-plugin.jar
      10:01:56,372 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/properties-plugin.jar
      10:01:56,372 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/mail.jar
      10:01:56,453 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/mail.jar
      10:01:56,453 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jmxri.jar
      10:01:56,493 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jmxri.jar
      10:01:56,503 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/autonumber-plugin.jar
      10:01:56,513 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/autonumber-plugin.jar
      10:01:56,513 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jbossmq.jar
      10:01:56,583 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jbossmq.jar
      10:01:56,583 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/process-plugin.jar
      10:01:56,603 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/process-plugin.jar
      10:01:56,603 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jpl-pattern.jar
      10:01:56,623 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jpl-pattern.jar
      10:01:56,623 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/counter-plugin.jar
      10:01:56,643 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/counter-plugin.jar
      10:01:56,643 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/commons-logging-api.jar
      10:01:56,663 WARN [MainDeployer] The manifest entry in file:/C:/jboss-3.0.3/server/default/lib/commons-logging-api.jar references URL file:/C:/jboss-3.0.3/server/default/lib/log4j-core.jar which could not be opened, entry ignored
      10:01:56,663 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/commons-logging-api.jar
      10:01:56,663 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jnet.jar
      10:01:56,693 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jnet.jar
      10:01:56,693 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/jboss-j2ee.jar
      10:01:56,723 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/jboss-j2ee.jar
      10:01:56,723 INFO [MainDeployer] Starting deployment of package: file:/C:/jboss-3.0.3/server/default/lib/classes12.jar
      10:01:56,883 INFO [MainDeployer] Deployed package: file:/C:/jboss-3.0.3/server/default/lib/classes12.jar
      10:01:57,514 INFO [PropertyEditorManagerService] Creating
      10:01:57,514 INFO [PropertyEditorManagerService] Created
      10:01:57,514 INFO [SystemPropertiesService] Creating
      10:01:57,524 INFO [SystemPropertiesService] Created
      10:01:57,524 INFO [Log4jService] Creating
      10:01:57,524 INFO [Log4jService] Created
      10:01:57,524 INFO [WebService] Creating
      10:01:57,524 INFO [WebService] Created
      10:01:57,524 WARN [ServiceController] jboss.management.single:j2eeType=J2EEDomain,name=Manager does not implement any Service methods
      10:01:57,524 INFO [NamingService] Creating
      10:01:57,524 INFO [NamingService] Created
      10:01:57,524 INFO [JNDIView] Creating
      10:01:57,524 INFO [JNDIView] Created
      10:01:57,524 INFO [SecurityConfig] Creating
      10:01:57,524 INFO [SecurityConfig] Created
      10:01:57,524 INFO [JaasSecurityManagerService] Creating
      10:01:57,524 INFO [JaasSecurityManagerService] Created
      10:01:57,524 WARN [ServiceController] jboss:service=XidFactory does not implement any Service methods
      10:01:57,524 INFO [TransactionManagerService] Creating
      10:01:57,524 INFO [TransactionManagerService] Created
      10:01:57,524 INFO [ClientUserTransactionService] Creating
      10:01:57,524 INFO [ClientUserTransactionService] Created
      10:01:57,524 INFO [CachedConnectionManager] Creating
      10:01:57,524 INFO [CachedConnectionManager] Created
      10:01:57,524 INFO [EARDeployer] Creating
      10:01:57,524 INFO [EARDeployer] Created
      10:01:57,524 INFO [JRMPInvoker] created
      10:01:57,524 INFO [LocalInvoker] Creating
      10:01:57,534 INFO [LocalInvoker] Created
      10:01:57,534 INFO [URLDeploymentScanner] Creating
      10:01:57,534 INFO [URLDeploymentScanner] Created
      10:01:57,534 INFO [PropertyEditorManagerService] Starting
      10:01:57,534 INFO [PropertyEditorManagerService] Started
      10:01:57,534 INFO [SystemPropertiesService] Starting
      10:01:57,534 INFO [SystemPropertiesService] Started
      10:01:57,544 INFO [Log4jService] Starting
      10:01:57,544 INFO [AbstractDeploymentScanner$ScannerThread] Running
      10:01:57,554 INFO [Log4jService$URLWatchTimerTask] Configuring from URL: resource:log4j.xml
      10:02:00,859 ERROR [ConnectionManager] NamingException looking up Database DS
      10:02:00,859 ERROR [ConnectionManager] javax.naming.NameNotFoundException: MySqlDS not bound
      10:02:04,164 ERROR [URLDeploymentScanner] Failed to deploy: org.jboss.deployment.scanner.URLDeploymentScanner$DeployedURL@695a79cc{ url=file:/C:/jboss-3.0.3/server/default/deploy/mysql-service.xml, deployedLastModified=0 }
      org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=MySqlDS
      at org.jboss.system.ServiceCreator.install(ServiceCreator.java:69)
      at org.jboss.system.ServiceConfigurator.internalInstall(ServiceConfigurator.java:167)
      at org.jboss.system.ServiceConfigurator.install(ServiceConfigurator.java:130)
      at org.jboss.system.ServiceController.install(ServiceController.java:225)
      at sun.reflect.GeneratedMethodAccessor9.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy3.install(Unknown Source)
      at org.jboss.deployment.SARDeployer.create(SARDeployer.java:209)
      at org.jboss.deployment.MainDeployer.create(MainDeployer.java:755)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:615)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
      at sun.reflect.GeneratedMethodAccessor11.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy4.deploy(Unknown Source)
      at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:427)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scanDirectory(URLDeploymentScanner.java:648)
      at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:499)
      at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:261)
      at org.jboss.system.ServiceMBeanSupport.start(ServiceMBeanSupport.java:164)
      at sun.reflect.GeneratedMethodAccessor8.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:976)
      at $Proxy0.start(Unknown Source)
      at org.jboss.system.ServiceController.start(ServiceController.java:397)
      at sun.reflect.GeneratedMethodAccessor6.invoke(Unknown Source)
      at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
      at java.lang.reflect.Method.invoke(Method.java:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.util.jmx.MBeanProxy.invoke(MBeanProxy.java:174)
      at $Proxy3.start(Unknown Source)
      at org.jboss.deployment.SARDeployer.start(SARDeployer.java:249)
      at org.jboss.deployment.MainDeployer.start(MainDeployer.java:802)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:616)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:580)
      at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:564)
      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:324)
      at org.jboss.mx.capability.ReflectedMBeanDispatcher.invoke(ReflectedMBeanDispatcher.java:284)
      at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:517)
      at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:324)
      at org.jboss.system.server.ServerImpl.start(ServerImpl.java:221)
      at org.jboss.Main.boot(Main.java:148)
      at org.jboss.Main$1.run(Main.java:381)
      at java.lang.Thread.run(Thread.java:536)
      10:02:08,029 ERROR [URLDeploymentScanner] MBeanException: Exception in MBean operation 'checkIncompleteDeployments()'
      Cause: Incomplete Deployment listing:
      Packages waiting for a deployer:

      Incompletely deployed packages:
      [org.jboss.deployment.DeploymentInfo@695a79cc { url=file:/C:/jboss-3.0.3/server/default/deploy/mysql-service.xml }
      deployer: org.jboss.deployment.SARDeployer@482923
      status: Deployment FAILED reason: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=MySqlDS
      state: FAILED
      watch: file:/C:/jboss-3.0.3/server/default/deploy/mysql-service.xml
      lastDeployed: 1081411324154
      lastModified: 1081411324094
      mbeans:
      ]MBeans waiting for classes:

      MBeans waiting for other MBeans:


      Tried switching the mysql drivers, both inside the lib directory and the config files, changing the mysql database to the default database, but this would also fail, etc.. So I'm sure I'm making a mistake somewhere, I just can't find it any pointers or help would be appreciated.. The App seems to use the hypersonic db for queue's and the mysql database for bean data normally..

        • 1. Re: Jboss and Mysql, xxxDS not bound problem
          Adrian Brock Master

          The message you posted says it is trying to install the connection manager twice.

          org.jboss.deployment.DeploymentException: Trying to install an already registered mbean: jboss.jca:service=LocalTxCM,name=MySqlDS

          It is hard to tell what is going on because you appear to have broken your
          conf/log4j.xml
          Once this is configured, all logging disappears.

          The local-tx-datasource configuration is a 3.2.x configuration
          I don't see how you can use it in 3.0.3

          Regards,
          Adrian

          • 2. Re: Jboss and Mysql, xxxDS not bound problem
            santarr Newbie

            Thank you for your answer, The second attempt to install the connectionmanager was a test of mine to see if jboss would reach the database, have removed this now.

            I Temporarily disabled the log4j.xml file so I have normal logging.

            The 3.2.x. database config was also added as a test.. but removed this as well, from boot.log I now receive this error still :

            11:00:00,966 INFO [Scheduler] Starting
            11:00:00,976 DEBUG [Scheduler] Start Scheduler on start up time
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::static - BEGIN
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::initialize - BEGIN
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager:: JNDI name : java:/MySQLDS
            11:00:01,036 ERROR [ConnectionManager] NamingException looking up Database DS
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::static - END
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::getConnection - BEGIN
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::initialize - BEGIN
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager:: JNDI name : java:/MySQLDS
            11:00:01,036 ERROR [ConnectionManager] javax.naming.NameNotFoundException: MySQLDS not bound
            11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::getConnection - END
            11:00:01,046 WARN [QueueScheduler] Start-up failed: Database not ready!

            Which was my original error I started with, just with more information.

            My jboss-service.xml file looks like this internally :


            <!-- ==================================================================== -->
            <!-- XXX JMS Queues -->
            <!-- ==================================================================== -->

            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager



            <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager


            <!-- MMX Requeue Scheduler
            Description: Starts a scheduler to check for messages that needs to be requeued
            Time interval between tasks: 60 * 1000 (60000) msec
            -->


            true
            nl.mobileminds.mmx.addon.queueing.QueueScheduler
            0
            60000
            -1


            <!-- MMX QuizMaster Requeue Scheduler
            Description: Starts a scheduler to check for messages that needs to be requeued
            Time interval between tasks: 60 * 1000 (60000) msec


            true
            nl.mobileminds.application.quizmaster.queueing.QueueScheduler
            0
            30000
            -1


            -->
            <!-- MMX Quiz Game Scheduler
            Description: Starts a scheduler to check for messages that needs to be requeued
            Time interval between tasks: 60 * 1000 (60000) msec


            true
            nl.mobileminds.application.quizmaster.queueing.GameScheduler
            0
            30000
            -1


            -->
            <!-- MMX Quiz Cycle Scheduler
            Description: Starts a scheduler to check for messages that needs to be requeued
            Time interval between tasks: 60 * 1000 (60000) msec


            true
            nl.mobileminds.application.quizmaster.queueing.CycleScheduler
            0
            60000
            -1


            -->

            <!-- ==================================================================== -->
            <!-- ConnectionManager setup for MySQL DBMS -->
            <!-- ==================================================================== -->



            <depends optional-attribute-name="ManagedConnectionFactoryName">

            <!--embedded mbean-->


            MySQLDS


            <config-property
            name="ConnectionURL"
            type="java.lang.String">jdbc:mysql://localhost:3306/mmx
            </config-property>
            <config-property
            name="DriverClass"
            type="java.lang.String">com.mysql.jdbc.Driver
            </config-property>
            <!--set these only if you want only default logins, not through JAAS -->
            <config-property name="UserName" type="java.lang.String">xxx</config-property>
            <config-property name="Password" type="java.lang.String">xxx</config-property>



            <!--Below here are advanced properties -->
            <!--hack-->
            <depends optional-attribute-name="OldRarDeployment">
            jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper




            <depends optional-attribute-name="ManagedConnectionPool">
            <!--embedded mbean-->


            0
            50
            5000
            15
            ByContainer



            <depends optional-attribute-name="CachedConnectionManager">
            jboss.jca:service=CachedConnectionManager

            <depends optional-attribute-name="JaasSecurityManagerService">
            jboss.security:service=JaasSecurityManager


            java:/TransactionManager

            <!--make the rar deploy! hack till better deployment-->
            jboss.jca:service=RARDeployer





            The server is still started with the same property file and it states :
            database.jndi.name=java:/MySqlDS

            I Have tried switching the IP inside the DB part around to see if I had my privileges right for MySQL, but I had them right, for xxx@localhost may connect, using other parts there results in Query and DB connect errors.

            It seems as tho the database is being connected to, I can see 2 tables being opened, yet somewhere the connectionmanager can not bound to the databases. I checked the code of the connectionmanager and it seems to be correct (checked it against information of how to do it correct).

            Relevant parts of the connectionmanager :

            public class ConnectionManager
            {
            private static DataSource dataSource = null;
            private static Log logger = LogFactory.getLog(ConnectionManager.class);

            static {
            logger.debug("ConnectionManager::static - BEGIN");

            try {
            initialize();
            } catch (NamingException ne) {
            logger.error("NamingException looking up Database DS");
            }

            logger.debug("ConnectionManager::static - END");
            }


            private static void initialize() throws NamingException {
            logger.debug("ConnectionManager::initialize - BEGIN");

            Context iniCtx = new InitialContext();
            String dsJndiName = System.getProperty("database.jndi.name.mmx").trim();
            logger.debug("ConnectionManager:: JNDI name : " + dsJndiName);
            if (dsJndiName == null)
            throw new NamingException("Datasource JNDI name not configured.");
            dataSource = (DataSource) iniCtx.lookup(dsJndiName);
            logger.debug("ConnectionManager::initialize - END");
            }

            public static Connection getConnection() throws SQLException
            {
            logger.debug("ConnectionManager::getConnection - BEGIN");
            Connection conn = null;

            try {
            if (dataSource == null) initialize();
            conn = dataSource.getConnection();
            } catch (NamingException ne) {logger.error(ne);}
            logger.debug("ConnectionManager::getConnection - END");
            return conn;
            }

            }

            Does anyone have any ideas ? If correct this set-up and code should have worked and not result in any errors..

            • 3. Re: Jboss and Mysql, xxxDS not bound problem
              santarr Newbie

              Some tags in my previous message seem to have disappeared.. trying again :

              Thank you for your answer, The second attempt to install the connectionmanager was a test of mine to see if jboss would reach the database, have removed this now.

              I Temporarily disabled the log4j.xml file so I have normal logging.

              The 3.2.x. database config was also added as a test.. but removed this as well, from boot.log I now receive this error still :

              11:00:00,966 INFO [Scheduler] Starting
              11:00:00,976 DEBUG [Scheduler] Start Scheduler on start up time
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::static - BEGIN
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::initialize - BEGIN
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager:: JNDI name : java:/MySQLDS
              11:00:01,036 ERROR [ConnectionManager] NamingException looking up Database DS
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::static - END
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::getConnection - BEGIN
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::initialize - BEGIN
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager:: JNDI name : java:/MySQLDS
              11:00:01,036 ERROR [ConnectionManager] javax.naming.NameNotFoundException: MySQLDS not bound
              11:00:01,036 DEBUG [ConnectionManager] ConnectionManager::getConnection - END
              11:00:01,046 WARN [QueueScheduler] Start-up failed: Database not ready!
              


              Which was my original error I started with, just with more information.

              My jboss-service.xml file looks like this internally :

              <server>
              
               <!-- ==================================================================== -->
               <!-- MMX JMS Queues -->
               <!-- ==================================================================== -->
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=ReportOutQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=ReportInQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=SubmitOutQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=SubmitInQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=DeliverOutQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=DeliverInQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=QuizMasterOutQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <mbean code="org.jboss.mq.server.jmx.Queue"
               name="jboss.mq.destination:service=Queue,name=QuizMasterInQ">
               <depends optional-attribute-name="DestinationManager">jboss.mq:service=DestinationManager</depends>
               </mbean>
              
               <!-- MMX Requeue Scheduler
               Description: Starts a scheduler to check for messages that needs to be requeued
               Time interval between tasks: 60 * 1000 (60000) msec
               -->
               <mbean
               code="org.jboss.varia.scheduler.Scheduler"
               name="jboss.util:service=Scheduler,type=RequeueSchedulerTasks">
              
               <attribute name="StartAtStartup">true</attribute>
               <attribute name="SchedulableClass">nl.mobileminds.mmx.addon.queueing.QueueScheduler</attribute>
               <attribute name="InitialStartDate">0</attribute>
               <attribute name="SchedulePeriod">60000</attribute>
               <attribute name="InitialRepetitions">-1</attribute>
               </mbean>
              
               <!-- MMX QuizMaster Requeue Scheduler
               Description: Starts a scheduler to check for messages that needs to be requeued
               Time interval between tasks: 60 * 1000 (60000) msec
               <mbean
               code="org.jboss.varia.scheduler.Scheduler"
               name="jboss.util:service=Scheduler,type=RequeueQuestionSchedulerTasks">
              
               <attribute name="StartAtStartup">true</attribute>
               <attribute name="SchedulableClass">nl.mobileminds.application.quizmaster.queueing.QueueScheduler</attribute>
               <attribute name="InitialStartDate">0</attribute>
               <attribute name="SchedulePeriod">30000</attribute>
               <attribute name="InitialRepetitions">-1</attribute>
               </mbean>
              
               -->
               <!-- MMX Quiz Game Scheduler
               Description: Starts a scheduler to check for messages that needs to be requeued
               Time interval between tasks: 60 * 1000 (60000) msec
               <mbean
               code="org.jboss.varia.scheduler.Scheduler"
               name="jboss.util:service=Scheduler,type=RequeueGameSchedulerTasks">
              
               <attribute name="StartAtStartup">true</attribute>
               <attribute name="SchedulableClass">nl.mobileminds.application.quizmaster.queueing.GameScheduler</attribute>
               <attribute name="InitialStartDate">0</attribute>
               <attribute name="SchedulePeriod">30000</attribute>
               <attribute name="InitialRepetitions">-1</attribute>
               </mbean>
              
               -->
               <!-- MMX Quiz Cycle Scheduler
               Description: Starts a scheduler to check for messages that needs to be requeued
               Time interval between tasks: 60 * 1000 (60000) msec
               <mbean
               code="org.jboss.varia.scheduler.Scheduler"
               name="jboss.util:service=Scheduler,type=RequeueCycleSchedulerTasks">
              
               <attribute name="StartAtStartup">true</attribute>
               <attribute name="SchedulableClass">nl.mobileminds.application.quizmaster.queueing.CycleScheduler</attribute>
               <attribute name="InitialStartDate">0</attribute>
               <attribute name="SchedulePeriod">60000</attribute>
               <attribute name="InitialRepetitions">-1</attribute>
               </mbean>
              
               -->
              
               <!-- ==================================================================== -->
               <!-- ConnectionManager setup for MySQL DBMS -->
               <!-- ==================================================================== -->
              
               <mbean
               code="org.jboss.resource.connectionmanager.LocalTxConnectionManager"
               name="jboss.jca:service=LocalTxCM,name=MySQLDS">
              
               <depends optional-attribute-name="ManagedConnectionFactoryName">
              
               <!--embedded mbean-->
               <mbean
               code="org.jboss.resource.connectionmanager.RARDeployment"
               name="jboss.jca:service=LocalTxDS,name=MySQLDS">
              
               <attribute name="JndiName">MySQLDS</attribute>
               <attribute name="ManagedConnectionFactoryProperties">
               <properties>
               <config-property
               name="ConnectionURL"
               type="java.lang.String">jdbc:mysql://localhost:3306/mmx
               </config-property>
               <config-property
               name="DriverClass"
               type="java.lang.String">com.mysql.jdbc.Driver
               </config-property>
               <!--set these only if you want only default logins, not through JAAS -->
               <config-property name="UserName" type="java.lang.String">mmx</config-property>
               <config-property name="Password" type="java.lang.String">mmx</config-property>
               </properties>
               </attribute>
              
               <!--Below here are advanced properties -->
               <!--hack-->
               <depends optional-attribute-name="OldRarDeployment">
               jboss.jca:service=RARDeployment,name=JBoss LocalTransaction JDBC Wrapper
               </depends>
               </mbean>
               </depends>
              
               <depends optional-attribute-name="ManagedConnectionPool">
               <!--embedded mbean-->
               <mbean
               code="org.jboss.resource.connectionmanager.JBossManagedConnectionPool"
               name="jboss.jca:service=LocalTxPool,name=MySQLDS">
              
               <attribute name="MinSize">0</attribute>
               <attribute name="MaxSize">50</attribute>
               <attribute name="BlockingTimeoutMillis">5000</attribute>
               <attribute name="IdleTimeoutMinutes">15</attribute>
               <attribute name="Criteria">ByContainer</attribute>
               </mbean>
               </depends>
              
               <depends optional-attribute-name="CachedConnectionManager">
               jboss.jca:service=CachedConnectionManager
               </depends>
               <depends optional-attribute-name="JaasSecurityManagerService">
               jboss.security:service=JaasSecurityManager
               </depends>
              
               <attribute name="TransactionManager">java:/TransactionManager</attribute>
              
               <!--make the rar deploy! hack till better deployment-->
               <depends>jboss.jca:service=RARDeployer</depends>
              
               </mbean>
              
              </server>
              


              The server is still started with the same property file and it states :
              database.jndi.name=java:/MySqlDS

              I Have tried switching the IP inside the DB part around to see if I had my privileges right for MySQL, but I had them right, for xxx@localhost may connect, using other parts there results in Query and DB connect errors.

              It seems as tho the database is being connected to, I can see 2 tables being opened, yet somewhere the connectionmanager can not bound to the databases. I checked the code of the connectionmanager and it seems to be correct (checked it against information of how to do it correct).

              Relevant parts of the connectionmanager :

              public class ConnectionManager
              {
               private static DataSource dataSource = null;
               private static Log logger = LogFactory.getLog(ConnectionManager.class);
              
               static {
               logger.debug("ConnectionManager::static - BEGIN");
              
               try {
               initialize();
               } catch (NamingException ne) {
               logger.error("NamingException looking up Database DS");
               }
              
               logger.debug("ConnectionManager::static - END");
               }
              
              
               private static void initialize() throws NamingException {
               logger.debug("ConnectionManager::initialize - BEGIN");
              
               Context iniCtx = new InitialContext();
               String dsJndiName = System.getProperty("database.jndi.name.mmx").trim();
               logger.debug("ConnectionManager:: JNDI name : " + dsJndiName);
               if (dsJndiName == null)
               throw new NamingException("Datasource JNDI name not configured.");
               dataSource = (DataSource) iniCtx.lookup(dsJndiName);
               logger.debug("ConnectionManager::initialize - END");
               }
              
               public static Connection getConnection() throws SQLException
               {
               logger.debug("ConnectionManager::getConnection - BEGIN");
               Connection conn = null;
              
               try {
               if (dataSource == null) initialize();
               conn = dataSource.getConnection();
               } catch (NamingException ne) {logger.error(ne);}
               logger.debug("ConnectionManager::getConnection - END");
               return conn;
               }
              
              }
              


              Does anyone have any ideas ? If correct this set-up and code should have worked and not result in any errors.. At least that was told to me..


              • 4. Re: Jboss and Mysql, xxxDS not bound problem
                Adrian Brock Master

                Add the following to whatever mbean is trying to use the DataSource before it
                is started (the scheduler?)

                <depends>jboss.jca:service=LocalTxCM,name=MySQLDS</depends>
                





                • 5. Re: Jboss and Mysql, xxxDS not bound problem
                  santarr Newbie

                  That last one seemed to have solved my problem, thanks !
                  It was lacking in 4 different schedulers it seemed.. (found a empty space in between lines there.. weird.. (QueueScheduler, etc..)

                  At least I can now see the server start without any errors in the logging. So it should run nicely from now on..