5 Replies Latest reply on May 5, 2015 7:09 PM by pioflor

Jboss add mysql and start server

pioflor Apr 29, 2015 8:26 PM

I cannot configure Jboss. I want to add module MySQL to JBoss.

There is a written in my handbook that I have add the following lines:

<subsystem xmlns="urn:jboss:domain:darasource:1.0">
    <datasources>
        <datasource jta="false" jndi-name="java:jboss/datasource/jbossas7development" pool-name="jbossas7development" enabled="true">
            <connection-url>
                jdbc:mysql://localhost:3306/ticketsystem
            </connection-url>
            <driver-class>com.mysql.jdbc.Driver</driver-class>
            <driver>mysql</driver>
            <security>
                <user-name>jboss</user-name>
                <password>jboss</password>
            </security>
        </datasource>
        <drivers>
            <driver name="mysql" module="com.mysql"/>
        </drivers>
    </datasources>
</subsystem>

I have a proper file structure:

pioflor@pioflor-IdeaPad-S210-Touch:~$ cd wildfly-8.0.0.Final/modules/com/mysql/main/
pioflor@pioflor-IdeaPad-S210-Touch:~/wildfly-8.0.0.Final/modules/com/mysql/main$ ls
module.xml mysql-connector-java-5.1.35-bin.jar
pioflor@pioflor-IdeaPad-S210-Touch:~/wildfly-8.0.0.Final/modules/com/mysql/main$ cat module.xml 
<module xmlns="urn:jboss:module:1.0" name="com.mysql">
  <resources>
  <resource-root path="mysql-connector-java-5.1.35-bin.jar"/>
  </resources>
  <dependencies>
  <module name="javax.api"/>
  <module name="javax.transaction.api"/>
  </dependencies>
</module>pioflor@pioflor-IdeaPad-S210-Touch:~/wildfly-8.0.0.Final/modules/com/mysql/main$

But when I run ./standalone.sh, I see in the console:

23:31:45,324 ERROR [org.jboss.as.server] (Controller Boot Thread) JBAS015956: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: JBAS014676: Failed to parse configuration
  at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:112) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
  at org.jboss.as.server.ServerService.boot(ServerService.java:331) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
  at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:256) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
  at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_31]
Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[157,9]
Message: Unexpected element '{urn:jboss:domain:darasource:1.0}subsystem'
  at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
  at org.jboss.staxmapper.XMLExtendedStreamReaderImpl.handleAny(XMLExtendedStreamReaderImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
  at org.jboss.as.server.parsing.StandaloneXml.parseServerProfile(StandaloneXml.java:1131) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
  at org.jboss.as.server.parsing.StandaloneXml.readServerElement_1_4(StandaloneXml.java:458) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
  at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:145) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
  at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:107) [wildfly-server-8.0.0.Final.jar:8.0.0.Final]
  at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:110) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
  at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69) [staxmapper-1.1.0.Final.jar:1.1.0.Final]
  at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:104) [wildfly-controller-8.0.0.Final.jar:8.0.0.Final]
  ... 3 more

23:31:45,328 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
23:31:45,457 INFO [org.jboss.as] (MSC service thread 1-1) JBAS015950: WildFly 8.0.0.Final "WildFly" stopped in 11ms
pioflor@pioflor-IdeaPad-S210-Touch:~/wildfly-8.0.0.Final/bin$ ./standalone.sh

1. Re: Jboss add mysql and start server

jaysensharma Apr 29, 2015 10:13 PM (in response to pioflor)

Manually editing the XML files for making configuration changes are not recommended as those are error prone.

In your case we see that you are missing character "s" in the subsystem "darasource" should be "darasources"

Can you try this:

<subsystem xmlns="urn:jboss:domain:darasource:1.0">

TO

<subsystem xmlns="urn:jboss:domain:datasources:1.0">
Actions
2. Re: Jboss add mysql and start server

pioflor May 1, 2015 5:34 PM (in response to jaysensharma)

I changed it

       <subsystem xmlns="urn:jboss:domain:datasources:1.0">
    <datasources>
        <datasource jta="false" jndi-name="java:jboss/datasource/jbossas7development" pool-name="jbossas7development" enabled="true">
            <connection-url>
                jdbc:mysql://localhost:3306/ticketsystem
            </connection-url>
            <driver-class>com.mysql.jdbc.Driver</driver-class>
            <driver>mysql</driver>
            <security>
                <user-name>jboss</user-name>
                <password>jboss</password>
            </security>
        </datasource>
        <drivers>
            <driver name="mysql" module="com.mysql"/>
        </drivers>
    </datasources>
</subsystem>

and

pioflor@pioflor-IdeaPad-S210-Touch:~$ wildfly-8.0.0.Final/bin/standalone.sh
=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /home/pioflor/wildfly-8.0.0.Final

