8 Replies Latest reply on Sep 21, 2016 2:39 AM by Arnab Samanta

    Could not create data source in wildfly Final9.0.2

    Arnab Samanta Newbie

      2016-09-08 04:39:39,260 INFO  [org.jboss.as.controller] (ServerService Thread Pool -- 77) WFLYCTL0183: Service status report

      WFLYCTL0184:    New missing/unsatisfied dependencies:

            service jboss.data-source.reference-factory.DSPostgres (missing) dependents: [service jboss.naming.context.java.jdbc._datasource]

       

       

      2016-09-08 04:39:47,891 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 77) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=DSPostgres' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.

      2016-09-08 04:39:47,895 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 77) WFLYCTL0013: Operation ("add") failed - address: ([

          ("subsystem" => "datasources"),

          ("data-source" => "DSPostgres")

      ]) - failure description: {"WFLYCTL0288: 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.java:/jdbc/_datasource"],

          "Services that may be the cause:" => [

              "jboss.http-upgrade-registry.default",

              "jboss.network.public",

              "jboss.network.unsecure",

              "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

          ]

      }}

        • 2. Re: Could not create data source in wildfly Final9.0.2
          Arnab Samanta Newbie

          Yes, I have install that. Even I could not deploy any application without any db connection. It is showing the following error:-

           

          2016-09-08 03:06:32,656 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 65) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "AUGENTAPP.ear")]) - failure description: {"WFLYCTL0288: 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.deployment.subunit.\"AUGENTAPP.ear\".\"App.war\".PARSE",

                  "jboss.deployment.unit.\"AUGENTAPP.ear\".PARSE"

              ],

              "Services that may be the cause:" => [

                  "jboss.http-upgrade-registry.default",

                  "jboss.network.public",

                  "jboss.network.unsecure",

                  "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

              ]

          }}

          • 3. Re: Could not create data source in wildfly Final9.0.2
            Wolfgang Mayer Master

            Is this driver also loaded? You should see an entry in your server.log like:

            WFLYJCA0018: Started Driver service with driver-name = postgresql

             

            For analyzing your issue it might also help if you post your server.log

            • 4. Re: Could not create data source in wildfly Final9.0.2
              Arnab Samanta Newbie

              Driver is loading there. I am attaching log file where server starting with error. Please look into it.

              I am running in Linux environment and domain mode:-

               

              2016-09-08 08:31:30,907 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final

              2016-09-08 08:31:31,222 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

              2016-09-08 08:31:31,350 INFO  [org.jboss.as] (MSC service thread 1-7) WFLYSRV0049: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) starting

              2016-09-08 08:31:31,352 DEBUG [org.jboss.as.config] (MSC service thread 1-7) Configured system properties:

                [Server:S_Server] =

                awt.toolkit = sun.awt.X11.XToolkit

                file.encoding = UTF-8

                file.encoding.pkg = sun.io

                file.separator = /

                java.awt.graphicsenv = sun.awt.X11GraphicsEnvironment

                java.awt.headless = true

                java.awt.printerjob = sun.print.PSPrinterJob

                java.class.path = /opt/wildfly/jboss-modules.jar

                java.class.version = 52.0

                java.endorsed.dirs = /usr/java/jdk1.8.0_45/jre/lib/endorsed

                java.ext.dirs = /usr/java/jdk1.8.0_45/jre/lib/ext:/usr/java/packages/lib/ext

                java.home = /usr/java/jdk1.8.0_45/jre

                java.io.tmpdir = /tmp

                java.library.path = /usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib

                java.net.preferIPv4Stack = true

                java.runtime.name = Java(TM) SE Runtime Environment

                java.runtime.version = 1.8.0_45-b14

                java.specification.name = Java Platform API Specification

                java.specification.vendor = Oracle Corporation

                java.specification.version = 1.8

                java.util.logging.manager = org.jboss.logmanager.LogManager

                java.vendor = Oracle Corporation

                java.vendor.url = http://java.oracle.com/

                java.vendor.url.bug = http://bugreport.sun.com/bugreport/

                java.version = 1.8.0_45

                java.vm.info = mixed mode

                java.vm.name = Java HotSpot(TM) 64-Bit Server VM

                java.vm.specification.name = Java Virtual Machine Specification

                java.vm.specification.vendor = Oracle Corporation

                java.vm.specification.version = 1.8

                java.vm.vendor = Oracle Corporation

                java.vm.version = 25.45-b02

                javax.management.builder.initial = org.jboss.as.jmx.PluggableMBeanServerBuilder

                javax.xml.datatype.DatatypeFactory = __redirected.__DatatypeFactory

                javax.xml.parsers.DocumentBuilderFactory = __redirected.__DocumentBuilderFactory

                javax.xml.parsers.SAXParserFactory = __redirected.__SAXParserFactory

                javax.xml.stream.XMLEventFactory = __redirected.__XMLEventFactory

                javax.xml.stream.XMLInputFactory = __redirected.__XMLInputFactory

                javax.xml.stream.XMLOutputFactory = __redirected.__XMLOutputFactory

                javax.xml.transform.TransformerFactory = __redirected.__TransformerFactory

                javax.xml.validation.SchemaFactory:http://www.w3.org/2001/XMLSchema = __redirected.__SchemaFactory

                javax.xml.xpath.XPathFactory:http://java.sun.com/jaxp/xpath/dom = __redirected.__XPathFactory

                jboss.domain.base.dir = /opt/wildfly/domain

                jboss.domain.config.dir = /opt/wildfly/domain/configuration

                jboss.home.dir = /opt/wildfly

                jboss.host.name = bigdatalite

                jboss.modules.dir = /opt/wildfly/modules

                jboss.modules.system.pkgs = org.jboss.byteman

                jboss.node.name = master:S_Server

                jboss.qualified.host.name = bigdatalite.localdomain

                jboss.server.base.dir = /opt/wildfly/domain/servers/S_Server

                jboss.server.config.dir = /opt/wildfly/domain/servers/S_Server/configuration

                jboss.server.data.dir = /opt/wildfly/domain/servers/S_Server/data

                jboss.server.deploy.dir = /opt/wildfly/domain/servers/S_Server/data/content

                jboss.server.log.dir = /opt/wildfly/domain/servers/S_Server/log

                jboss.server.name = S_Server

                jboss.server.persist.config = true

                jboss.server.temp.dir = /opt/wildfly/domain/servers/S_Server/tmp

                line.separator =

               

               

                logging.configuration = file:/opt/wildfly/domain/servers/S_Server/data/logging.properties

                module.path = /opt/wildfly/modules

                org.jboss.resolver.warning = true

                org.xml.sax.driver = __redirected.__XMLReaderFactory

                os.arch = amd64

                os.name = Linux

                os.version = 2.6.32-504.16.2.el6.x86_64

                path.separator = :

                sun.arch.data.model = 64

                sun.boot.class.path = /usr/java/jdk1.8.0_45/jre/lib/resources.jar:/usr/java/jdk1.8.0_45/jre/lib/rt.jar:/usr/java/jdk1.8.0_45/jre/lib/sunrsasign.jar:/usr/java/jdk1.8.0_45/jre/lib/jsse.jar:/usr/java/jdk1.8.0_45/jre/lib/jce.jar:/usr/java/jdk1.8.0_45/jre/lib/charsets.jar:/usr/java/jdk1.8.0_45/jre/lib/jfr.jar:/usr/java/jdk1.8.0_45/jre/classes

                sun.boot.library.path = /usr/java/jdk1.8.0_45/jre/lib/amd64

                sun.cpu.endian = little

                sun.cpu.isalist =

                sun.io.unicode.encoding = UnicodeLittle

                sun.java.command = /opt/wildfly/jboss-modules.jar -mp /opt/wildfly/modules org.jboss.as.server

                sun.java.launcher = SUN_STANDARD

                sun.jnu.encoding = UTF-8

                sun.management.compiler = HotSpot 64-Bit Tiered Compilers

                sun.os.patch.level = unknown

                user.country = US

                user.dir = /u01/iotservice/server/wildfly-9.0.2.Final

                user.home = /home/wildfly

                user.language = en

                user.name = wildfly

                user.timezone = US/Eastern

                xsl.template.home = /u01/eMPowerBizz/bpms-files-store/reports-files/mail-templates/

              2016-09-08 08:31:31,354 DEBUG [org.jboss.as.config] (MSC service thread 1-7) VM Arguments: -D[Server:S_Server] -Xms64m -Xmx256m -DCONFIG_BPMS_APP_PROP_FILE=/u01/eMPowerBizz/bpms-config/props/appConstants.properties -DCONFIG_BPMS_CACHE_PROP=/u01/eMPowerBizz/bpms-config/props/cacheConstants.properties -DCONFIG_BPMS_COMM_PROP_FILE=/u01/eMPowerBizz/bpms-config/props/commonConstants.properties -DCONFIG_VISIO_TARGET_PATH=/u01/eMPowerBizz/visiotarget -DCONFIG_VISIO_TRANSFORM_FILE=/u01/eMPowerBizz/visiotemplate/Template.xsl -DMONITOR_BY_CONNECTION_POOL=true -DTXN_MANAGER=org.hibernate.service.jta.platform.internal.JBossAppServerJtaPlatform -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Djboss.home.dir=/opt/wildfly -Djboss.modules.system.pkgs=org.jboss.byteman -Dxsl.template.home=/u01/eMPowerBizz/bpms-files-store/reports-files/mail-templates/ -Djboss.server.log.dir=/opt/wildfly/domain/servers/S_Server/log -Djboss.server.temp.dir=/opt/wildfly/domain/servers/S_Server/tmp -Djboss.server.data.dir=/opt/wildfly/domain/servers/S_Server/data -Dlogging.configuration=file:/opt/wildfly/domain/servers/S_Server/data/logging.properties

              2016-09-08 08:31:31,437 INFO  [org.xnio] (MSC service thread 1-4) XNIO version 3.3.1.Final

              2016-09-08 08:31:31,450 INFO  [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.3.1.Final

              2016-09-08 08:31:31,489 INFO  [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 4.0.9.Final

              2016-09-08 08:31:33,772 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 13) WFLYCTL0028: Attribute 'enabled' in the resource at address '/subsystem=datasources/data-source=ExampleDS' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.

              2016-09-08 08:31:33,776 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) WFLYCTL0028: Attribute 'job-repository-type' in the resource at address '/subsystem=batch' is deprecated, and may be removed in future version. See the attribute description in the output of the read-resource-description operation to learn more about the deprecation.

              2016-09-08 08:31:33,923 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("interface" => "public")]) - failure description: "WFLYCTL0149: No interface criteria was provided"

              2016-09-08 08:31:33,925 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("interface" => "unsecure")]) - failure description: "WFLYCTL0149: No interface criteria was provided"

              2016-09-08 08:31:33,951 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 36) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.

              2016-09-08 08:31:33,957 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 38) WFLYSEC0002: Activating Security Subsystem

              2016-09-08 08:31:33,972 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 34) WFLYWS0002: Activating WebServices Extension

              2016-09-08 08:31:33,991 INFO  [org.jboss.as.security] (MSC service thread 1-1) WFLYSEC0001: Current PicketBox version=4.9.2.Final

              2016-09-08 08:31:34,016 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 44) WFLYNAM0001: Activating Naming Subsystem

              2016-09-08 08:31:34,044 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 56) WFLYIO001: Worker 'default' has auto-configured to 12 core threads with 96 task threads based on your 6 available processors

              2016-09-08 08:31:34,046 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0003: Undertow 1.2.9.Final starting

              2016-09-08 08:31:34,047 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 35) WFLYUT0003: Undertow 1.2.9.Final starting

              2016-09-08 08:31:34,069 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 55) WFLYCLINF0001: Activating Infinispan subsystem.

              2016-09-08 08:31:34,089 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 54) WFLYIIOP0001: Activating IIOP Subsystem

              2016-09-08 08:31:34,092 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.5.Final)

              2016-09-08 08:31:34,129 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]

              2016-09-08 08:31:34,148 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service

              2016-09-08 08:31:34,148 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-6) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

              2016-09-08 08:31:34,166 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 59) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

              2016-09-08 08:31:34,170 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = h2

              2016-09-08 08:31:34,195 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 59) WFLYJCA0005: Deploying non-JDBC-compliant driver class org.postgresql.Driver (version 9.4)

              2016-09-08 08:31:34,196 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-2) WFLYJCA0018: Started Driver service with driver-name = postgres

              2016-09-08 08:31:34,312 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 35) WFLYUT0014: Creating file handler for path /opt/wildfly/welcome-content

              2016-09-08 08:31:34,390 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 59) WFLYJCA0004: Deploying JDBC-compliant driver class oracle.jdbc.OracleDriver (version 11.1)

              2016-09-08 08:31:34,392 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = oracle

              2016-09-08 08:31:34,491 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0012: Started server default-server.

              2016-09-08 08:31:34,544 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0018: Host default-host starting

              2016-09-08 08:31:35,121 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("socket-binding-group" => "full-sockets")]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.socket-binding-manager is missing [jboss.network.public]"]}

              2016-09-08 08:31:35,124 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("socket-binding-group" => "full-sockets"),

                  ("socket-binding" => "http")

              ]) - failure description: {"WFLYCTL0288: 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.binding.http"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,125 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("socket-binding-group" => "full-sockets"),

                  ("socket-binding" => "https")

              ]) - failure description: {"WFLYCTL0288: 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.binding.https"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,126 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("socket-binding-group" => "full-sockets"),

                  ("socket-binding" => "iiop")

              ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.binding.iiop is missing [jboss.network.unsecure]"]}

              2016-09-08 08:31:35,127 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("socket-binding-group" => "full-sockets"),

                  ("socket-binding" => "iiop-ssl")

              ]) - failure description: {"WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.binding.iiop-ssl is missing [jboss.network.unsecure]"]}

              2016-09-08 08:31:35,128 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("socket-binding-group" => "full-sockets"),

                  ("socket-binding" => "txn-recovery-environment")

              ]) - failure description: {"WFLYCTL0288: 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.binding.txn-recovery-environment"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,129 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("socket-binding-group" => "full-sockets"),

                  ("socket-binding" => "txn-status-manager")

              ]) - failure description: {"WFLYCTL0288: 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.binding.txn-status-manager"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,130 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("socket-binding-group" => "full-sockets"),

                  ("remote-destination-outbound-socket-binding" => "mail-smtp")

              ]) - failure description: {"WFLYCTL0288: 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.outbound-socket-binding.mail-smtp"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,132 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "mail"),

                  ("mail-session" => "default")

              ]) - failure description: {"WFLYCTL0288: 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.mail-session.default"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,133 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "ee"),

                  ("managed-scheduled-executor-service" => "default")

              ]) - failure description: {"WFLYCTL0288: 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.concurrent.ee.scheduledexecutor.default"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,139 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jca")]) - failure description: {"WFLYCTL0288: 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.connector.transactionintegration",

                      "jboss.rarepository"

                  ],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,141 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "ee"),

                  ("managed-thread-factory" => "default")

              ]) - failure description: {"WFLYCTL0288: 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.concurrent.ee.threadfactory.default"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,142 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "jca"),

                  ("cached-connection-manager" => "cached-connection-manager")

              ]) - failure description: {"WFLYCTL0288: 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.cached-connection-manager"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,143 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jpa")]) - failure description: {"WFLYCTL0288: 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.jpa"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,144 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "webservices")]) - failure description: {"WFLYCTL0288: 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.ws.config"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,148 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "ee"),

                  ("context-service" => "default")

              ]) - failure description: {"WFLYCTL0288: 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.concurrent.ee.context.service.default"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,150 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "ee"),

                  ("managed-executor-service" => "default")

              ]) - failure description: {"WFLYCTL0288: 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.concurrent.ee.executor.default"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,151 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "jsr77")]) - failure description: {"WFLYCTL0288: 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.jsr77.ejb"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,153 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "jca"),

                  ("bootstrap-context" => "default")

              ]) - failure description: {"WFLYCTL0288: 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.connector.bootstrapcontext.default"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,155 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "security"),

                  ("security-domain" => "other")

              ]) - failure description: {"WFLYCTL0288: 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.security.security-domain.other"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,156 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "security"),

                  ("security-domain" => "jboss-web-policy")

              ]) - failure description: {"WFLYCTL0288: 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.security.security-domain.jboss-web-policy"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,157 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "security"),

                  ("security-domain" => "jboss-ejb-policy")

              ]) - failure description: {"WFLYCTL0288: 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.security.security-domain.jboss-ejb-policy"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,158 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "transactions")]) - failure description: {"WFLYCTL0288: 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.concurrent.ee.tsp",

                      "jboss.naming.context.java.TransactionManager",

                      "jboss.naming.context.java.jboss.TransactionManager",

                      "jboss.naming.context.java.jboss.TransactionSynchronizationRegistry",

                      "jboss.naming.context.java.jboss.UserTransaction",

                      "jboss.txn.ArjunaRecoveryManager",

                      "jboss.txn.ArjunaTransactionManager",

                      "jboss.txn.TransactionManager",

                      "jboss.txn.TransactionSynchronizationRegistry",

                      "jboss.txn.UserTransaction"

                  ],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,159 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "messaging"),

                  ("hornetq-server" => "default")

              ]) - failure description: {

                  "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging.default is missing [jboss.http-upgrade-registry.default]"],

                  "WFLYCTL0288: 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.messaging.default.jms.manager"],

                      "Services that may be the cause:" => [

                          "jboss.http-upgrade-registry.default",

                          "jboss.network.public",

                          "jboss.network.unsecure",

                          "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                      ]

                  }

              }

              2016-09-08 08:31:35,160 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "ejb3")]) - failure description: {"WFLYCTL0288: 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.ejb.default-local-ejb-receiver-service",

                      "jboss.ejb.tx-recovery-service",

                      "jboss.ejb.utilities",

                      "jboss.ejb3.ejbClientContext.default",

                      "jboss.ejb3.localEjbReceiver.value"

                  ],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,161 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "datasources"),

                  ("data-source" => "ExampleDS")

              ]) - failure description: {"WFLYCTL0288: 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.java:jboss/datasources/ExampleDS"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,162 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([("subsystem" => "iiop-openjdk")]) - failure description: {"WFLYCTL0288: 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.iiop-openjdk.naming-service",

                      "jboss.iiop-openjdk.orb-service",

                      "jboss.iiop-openjdk.poa-service.irpoa",

                      "jboss.iiop-openjdk.poa-service.namingpoa",

                      "jboss.iiop-openjdk.poa-service.rootpoa"

                  ],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,163 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "ejb3"),

                  ("service" => "timer-service"),

                  ("file-data-store" => "default-file-store")

              ]) - failure description: {"WFLYCTL0288: 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.ejb3.timerService.timerPersistence.default-file-store"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,164 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "undertow"),

                  ("server" => "default-server"),

                  ("http-listener" => "default")

              ]) - failure description: {"WFLYCTL0288: 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.undertow.listener.default"],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,165 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "ejb3"),

                  ("service" => "remote")

              ]) - failure description: {

                  "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.ejb3.connector is missing [jboss.remoting.remotingConnectorInfoService.http-remoting-connector]"],

                  "WFLYCTL0288: 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.ejb.remote-transactions-repository"],

                      "Services that may be the cause:" => [

                          "jboss.http-upgrade-registry.default",

                          "jboss.network.public",

                          "jboss.network.unsecure",

                          "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                      ]

                  }

              }

              2016-09-08 08:31:35,168 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "datasources"),

                  ("data-source" => "ExampleDS")

              ]) - failure description: {"WFLYCTL0288: 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.java:jboss/datasources/ExampleDS",

                      "jboss.data-source.java:jboss/datasources/ExampleDS",

                      "jboss.data-source.reference-factory.ExampleDS",

                      "jboss.naming.context.java.jboss.datasources.ExampleDS"

                  ],

                  "Services that may be the cause:" => [

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector",

                      "jboss.http-upgrade-registry.default",

                      "jboss.network.public",

                      "jboss.network.unsecure",

                      "jboss.remoting.remotingConnectorInfoService.http-remoting-connector"

                  ]

              }}

              2016-09-08 08:31:35,209 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

              WFLYCTL0184:    New missing/unsatisfied dependencies:

                    service jboss.http-upgrade-registry.default (missing) dependents: [service jboss.messaging.default]

                    service jboss.network.public (missing) dependents: [service jboss.socket-binding-manager]

                    service jboss.network.unsecure (missing) dependents: [service jboss.binding.iiop-ssl, service jboss.binding.iiop]

                    service jboss.remoting.remotingConnectorInfoService.http-remoting-connector (missing) dependents: [service jboss.ejb3.connector]

               

               

              2016-09-08 08:31:35,373 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.2.Final (WildFly Core 1.0.2.Final) started (with errors) in 4903ms - Started 149 of 388 services (52 services failed or missing dependencies, 215 services are lazy, passive or on-demand)

              • 5. Re: Could not create data source in wildfly Final9.0.2
                Wolfgang Mayer Master

                Looks like a problem in your host.xml. Maybe you can post this as well.

                1 of 1 people found this helpful
                • 6. Re: Could not create data source in wildfly Final9.0.2
                  Arnab Samanta Newbie

                  I have attached all the configuration files. Please go through it and let me know is there any change required?

                  • 7. Re: Could not create data source in wildfly Final9.0.2
                    Wolfgang Mayer Master

                    I've found a few potential issues:

                    1. You should not use a bind address of 0.0.0.0
                    2. The servers S_Server and eMPowerBizz should also be placed into host.xml (and not host-master.xml)
                    3. The server eMPowerBizz has a port-offset of "151" which is just 1 above server server-two. This may produce conflicts.
                    4. If you name your driver as postgresql then you may skip the driver detection when configuring the datasource via the WildFly console since this name is default.
                    5. In which profile did you configure your datasource?
                    1 of 1 people found this helpful
                    • 8. Re: Could not create data source in wildfly Final9.0.2
                      Arnab Samanta Newbie

                      Thank you Wolfgang. It was problem with the setting in wildfly.conf file, where I have set  JBOSS_HOST_CONFIG=host-master.xml mistakenly. So  host-master.xml was working as host.xml. that was the problem.Now problem is solved.

                      But, I have a questions regarding your previous reply-

                      1. You should not use a bind address of 0.0.0.0

                                Q:   If I want to make it accessible from outside the machine how can I do that,because default bind address set to 127.0.0.1?