1 2 Previous Next 29 Replies Latest reply on Sep 9, 2015 6:15 AM by Tom Jenkinson

    Installing Blacktie with Wildfly

    Joice Joy Newbie

      I am installing Blacktie 5.2.2 Final with Wildfly 9.0.1

       

      I have performed the following steps:

      1. Unzip wildfly-9.0.1.Final.zip

      2. unzip wildfly-blacktie-build-5.2.2.Final-bin.zip in Wildfly install location. See logs below:

           sh-4.1$ unzip wildfly-blacktie-build-5.2.2.Final-bin.zip

           Archive:  wildfly-blacktie-build-5.2.2.Final-bin.zip

             inflating: docs/examples/configs/standalone-blacktie.xml

              creating: modules/system/layers/base/org/wildfly/extension/blacktie/

              creating: modules/system/layers/base/org/wildfly/extension/blacktie/main/

            extracting: modules/system/layers/base/org/wildfly/extension/blacktie/main/wildfly-blacktie-5.2.2.Final.jar

             inflating: modules/system/layers/base/org/wildfly/extension/blacktie/main/module.xml

       

      3. copy blacktie-admin-services-ear-5.2.2.Final.ear into WildFly/standalone/deployments/

      4. Manually make edits to standalone-blacktie.xml and application-roles.properties as mentioned in:

           narayana/initializeJBoss.xml at 5.2.2.Final · jbosstm/narayana · GitHub

      5. Run the WildFly Server using ./standalone.sh -c standalone-full.xml

       

       

      But the server does not start the blacktie service:

       

       

       

       

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

       

       

        JBoss Bootstrap Environment

       

       

        JBOSS_HOME: /fxtest/trep/wildfly/wildfly-9.0.1.Final

       

       

        JAVA: /fxtest/trep/java/jdk1.8.0_51/bin/java

       

       

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

       

       

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

       

       

      Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0

      07:35:52,490 INFO  [org.jboss.modules] (main) JBoss Modules version 1.4.3.Final

      07:35:52,892 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.6.Final

      07:35:53,007 INFO  [org.jboss.as] (MSC service thread 1-3) WFLYSRV0049: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) starting

      07:35:55,053 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 15) 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.

      07:35:55,055 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 21) 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.

      07:35:55,121 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment blacktie-admin-services-ear-5.2.2.Final.ear

      07:35:55,361 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 24) WFLYDR0001: Content added at location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content

      07:35:55,390 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

      07:35:55,422 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.3.1.Final

      07:35:55,438 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.3.1.Final

      07:35:55,482 INFO  [org.jboss.remoting] (MSC service thread 1-1) JBoss Remoting version 4.0.9.Final

      07:35:55,548 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 41) WFLYCLINF0001: Activating Infinispan subsystem.

      07:35:55,554 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 40) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors

      07:35:55,557 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 42) WFLYIIOP0001: Activating IIOP Subsystem

      07:35:55,602 INFO  [org.jboss.as.connector] (MSC service thread 1-1) WFLYJCA0009: Starting JCA Subsystem (IronJacamar 1.2.4.Final)

      07:35:55,615 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 48) WFLYJSF0007: Activated the following JSF Implementations: [main]

      07:35:55,652 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 36) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3)

      07:35:55,661 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 52) WFLYNAM0001: Activating Naming Subsystem

      07:35:55,670 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-3) WFLYJCA0018: Started Driver service with driver-name = h2

      07:35:55,827 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 59) WFLYSEC0002: Activating Security Subsystem

      07:35:55,829 INFO  [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=4.9.2.Final

      07:35:55,849 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 60) WFLYTX0013: Node identifier property is set to the default value. Please make sure it is unique.

      07:35:55,849 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 62) WFLYWS0002: Activating WebServices Extension

      07:35:55,998 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0003: Undertow 1.2.9.Final starting

      07:35:56,034 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.2.9.Final starting

      07:35:56,095 INFO  [org.jboss.as.naming] (MSC service thread 1-2) WFLYNAM0003: Starting Naming Service

      07:35:56,119 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-2) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

      07:35:56,352 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 61) WFLYUT0014: Creating file handler for path /fxtest/trep/wildfly/wildfly-9.0.1.Final/welcome-content

      07:35:56,417 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.

      07:35:56,437 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0018: Host default-host starting

      07:35:56,589 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on /127.0.0.1:8080

      07:35:56,945 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-3) WFLYIIOP0009: CORBA ORB Service started

      07:35:56,969 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

      07:35:57,030 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-3) WFLYDS0013: Started FileSystemDeploymentService for directory /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/deployments

      07:35:57,059 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear")

      07:35:57,187 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221000: live server is starting with configuration HornetQ Configuration (clustered=false,backup=false,sharedStore=true,journalDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingjournal,bindingsDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingbindings,largeMessagesDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messaginglargemessages,pagingDirectory=/fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/messagingpaging)

      07:35:57,193 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221006: Waiting to obtain live lock

      07:35:57,287 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221012: Using AIO Journal

      07:35:57,387 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support CORE

      07:35:57,414 INFO  [org.jboss.ws.common.management] (MSC service thread 1-4) JBWS022052: Starting JBoss Web Services - Stack CXF Server 5.0.0.Final

      07:35:57,439 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support AMQP

      07:35:57,443 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221043: Adding protocol support STOMP

      07:35:57,502 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221034: Waiting to obtain live lock

      07:35:57,504 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221035: Live Server Obtained live lock

      07:35:58,108 INFO  [org.jboss.messaging] (MSC service thread 1-3) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor acceptor

      07:35:58,112 INFO  [org.jboss.messaging] (MSC service thread 1-1) WFLYMSG0016: Registered HTTP upgrade for hornetq-remoting protocol handled by http-acceptor-throughput acceptor

      07:35:58,206 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221007: Server is now live

      07:35:58,207 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221001: HornetQ Server version 2.4.7.Final (2.4.7.Final, 124) [9d12c6a3-4666-11e5-8632-95a54ac84561]

      07:35:58,210 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 64) HQ221003: trying to deploy queue jms.queue.ExpiryQueue

      07:35:58,514 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 66) WFLYMSG0002: Bound messaging object to jndi name java:/ConnectionFactory

      07:35:58,519 INFO  [org.jboss.as.messaging] (ServerService Thread Pool -- 67) WFLYMSG0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

      07:35:58,519 INFO  [org.hornetq.core.server] (ServerService Thread Pool -- 65) HQ221003: trying to deploy queue jms.queue.DLQ

      07:35:58,623 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0007: Registered connection factory java:/JmsXA

      07:35:58,721 INFO  [org.hornetq.ra] (MSC service thread 1-4) HornetQ resource adaptor started

      07:35:58,721 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-4) IJ020002: Deployed: file://RaActivatorhornetq-ra

      07:35:58,733 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]

      07:35:58,733 INFO  [org.jboss.as.messaging] (MSC service thread 1-4) WFLYMSG0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

      07:35:58,762 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.

      07:35:58,762 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jaxb-impl.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.

      07:35:58,762 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry jsr173_1.0_api.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.

      07:35:58,763 WARN  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0059: Class Path entry activation.jar in /content/blacktie-admin-services-ear-5.2.2.Final.ear/lib/jaxb-xjc-2.0EA3.jar  does not point to a valid jar for a Class-Path reference.

      07:35:58,780 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0207: Starting subdeployment (runtime-name: "blacktie-admin-services-5.2.2.Final.jar")

      07:35:58,885 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-2) MSC000001: Failed to start service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear"

              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:163)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1948)

              at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1881)

              at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

              at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

              at java.lang.Thread.run(Thread.java:745)

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml

              at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:98)

              at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:156)

              ... 5 more

      Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml

              at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:95)

              ... 6 more

      Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]

      Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'

              at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:108)

              at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:69)

              at org.jboss.as.messaging.deployment.MessagingXmlParsingDeploymentUnitProcessor.deploy(MessagingXmlParsingDeploymentUnitProcessor.java:89)

              ... 6 more

       

       

      07:35:58,893 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "blacktie-admin-services-ear-5.2.2.Final.ear")]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.subunit.\"blacktie-admin-services-ear-5.2.2.Final.ear\".\"blacktie-admin-services-5.2.2.Final.jar\".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment \"blacktie-admin-services-5.2.2.Final.jar\" of deployment \"blacktie-admin-services-ear-5.2.2.Final.ear\"

          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml

          Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: WFLYMSG0055: Could not parse file /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/tmp/vfs/deployment/deployment865003eadac08a4f/blacktie-admin-services-5.2.2.Final.jar-9cb8aa19a9dae2ff/contents/META-INF/activemq-jms.xml

          Caused by: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[2,1]

      Message: Unexpected element '{urn:jboss:messaging-activemq-deployment:1.0}messaging-deployment'"}}

      07:35:58,980 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 37) WFLYSRV0010: Deployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name : "blacktie-admin-services-ear-5.2.2.Final.ear")

      07:35:58,982 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

      WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE: WFLYSRV0153: Failed to process phase PARSE of subdeployment "blacktie-admin-services-5.2.2.Final.jar" of deployment "blacktie-admin-services-ear-5.2.2.Final.ear"

       

       

      07:35:59,202 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

      07:35:59,202 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

      07:35:59,202 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 9.0.1.Final (WildFly Core 1.0.1.Final) started (with errors) in 7156ms - Started 247 of 423 services (2 services failed or missing dependencies, 222 services are lazy, passive or on-demand)

      07:35:59,243 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: blacktie-admin-services-5.2.2.Final.jar) in 9ms

      07:35:59,332 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0028: Stopped deployment blacktie-admin-services-ear-5.2.2.Final.ear (runtime-name: blacktie-admin-services-ear-5.2.2.Final.ear) in 98ms

      07:35:59,413 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 2) WFLYDR0002: Content removed from location /fxtest/trep/wildfly/wildfly-9.0.1.Final/standalone/data/content/6a/4973c6ad23d3978c57f955fd341a56f1bc550a/content

      07:35:59,414 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0009: Undeployed "blacktie-admin-services-ear-5.2.2.Final.ear" (runtime-name: "blacktie-admin-services-ear-5.2.2.Final.ear")

      07:35:59,414 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 2) WFLYCTL0183: Service status report

      WFLYCTL0186:   Services which failed to start:      service jboss.deployment.subunit."blacktie-admin-services-ear-5.2.2.Final.ear"."blacktie-admin-services-5.2.2.Final.jar".PARSE

       

       

       

      Please help suggest a solution.

        • 1. Re: Installing Blacktie with Wildfly
          Tom Jenkinson Master

          Hi Joy,

           

          I updated the Jira ([JBTM-2495] Installing Blacktie 5.2.2 with Wildfly 9.0.1.Final Fails: Docs needs to say use WFLY "master" (or appropriat…) but the issue is that the docs are wrong, we only integrate with WFLY master so please can you try to run this on WFLY 10 Beta 1 (http://wildfly.org/downloads/).

           

          Thanks,

          Tom

          • 2. Re: Installing Blacktie with Wildfly
            Amos Feng Apprentice

            Hi Joy,

             

            As Tom said that it should run with the lastest WFLY 10 and you should start with standalone-blacktie.xml. I'd commented on the JBTM-2495

             

            Thanks,

            Amos

            • 3. Re: Installing Blacktie with Wildfly
              Joice Joy Newbie

              Thanks for the help.

               

              This solved the issue.

              • 4. Re: Installing Blacktie with Wildfly
                Joice Joy Newbie

                I am trying to start the server application in fooapp QS but get the following error:

                 

                There is an unset environment variable within the configuration element/attribute: NameService=corbaloc::${jboss.bind.address}:3528/NameService

                There is an unset environment variable within the configuration element/attribute: iiop://${jboss.bind.address}:0

                There is an unset environment variable within the configuration element/attribute: ${jboss.bind.address}

                Could not invoke command: org.jboss.narayana.blacktie.btadmin.commands.Server

                java.lang.ClassNotFoundException: org.jboss.narayana.blacktie.btadmin.commands.Server

                        at java.net.URLClassLoader.findClass(URLClassLoader.java:381)

                        at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

                        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)

                        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

                        at java.lang.Class.forName0(Native Method)

                        at java.lang.Class.forName(Class.java:264)

                        at org.jboss.narayana.blacktie.btadmin.CommandHandler.loadCommand(CommandHandler.java:143)

                        at org.jboss.narayana.blacktie.btadmin.CommandHandler.handleCommand(CommandHandler.java:76)

                        at org.jboss.narayana.blacktie.btadmin.BTAdmin.main(BTAdmin.java:62)

                 

                 

                The same error appears when starting the Wildfly server:

                23:47:42,766 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.conf.XMLEnvHandler] (ServerService Thread Pool -- 74) There is an unset environment variable within the configuration element/attribute: NameService=corbaloc::${jboss.bind.address}:3528/NameService

                23:47:42,766 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.conf.XMLEnvHandler] (ServerService Thread Pool -- 74) There is an unset environment variable within the configuration element/attribute: iiop://${jboss.bind.address}:0

                23:47:42,767 ERROR [org.jboss.narayana.blacktie.jatmibroker.core.conf.XMLEnvHandler] (ServerService Thread Pool -- 74) There is an unset environment variable within the configuration element/attribute: ${jboss.bind.address}

                 

                 

                I have added the following line to standalone.conf as per the initializeJBoss.xml

                export JAVA_OPTS="$JAVA_OPTS -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE"

                 

                Any reason for this.

                 

                 

                • 5. Re: Installing Blacktie with Wildfly
                  Joice Joy Newbie

                  The issue was due to missing btconfig.xml file.

                   

                  Now I am facing another error:

                  sh-4.1$ btadmin startup

                  Checking for host: drdvrh36 or ip: 10.68.5.247

                  2015-08-21 07:06:41,194 [0x7f8c59e7e760] FATAL (AtmiBrokerServer         :473 ) - advertise admin service failed

                  2015-08-21 07:06:43,395 [0x7f8c59e7e760] FATAL (AtmiBrokerServer         :254 ) - serverinit failed

                   

                   

                  The server console prints the following:

                   

                  07:06:41,146 ERROR [org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService] (Thread-2 (ActiveMQ-client-global-threads-1032381849)) Could not deploy queue of .fooapp1: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to http-remoting://localhost:9990. The connection failed

                   

                  I have checked there is no localhost in btconfig.xml

                   

                  Is there another file where IP needs to be configured.

                  • 6. Re: Installing Blacktie with Wildfly
                    Michael Musgrove Master

                    I have successfully ran the fooapp quickstart using the attached shell script. The first half of it builds the distribution and the second half runs the example.

                     

                    Good luck

                    • 7. Re: Installing Blacktie with Wildfly
                      Amos Feng Apprentice

                      The issue happens when connecting to the wildfly admin management interface to deploy the queue. So you need to run the server as

                      bin/standalone.sh -c standalone-blacktie.xml -Djboss.bind.address=$JBOSSAS_IP_ADDR -Djboss.bind.address.unsecure=$JBOSSAS_IP_ADDR
                      

                      and the JBOSSAS_IP_ADDR should be localhost or your hostname

                       

                      Thanks Mike and it should be very helpful to run with his shell script.

                      • 8. Re: Installing Blacktie with Wildfly
                        Joice Joy Newbie

                        I have tried ./standalone.sh -c standalone-blacktie.xml -Djboss.bind.address=$JBOSSAS_IP_ADDR -Djboss.bind.address.unsecure=$JBOSSAS_IP_ADDR

                         

                        Still the same issue. Note I am running the Quickstart from the same machine as the Wildfly server. Is this a limitation. Is there a way to configure  activemq to use IP address instead of localhost.

                         

                        blacktie logs state this:

                         

                        blacktie.log:2015-08-22 10:59:53,958 [0x7f37d9bcd760] TRACE (HybridSocketSessionImpl  :326 ) - send set messagereplyto: localhost:12341:0

                        blacktie.log:2015-08-22 10:59:53,960 [0x7f37d9bcd760] TRACE (AtmiBrokerLogc           :84  ) - stomp_write header messagereplyto:localhost:12341:0

                        • 9. Re: Installing Blacktie with Wildfly
                          Joice Joy Newbie

                          I wasnt able to to run the script as I am getting Git errors:

                          < HTTP/1.1 200 OK

                          < Server: GitHub Babel 2.0

                          < Content-Type: application/x-git-upload-pack-result

                          < Transfer-Encoding: chunked

                          < Expires: Fri, 01 Jan 1980 00:00:00 GMT

                          < Pragma: no-cache

                          < Cache-Control: no-cache, max-age=0, must-revalidate

                          < Vary: Accept-Encoding

                          <

                          * Done waiting for 100-continue

                          * transfer closed with outstanding read data remaining

                          * Closing connection #0

                          error: RPC failed; result=18, HTTP code = 200

                           

                          Will try later.

                           

                           

                          I have now tried with the following

                          ./standalone.sh -c standalone-blacktie.xml -Djboss.bind.address=${JBOSSAS_IP_ADDR} -Djboss.bind.address.unsecure=${JBOSSAS_IP_ADDR} -b=${JBOSSAS_IP_ADDR} -bmanagement=${JBOSSAS_IP_ADDR}

                           

                          Now the localhost error is not coming. But I get the following error:

                           

                           

                          03:59:53,979 ERROR [org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService] (Thread-0 (ActiveMQ-client-global-threads-1140963822)) Could not deploy queue of FOOAPP: java.lang.RuntimeException: "WFLYCTL0212: Duplicate resource [

                              (\"subsystem\" => \"messaging-activemq\"),

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

                              (\"jms-queue\" => \"BTR_FOOAPP\")

                          ]"

                                  at org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService.applyUpdate(BlacktieStompAdministrationService.java:100)

                                  at org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService.deployQueue(BlacktieStompAdministrationService.java:294)

                                  at org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService.tpservice(BlacktieStompAdministrationService.java:415)

                                  at org.jboss.narayana.blacktie.jatmibroker.xatmi.BlackTieService.processMessage(BlackTieService.java:182)

                                  at org.jboss.narayana.blacktie.jatmibroker.xatmi.mdb.MDBBlacktieService.onMessage(MDBBlacktieService.java:66)

                                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                                  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

                                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                                  at java.lang.reflect.Method.invoke(Method.java:497)

                                  at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)

                                  at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82)

                                  at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93)

                                  at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437)

                                  at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:73)

                                  at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)

                                  at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInNoTx(CMTTxInterceptor.java:263)

                                  at org.jboss.as.ejb3.tx.CMTTxInterceptor.never(CMTTxInterceptor.java:299)

                                  at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:235)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:53)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.as.ejb3.component.messagedriven.MessageDrivenComponentDescription$5$1.processInvocation(MessageDrivenComponentDescription.java:213)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)

                                  at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636)

                                  at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356)

                                  at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)

                                  at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195)

                                  at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185)

                                  at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340)

                                  at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61)

                                  at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73)

                                  at org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService$$$view2.onMessage(Unknown Source)

                                  at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

                                  at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

                                  at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

                                  at java.lang.reflect.Method.invoke(Method.java:497)

                                  at org.jboss.as.ejb3.inflow.MessageEndpointInvocationHandler.doInvoke(MessageEndpointInvocationHandler.java:139)

                                  at org.jboss.as.ejb3.inflow.AbstractInvocationHandler.invoke(AbstractInvocationHandler.java:73)

                                  at org.jboss.narayana.blacktie.administration.BlacktieStompAdministrationService$$$endpoint2.onMessage(Unknown Source)

                                  at org.apache.activemq.artemis.ra.inflow.ActiveMQMessageHandler.onMessage(ActiveMQMessageHandler.java:332)

                                  at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.callOnMessage(ClientConsumerImpl.java:1089)

                                  at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl.access$400(ClientConsumerImpl.java:47)

                                  at org.apache.activemq.artemis.core.client.impl.ClientConsumerImpl$Runner.run(ClientConsumerImpl.java:1224)

                                  at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)

                                  at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

                                  at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

                                  at java.lang.Thread.run(Thread.java:745)

                           

                           

                          The server thread prints this:

                          sh-4.1$ btadmin startup

                                  Checking for host: drdvrh36 or ip: 10.68.5.247

                          2015-08-24 03:59:53,357 [0x7f0624500760] INFO  (AtmiBrokerServer         :938 ) - advertised service .fooapp1

                          2015-08-24 03:59:54,032 [0x7f0624500760] ERROR (AtmiBrokerServer         :1150) - Service returned with error:

                          2015-08-24 03:59:54,035 [0x7f0624500760] INFO  (AtmiBrokerServer         :243 ) - Server 1 Running

                          2015-08-24 03:59:54,281 [0x7f0624500760] INFO  (AtmiBrokerServer         :938 ) - advertised service FOOAPP

                          2015-08-24 03:59:54,282 [0x7f0624500760] INFO  (AtmiBrokerServer         :645 ) - Server waiting for requests...

                          2015-08-24 03:59:54,612 [0x7f5db3e5d760] INFO  (AtmiBrokerServer         :938 ) - advertised service .fooapp2

                          2015-08-24 03:59:54,893 [0x7f5db3e5d760] INFO  (AtmiBrokerServer         :938 ) - advertised service FOOAPP

                          2015-08-24 03:59:54,893 [0x7f5db3e5d760] INFO  (AtmiBrokerServer         :243 ) - Server 2 Running

                          2015-08-24 03:59:54,893 [0x7f5db3e5d760] INFO  (AtmiBrokerServer         :645 ) - Server waiting for requests...

                          • 10. Re: Installing Blacktie with Wildfly
                            Tom Jenkinson Master

                            Please can you check whether you already have a BTR_FOOAPP in your standalone.xml from a previous run? That being said, the "btadmin startup" looks successful, does ./client work while the server is started?

                             

                            To run from different machines you can set JBOSSAS_IP_ADDR in the environment of the BlackTie server/clients.

                            • 11. Re: Installing Blacktie with Wildfly
                              Joice Joy Newbie

                              I do have BTR_FOOAPP in the standalone-blacktie.xml

                               

                                              <jms-queue name="ExpiryQueue" entries="java:/jms/queue/ExpiryQueue"/>

                                              <jms-queue name="DLQ" entries="java:/jms/queue/DLQ"/>

                                              <jms-queue name="BTR_TestOne" entries="queue/BTR_TestOne java:/jms/queue/BTR_TestOne"/>

                                              <jms-queue name="BTR_TestTwo" entries="queue/BTR_TestTwo java:/jms/queue/BTR_TestTwo"/>

                                              <jms-queue name="BTC_ConvService" entries="queue/BTC_ConvService java:/jms/queue/BTC_ConvService"/>

                                              <jms-queue name="BTR_JAVA_Converse" entries="queue/BTR_JAVA_Converse java:/jms/queue/BTR_JAVA_Converse"/>

                                              <jms-queue name="BTR_.fooapp1" entries="/queue/BTR_.fooapp1"/>

                                              <jms-queue name="BTR_FOOAPP" entries="/queue/BTR_FOOAPP"/>

                                              <jms-queue name="BTR_.fooapp2" entries="/queue/BTR_.fooapp2"/>

                                              <jms-topic name="BTR_JAVA_Topic" entries="topic/BTR_JAVA_Topic java:/jms/topic/BTR_JAVA_Topic"/>

                               

                               

                              Also the client runs successfully but the btadmin shutdown fails when I do ./run.sh

                              Checking for host: drdvrh36 or ip: 10.68.5.247

                              Could not invoke the command: null

                              java.lang.reflect.UndeclaredThrowableException

                                      at com.sun.proxy.$Proxy0.shutdown(Unknown Source)

                                      at org.jboss.narayana.blacktie.btadmin.commands.Shutdown.invoke(Shutdown.java:123)

                                      at org.jboss.narayana.blacktie.btadmin.CommandHandler.handleCommand(CommandHandler.java:117)

                                      at org.jboss.narayana.blacktie.btadmin.BTAdmin.main(BTAdmin.java:62)

                              Caused by: org.jboss.narayana.blacktie.jatmibroker.xatmi.ResponseException: tperrno: 10 reason: Got an error back from the remote service

                                      at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.receive(ConnectionImpl.java:547)

                                      at org.jboss.narayana.blacktie.jatmibroker.xatmi.impl.ConnectionImpl.tpcall(ConnectionImpl.java:183)

                                      at org.jboss.narayana.blacktie.btadmin.CommandHandler.invoke(CommandHandler.java:187)

                                      ... 4 more

                               

                               

                              When I run btadmin shutdown manually I get this:

                              Checking for host: drdvrh36 or ip: 10.68.5.247

                              Server could not be shutdown (may already be stopped)

                               

                               

                              On server side I got this:

                              05:58:54,808 INFO  [org.jboss.narayana.blacktie.administration.BlacktieAdminServiceXATMI] (Thread-4 (ActiveMQ-client-global-threads-766345414)) init PostConstruct

                              05:58:54,808 INFO  [org.jboss.narayana.blacktie.administration.core.AdministrationProxy] (Thread-4 (ActiveMQ-client-global-threads-766345414)) onConstruct load btconfig.xml

                              05:58:54,914 ERROR [org.apache.activemq.artemis.core.server] (Thread-8 (ActiveMQ-remoting-threads-ActiveMQServerImpl::serverUUID=cfbf901c-4703-11e5-905e-7138cae39df8-390279428-1576535102)) AMQ224018: Failed to create session: ActiveMQSecurityException[errorType=SECURITY_EXCEPTION message=AMQ119031: Unable to validate user: guest]

                                      at org.apache.activemq.artemis.core.security.impl.SecurityStoreImpl.authenticate(SecurityStoreImpl.java:146)

                                      at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.createSession(ActiveMQServerImpl.java:1056)

                                      at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handleCreateSession(ActiveMQPacketHandler.java:168)

                                      at org.apache.activemq.artemis.core.protocol.core.impl.ActiveMQPacketHandler.handlePacket(ActiveMQPacketHandler.java:80)

                                      at org.apache.activemq.artemis.core.protocol.core.impl.ChannelImpl.handlePacket(ChannelImpl.java:652)

                                      at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.doBufferReceived(RemotingConnectionImpl.java:402)

                                      at org.apache.activemq.artemis.core.protocol.core.impl.RemotingConnectionImpl.bufferReceived(RemotingConnectionImpl.java:379)

                                      at org.apache.activemq.artemis.core.remoting.server.impl.RemotingServiceImpl$DelegatingBufferHandler.bufferReceived(RemotingServiceImpl.java:694)

                                      at org.apache.activemq.artemis.core.remoting.impl.invm.InVMConnection$1.run(InVMConnection.java:185)

                                      at org.apache.activemq.artemis.utils.OrderedExecutorFactory$OrderedExecutor$1.run(OrderedExecutorFactory.java:105)

                                      at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)

                                      at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)

                                      at java.lang.Thread.run(Thread.java:745)

                              • 12. Re: Installing Blacktie with Wildfly
                                Tom Jenkinson Master

                                Hi Joice,

                                 

                                Sorry, I forgot to mention I tried this earlier and replicate the issue entirely with the duplicate queue but server started OK. What I realised is that a previous "btadmin shutdown" failed to shutdown server id 2 (the example runs with two servers). I managed to reset entirely (and avoid that SECURITY_EXCEPTION) with the following changes:

                                 

                                killall -9 java

                                killall -9 server (this was the rogue server that was running)

                                 

                                I also managed to work out the use with the SECURITY_EXCEPTION, I imagine you got to the same place as I did by:

                                 

                                wget https://raw.githubusercontent.com/jbosstm/narayana/5.2.2.Final/blacktie/scripts/hudson/initializeJBoss.xml

                                ant -f initializeJBoss.xml -DJBOSS_HOME=$JBOSS_HOME initializeJBoss

                                (then getting an error message about missing folder config/ but after reading the file realising that you can do that with ./add-user...)

                                The issue is the command in the comments is out of date (I fixed it now)

                                 

                                The commands are actually:

                                ./add-user.sh admin password1@

                                ./add-user.sh guest password1@ -a

                                ./add-user.sh dynsub password1@ -a

                                 

                                Hope that helps,

                                Tom

                                • 13. Re: Installing Blacktie with Wildfly
                                  Joice Joy Newbie

                                  Thanks Tom but the issue is still present.

                                   

                                  I never used password1@. Initially i changed it to password and ran btadmin startup which worked. Even though the actual password was password1@. It seemed to me that it used another file for password.

                                  But for btadmin shutdown this password failed. I also tried with password1@ but it still fails. Somehow my btconfig.xml entry is not being picked. Very odd behavior maybe I missed something.

                                   

                                   

                                  Also for the txfooapp, it says "You must have the following databases initialized with quickstart tables: ORCL and blacktie"

                                  Are there any blacktie specific tables to be initialized. Also is ORCL the default DB present in Oracle database.

                                  • 14. Re: Installing Blacktie with Wildfly
                                    Tom Jenkinson Master

                                    Joice Joy wrote:

                                     

                                    Also for the txfooapp, it says "You must have the following databases initialized with quickstart tables: ORCL and blacktie"

                                    Are there any blacktie specific tables to be initialized. Also is ORCL the default DB present in Oracle database.

                                    The table that is required is one of the sample tables optionally created with a new database on Oracle. Its called "emp". If you haven't got one of those already you should be able to create it with:

                                     

                                    CREATE TABLE DEPT (

                                    DEPTNO              NUMBER(2) NOT NULL,

                                    DNAME               VARCHAR2(14),

                                    LOC                 VARCHAR2(13),

                                    CONSTRAINT DEPT_PRIMARY_KEY PRIMARY KEY (DEPTNO));

                                     

                                    INSERT INTO DEPT VALUES (20,'RESEARCH','DALLAS');

                                     

                                    CREATE TABLE EMP (

                                    EMPNO               NUMBER(4) NOT NULL,

                                    ENAME               VARCHAR2(10),

                                    JOB                 VARCHAR2(9),

                                    MGR                 NUMBER(4) CONSTRAINT EMP_SELF_KEY REFERENCES EMP (EMPNO),

                                    HIREDATE            DATE,

                                    SAL                 NUMBER(7,2),

                                    COMM                NUMBER(7,2),

                                    DEPTNO              NUMBER(2) NOT NULL,

                                    CONSTRAINT EMP_FOREIGN_KEY FOREIGN KEY (DEPTNO) REFERENCES DEPT (DEPTNO),

                                    CONSTRAINT EMP_PRIMARY_KEY PRIMARY KEY (EMPNO));

                                    1 2 Previous Next