JAVA: java

JAVA_OPTS: -server -XX:+UseCompressedOops -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

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

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
23:31:58,914 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.0.Final
23:31:59,248 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.0.Final
23:31:59,371 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: WildFly 8.0.0.Final "WildFly" starting
23:32:01,256 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 16) JBAS014613: Operation ("add") failed - address: ([("subsystem" => "datasources")]) - failure description: "JBAS014803: Duplicate resource [(\"subsystem\" => \"datasources\")]"
23:32:01,312 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment mojeweb.war
23:32:01,315 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment jsf-managedBean-and-ejb.war
23:32:01,317 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015014: Re-attempting failed deployment statich.war
23:32:01,318 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jsf-managedBean-and-ejb.war in deployment directory. To trigger deployment create a file called jsf-managedBean-and-ejb.war.dodeploy
23:32:01,319 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found statich.war in deployment directory. To trigger deployment create a file called statich.war.dodeploy
23:32:01,321 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found mojeweb.war in deployment directory. To trigger deployment create a file called mojeweb.war.dodeploy
23:32:01,348 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) "JBAS014784: Failed executing subsystem datasources boot operations"
23:32:01,350 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("parallel-subsystem-boot") failed - address: ([]) - failure description: "\"JBAS014784: Failed executing subsystem datasources boot operations\""
23:32:01,365 FATAL [org.jboss.as.server] (Controller Boot Thread) JBAS015957: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
23:32:01,401 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015950: WildFly 8.0.0.Final "WildFly" stopped in 7ms
pioflor@pioflor-IdeaPad-S210-Touch:~$

Are there other ways to configure?
Actions
3. Re: Jboss add mysql and start server

sanjay05222 May 2, 2015 3:37 AM (in response to pioflor)

Please look at this detail hope this might be helpful

mysql Jconnector configuration with wildfly 8.1.0 and issue with version mysql-connector-java-5.0.8

below is the correct sample which work in my system , please make sure that you have one and only on "<subsystem xmlns="urn:jboss:domain:datasources:2.0">" this element and proper closing element based on the error it looks like that you also added one more datasources subsystem.

I hope this helps

SAMPLE CONFIGURATION FOR H2
<subsystem xmlns="urn:jboss:domain:datasources:2.0">
           <datasources>
                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
                    <driver>h2</driver>
                    <security>
                        <user-name>sa</user-name>
                        <password>sa</password>
                    </security>
                </datasource>
                <datasource jta="true" jndi-name="java:jboss/datasources/jbpmDS" pool-name="H2DS" enabled="true" use-java-context="true" use-ccm="true">
                    <connection-url>jdbc:h2:~/jbpm</connection-url>
                    <driver>h2</driver>
                    <security>
                        <user-name>sa</user-name>
                    </security>
                </datasource>
                <drivers>
                    <driver name="h2" module="com.h2database.h2">
                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                    </driver>
                </drivers>
          </datasources>
        </subsystem>
Actions
4. Re: Jboss add mysql and start server

pioflor May 5, 2015 9:12 AM (in response to sanjay05222)

This is my current entry in the file:
[code]
<subsystem xmlns="urn:jboss:domain:datasources:2.0">
            <datasources>
                <datasource jndi-name="java:jboss/datasources/ExampleDS" pool-name="ExampleDS" enabled="true" use-java-context="true">
                    <connection-url>jdbc:h2:mem:test;DB_CLOSE_DELAY=-1;DB_CLOSE_ON_EXIT=FALSE</connection-url>
                    <driver>h2</driver>
                    <security>
                        <user-name>sa</user-name>
                        <password>sa</password>
                    </security>
                </datasource>
                <datasource jta="true" jndi-name="java:/newdatabase" pool-name="newdatabase" enabled="true" use-java-context="true" use-ccm="true">
                    <connection-url>jdbc:mysql://localhost:3306/newdatabase</connection-url>
                    <driver-class>com.mysql.jdbc.Driver</driver-class>
                    <driver>mysql</driver>
                    <security>
                        <user-name>chowniec</user-name>
                        <password>password2</password>
                    </security>
                </datasource>
                <drivers>
                    <driver name="h2" module="com.h2database.h2">
                        <xa-datasource-class>org.h2.jdbcx.JdbcDataSource</xa-datasource-class>
                    </driver>
                    <driver name="mysql" module="com.mysql"/>
                </drivers>
            </datasources>
        </subsystem>
[\code]
When I run server and go to the main website, I see: 404 - Not Found
Actions
5. Re: Jboss add mysql and start server

pioflor May 5, 2015 7:09 PM (in response to pioflor)

I do not understand but the main page works.
When the code is executing in EJB:
[code]
try {
             // String className = "org.gjt.mm.mysql.Driver";
              String className = "com.mysql.jdbc.Driver";
              Class driverObject = Class.forName(className);
              System.out.println("driverObject=" + driverObject);
              System.out.println("your installation of JDBC Driver OK.");
            } catch (Exception e) {
              System.out.println("Failed: JDBC Driver Error: " + e.getMessage());
            }
[\code]
I see in console :
22:07:26,027 INFO [stdout] (default task-4) Failed: JDBC Driver Error: com.mysql.jdbc.Driver from [Module "deployment.jsf-managedBean-and-ejb.war:main" from Service Module Loader]

When the server is started:
[code]
$ Pobrane/wildfly-8.2.0.Final/bin/standalone.sh
=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /home/pioflor/Pobrane/wildfly-8.2.0.Final

JAVA: java

JAVA_OPTS: -server -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

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

Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0
22:39:32,464 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.3.Final
22:39:32,871 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.2.Final
22:39:32,992 INFO [org.jboss.as] (MSC service thread 1-2) JBAS015899: WildFly 8.2.0.Final "Tweek" starting
22:39:34,975 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jsf-managedBean-and-ejb.war in deployment directory. To trigger deployment create a file called jsf-managedBean-and-ejb.war.dodeploy
22:39:35,006 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http)
22:39:35,046 INFO [org.xnio] (MSC service thread 1-2) XNIO version 3.3.0.Final
22:39:35,085 INFO [org.xnio.nio] (MSC service thread 1-2) XNIO NIO Implementation Version 3.3.0.Final
22:39:35,193 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 31) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors
22:39:35,198 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 32) JBAS010280: Activating Infinispan subsystem.
22:39:35,273 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.1.9.Final)
22:39:35,275 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 40) JBAS011800: Activating Naming Subsystem
22:39:35,309 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 38) JBAS012615: Activated the following JSF Implementations: [main]
22:39:35,323 INFO [org.jboss.as.security] (ServerService Thread Pool -- 45) JBAS013171: Activating Security Subsystem
22:39:35,347 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 46) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique.
22:39:35,356 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 27) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)
22:39:35,411 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) JBAS010417: Started Driver service with driver-name = h2
22:39:35,424 INFO [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 4.0.6.Final
22:39:35,426 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 48) JBAS015537: Activating WebServices Extension
22:39:35,471 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 27) JBAS014613: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("jdbc-driver" => "mysql")
]) - failure description: "JBAS010441: Failed to load module for driver [com.mysql.jdbc]"
22:39:35,487 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017502: Undertow 1.1.0.Final starting
22:39:35,501 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017502: Undertow 1.1.0.Final starting
22:39:35,507 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.0.21.Final
22:39:35,642 INFO [org.jboss.as.naming] (MSC service thread 1-1) JBAS011802: Starting Naming Service
22:39:35,643 INFO [org.jboss.as.mail.extension] (MSC service thread 1-3) JBAS015400: Bound mail session [java:jboss/mail/Default]
22:39:36,092 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 47) JBAS017527: Creating file handler for path /home/pioflor/Pobrane/wildfly-8.2.0.Final/welcome-content
22:39:36,232 INFO [org.wildfly.extension.undertow] (MSC service thread 1-3) JBAS017525: Started server default-server.
22:39:36,308 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) JBAS017531: Host default-host starting
22:39:36,504 INFO [org.wildfly.extension.undertow] (MSC service thread 1-2) JBAS017519: Undertow HTTP listener default listening on /127.0.0.1:8080
22:39:36,804 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) JBAS015012: Started FileSystemDeploymentService for directory /home/pioflor/Pobrane/wildfly-8.2.0.Final/standalone/deployments
22:39:36,834 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "jsf-managedBean-and-ejb.war" (runtime-name: "jsf-managedBean-and-ejb.war")
22:39:37,194 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS]
22:39:37,567 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.2.Final
22:39:38,060 INFO [org.jboss.as.jpa] (MSC service thread 1-1) JBAS011401: Read persistence.xml for jsf-managedBean-and-ejb
22:39:38,247 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) JBAS011409: Starting Persistence Unit (phase 1 of 2) Service 'jsf-managedBean-and-ejb.war#jsf-managedBean-and-ejb'
22:39:38,260 INFO [org.hibernate.jpa.internal.util.LogHelper] (ServerService Thread Pool -- 50) HHH000204: Processing PersistenceUnitInfo [
        name: jsf-managedBean-and-ejb
        ...]
22:39:38,346 INFO [org.hibernate.Version] (ServerService Thread Pool -- 50) HHH000412: Hibernate Core {4.3.7.Final}
22:39:38,348 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000206: hibernate.properties not found
22:39:38,351 INFO [org.hibernate.cfg.Environment] (ServerService Thread Pool -- 50) HHH000021: Bytecode provider name : javassist
22:39:38,790 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016002: Processing weld deployment jsf-managedBean-and-ejb.war
22:39:38,890 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-2) HV000001: Hibernate Validator 5.1.3.Final
22:39:39,009 INFO [org.jboss.as.ejb3.deployment.processors.EjbJndiBindingsDeploymentUnitProcessor] (MSC service thread 1-2) JNDI bindings for session bean named CalculatorImpl in deployment unit deployment "jsf-managedBean-and-ejb.war" are as follows:

        java:global/jsf-managedBean-and-ejb/CalculatorImpl!org.superbiz.jsf.Calculator
        java:app/jsf-managedBean-and-ejb/CalculatorImpl!org.superbiz.jsf.Calculator
        java:module/CalculatorImpl!org.superbiz.jsf.Calculator
        java:jboss/exported/jsf-managedBean-and-ejb/CalculatorImpl!org.superbiz.jsf.Calculator
        java:global/jsf-managedBean-and-ejb/CalculatorImpl
        java:app/jsf-managedBean-and-ejb/CalculatorImpl
        java:module/CalculatorImpl

22:39:39,569 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016005: Starting Services for CDI deployment: jsf-managedBean-and-ejb.war
22:39:39,619 INFO [org.jboss.weld.Version] (MSC service thread 1-2) WELD-000900: 2.2.6 (Final)
22:39:39,682 INFO [org.jboss.weld.deployer] (MSC service thread 1-2) JBAS016008: Starting weld service for deployment jsf-managedBean-and-ejb.war
22:39:39,995 INFO [org.jboss.as.jpa] (ServerService Thread Pool -- 50) JBAS011409: Starting Persistence Unit (phase 2 of 2) Service 'jsf-managedBean-and-ejb.war#jsf-managedBean-and-ejb'
22:39:40,126 INFO [org.hibernate.annotations.common.Version] (ServerService Thread Pool -- 50) HCANN000001: Hibernate Commons Annotations {4.0.4.Final}
22:39:40,801 INFO [org.hibernate.dialect.Dialect] (ServerService Thread Pool -- 50) HHH000400: Using dialect: org.hibernate.dialect.H2Dialect
22:39:40,813 WARN [org.hibernate.dialect.H2Dialect] (ServerService Thread Pool -- 50) HHH000431: Unable to determine H2 database version, certain features may not work
22:39:40,911 INFO [org.hibernate.hql.internal.ast.ASTQueryTranslatorFactory] (ServerService Thread Pool -- 50) HHH000397: Using ASTQueryTranslatorFactory
22:39:43,444 INFO [javax.enterprise.resource.webcontainer.jsf.config] (MSC service thread 1-4) Initializing Mojarra 2.2.8-jbossorg-1 20140822-1131 for context '/jsf-managedBean-and-ejb'
22:39:44,975 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) JBAS017534: Registered web context: /jsf-managedBean-and-ejb
22:39:44,993 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("data-source" => "newdatabase")
]) - failure description: {"JBAS014771: Services with missing/unavailable dependencies" => [
    "jboss.data-source.java:/newdatabase is missing [jboss.jdbc-driver.mysql]",
    "jboss.driver-demander.java:/newdatabase is missing [jboss.jdbc-driver.mysql]"
]}
22:39:45,001 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
    ("subsystem" => "datasources"),
    ("data-source" => "newdatabase")
]) - failure description: {
    "JBAS014771: Services with missing/unavailable dependencies" => [
        "jboss.data-source.java:/newdatabase is missing [jboss.jdbc-driver.mysql]",
        "jboss.driver-demander.java:/newdatabase is missing [jboss.jdbc-driver.mysql]"
    ],
    "JBAS014879: One or more services were unable to start due to one or more indirect dependencies not being available." => {
        "Services that were unable to start:" => [
            "jboss.data-source.reference-factory.newdatabase",
            "jboss.naming.context.java.newdatabase"
        ],
        "Services that may be the cause:" => ["jboss.jdbc-driver.mysql"]
    }
}
22:39:45,118 INFO [org.jboss.as.server] (ServerService Thread Pool -- 28) JBAS018559: Deployed "jsf-managedBean-and-ejb.war" (runtime-name : "jsf-managedBean-and-ejb.war")
22:39:45,123 INFO [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.jdbc-driver.mysql (missing) dependents: [service jboss.driver-demander.java:/newdatabase, service jboss.data-source.java:/newdatabase]

22:39:45,229 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management
22:39:45,229 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
22:39:45,230 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: WildFly 8.2.0.Final "Tweek" started (with errors) in 13269ms - Started 739 of 796 services (4 services failed or missing dependencies, 92 services are lazy, passive or on-demand)

[\code]

It seems that JBoss is still not connected to MySQL?

I found this website https://issues.jboss.org/browse/WFLY-3646

Does this mean that this is a bug in this version?
Actions

Go to original post