5 Replies Latest reply on Feb 21, 2018 5:31 AM by tomjenkinson

Failed to execute BlackTie quickstarts

ashuprabhune Feb 19, 2018 4:41 AM

Hi,

I am using jboss-eap-7.1 and blacktie-5.7.2.Final. I have performed following steps :-

1. unzip wildfly-blacktie-build-${VERSION}-bin.zip into ${WILDFLY_LOCATION}

2. copy blacktie-admin-services-ear-*.ear to dir ${WILDFLY_LOCATION}/standalone/deployments

3. Make changes as defined in:

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

4.Edit the setenv.[sh|bat] file as appropriate

I am starting jboss as follows

./standalone.sh -c standalone-full.xml -Djboss.bind.address=localhost -Djboss.bind.address.unsecure=localhost

I have attached the logs for jboss.

BUT WHEN I TRY EXECUTING EXAMPLES by running the script /root/quickstart-example/blacktie/xatmi/fooapp/run.sh

I get following errors

2018-02-19 12:06:35,880 [0x7f478cb8a780] ERROR (HybridConnectionImpl :106 ) - Connection failed: localhost, 61613

2018-02-19 12:06:35,897 [0x7f478cb8a780] ERROR (HybridConnectionImpl :109 ) - APR Error was: 111: Connection refused

2018-02-19 12:06:35,899 [0x7f478cb8a780] ERROR (HybridSocketSessionImpl :446 ) - Could not send frame

2018-02-19 12:06:35,899 [0x7f478cb8a780] ERROR (HybridSocketSessionImpl :450 ) - APR Error was: 20011: No socket was provided and one was required.

2018-02-19 12:06:35,900 [0x7f478cb8a780] ERROR (AtmiBrokerServer :1113) - Could not advertise service with command: tpadvertise,fooapp,.fooapp1,0,queue,5.7.2.Final,

2018-02-19 12:06:35,901 [0x7f478cb8a780] FATAL (AtmiBrokerServer :473 ) - advertise admin service failed

2018-02-19 12:06:38,879 [0x7f478cb8a780] FATAL (AtmiBrokerServer :254 ) - serverinit failed

What are the things I am missing or doing wrong? Where can I attach logs, if required to solve the problem?

JBOSS_logs.txt.zip 4.2 KB

1. Re: Failed to execute BlackTie quickstarts

tomjenkinson Feb 19, 2018 6:03 AM (in response to ashuprabhune)

I think the problem is that you need to start the server with standalone-blacktie.xml: quickstart/README at 21ac5530950486b959a0420323828292fe38205d · jbosstm/quickstart · GitHub
Actions
2. Re: Failed to execute BlackTie quickstarts

ashuprabhune Feb 19, 2018 6:19 AM (in response to tomjenkinson)

I tried using standalone-blacktie.xml and but then it gives following error:-

./standalone.sh -c standalone-blacktie.xml -Djboss.bind.address=localhost -Djboss.bind.address.unsecure=localhost
=========================================================================

JBoss Bootstrap Environment

JBOSS_HOME: /root/jboss-eap-7.1

JAVA: /usr/java/jdk1.8.0_161/bin/java

JAVA_OPTS: -server -verbose:gc -Xloggc:"/root/jboss-eap-7.1/standalone/log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -DOrbPortabilityEnvironmentBean.resolveService=NAME_SERVICE

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

16:46:49,427 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final-redhat-1
16:46:49,876 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
16:46:50,022 INFO [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) starting
16:46:51,220 INFO [org.jboss.as.controller] (Controller Boot Thread) OPVDX002: Failed to pretty print validation error: null
16:46:51,221 ERROR [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0055: Caught exception during boot: org.jboss.as.controller.persistence.ConfigurationPersistenceException: WFLYCTL0085: Failed to parse configuration
        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:143)
        at org.jboss.as.server.ServerService.boot(ServerService.java:387)
        at org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:370)
        at java.lang.Thread.run(Thread.java:748)
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module org.wildfly.extension.blacktie
        at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:154)
        at org.jboss.as.server.parsing.StandaloneXml$DefaultExtensionHandler.parseExtensions(StandaloneXml.java:131)
        at org.jboss.as.server.parsing.StandaloneXml_4.readServerElement(StandaloneXml_4.java:200)
        at org.jboss.as.server.parsing.StandaloneXml_4.readElement(StandaloneXml_4.java:123)
        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:104)
        at org.jboss.as.server.parsing.StandaloneXml.readElement(StandaloneXml.java:49)
        at org.jboss.staxmapper.XMLMapperImpl.processNested(XMLMapperImpl.java:122)
        at org.jboss.staxmapper.XMLMapperImpl.parseDocument(XMLMapperImpl.java:76)
        at org.jboss.as.controller.persistence.XmlConfigurationPersister.load(XmlConfigurationPersister.java:126)
        ... 3 more
Caused by: java.util.concurrent.ExecutionException: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module
        at java.util.concurrent.FutureTask.report(FutureTask.java:122)
        at java.util.concurrent.FutureTask.get(FutureTask.java:192)
        at org.jboss.as.controller.parsing.ExtensionXml.parseExtensions(ExtensionXml.java:146)
        ... 11 more
Caused by: javax.xml.stream.XMLStreamException: WFLYCTL0083: Failed to load module
        at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:195)
        at org.jboss.as.controller.parsing.ExtensionXml.access$000(ExtensionXml.java:68)
        at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:126)
        at org.jboss.as.controller.parsing.ExtensionXml$1.call(ExtensionXml.java:123)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)
        at org.jboss.threads.JBossThread.run(JBossThread.java:320)
Caused by: org.jboss.modules.ModuleNotFoundException: org.wildfly.extension.blacktie
        at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:285)
        at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:271)
        at org.jboss.as.controller.parsing.ExtensionXml.loadModule(ExtensionXml.java:177)
        ... 8 more

16:46:51,223 FATAL [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0056: Server boot has failed in an unrecoverable manner; exiting. See previous messages for details.
16:46:51,242 INFO [org.jboss.as] (MSC service thread 1-4) WFLYSRV0050: JBoss EAP 7.1.0.GA (WildFly Core 3.0.10.Final-redhat-1) stopped in 11ms
Actions
3. Re: Failed to execute BlackTie quickstarts

tomjenkinson Feb 19, 2018 9:56 AM (in response to ashuprabhune)

This is what I get:

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

JBoss Bootstrap Environment

JBOSS_HOME: C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1

JAVA: /cygdrive/c/Program Files/Java/jdk1.8.0_144/bin/java

JAVA_OPTS: -server -verbose:gc -Xloggc:"C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1\standalone\log/gc.log" -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Xms1303m -Xmx1303m -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true

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

14:52:39,378 INFO [org.jboss.modules] (main) JBoss Modules version 1.6.0.Final-redhat-1
14:52:39,844 INFO [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1
14:52:39,961 INFO [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: JBoss EAP 7.1.0.GA (WildFly Core 3.0.9.Final-redhat-1) starting
14:52:41,045 INFO [org.jboss.as.controller.management-deprecated] (Controller Boot Thread) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/core-service=management/management-interface=http-interface' 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.
14:52:41,078 INFO [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 14) WFLYCTL0028: Attribute 'security-realm' in the resource at address '/subsystem=undertow/server=default-server/https-listener=https' 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.
14:52:41,078 WARN [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 8) WFLYIIOP0111: SSL has not been configured but ssl-port property has been specified - the connection will use clear-text protocol
14:52:41,128 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)
14:52:41,161 INFO [org.xnio] (MSC service thread 1-5) XNIO version 3.5.4.Final-redhat-1
14:52:41,161 INFO [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.5.4.Final-redhat-1
14:52:41,210 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 62) WFLYTX0013: The node-identifier attribute on the /subsystem=transactions is set to the default value. This is a danger for environments running multiple servers. Please make sure the attribute value is unique.
14:52:41,210 INFO [org.jboss.as.jaxrs] (ServerService Thread Pool -- 45) WFLYRS0016: RESTEasy version 3.0.24.Final-redhat-1
14:52:41,211 INFO [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 44) WFLYIIOP0001: Activating IIOP Subsystem
14:52:41,211 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 43) WFLYCLINF0001: Activating Infinispan subsystem.
14:52:41,211 INFO [org.jboss.as.security] (ServerService Thread Pool -- 61) WFLYSEC0002: Activating Security Subsystem
14:52:41,211 INFO [org.wildfly.extension.blacktie] (ServerService Thread Pool -- 67) Starting Blacktie Susbsystem
14:52:41,211 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 54) WFLYNAM0001: Activating Naming Subsystem
14:52:41,228 INFO [org.wildfly.extension.io] (ServerService Thread Pool -- 42) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors
14:52:41,228 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 64) WFLYWS0002: Activating WebServices Extension
14:52:41,244 INFO [org.jboss.as.security] (MSC service thread 1-4) WFLYSEC0001: Current PicketBox version=5.0.2.Final-redhat-1
14:52:41,245 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 50) WFLYJSF0007: Activated the following JSF Implementations: [main]
14:52:41,278 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 38) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)
14:52:41,294 INFO [org.jboss.remoting] (MSC service thread 1-7) JBoss Remoting version 5.0.5.Final-redhat-1
14:52:41,295 INFO [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final-redhat-1)
14:52:41,295 INFO [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = h2
14:52:41,311 INFO [org.wildfly.extension.undertow] (MSC service thread 1-6) WFLYUT0003: Undertow 1.4.18.Final-redhat-2 starting
14:52:41,328 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]
14:52:41,328 INFO [org.jboss.as.naming] (MSC service thread 1-6) WFLYNAM0003: Starting Naming Service
14:52:41,428 INFO [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 128 (per class), which is derived from thread worker pool sizing.
14:52:41,428 INFO [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 32 (per class), which is derived from the number of CPUs on this host.
14:52:41,528 INFO [org.wildfly.extension.undertow] (ServerService Thread Pool -- 63) WFLYUT0014: Creating file handler for path 'C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']
14:52:41,545 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.
14:52:41,545 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0018: Host default-host starting
14:52:41,727 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080
14:52:41,728 WARN [org.jboss.as.domain.management.security] (MSC service thread 1-5) WFLYDM0111: Keystore C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost
14:52:41,745 INFO [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none
14:52:41,745 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-2) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1\standalone\deployments
14:52:41,778 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-2) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.
14:52:41,828 INFO [org.jboss.as.ejb3] (MSC service thread 1-8) WFLYEJB0493: EJB subsystem suspension complete
14:52:41,911 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-4) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.ParticipantApplication
14:52:41,911 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-4) RESTEASY002205: Adding provider class org.jboss.narayana.rest.integration.HeuristicMapper from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication
14:52:41,927 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-4) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.ParticipantResource from Application class org.wildfly.extension.rts.jaxrs.ParticipantApplication
14:52:41,928 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication
14:52:41,911 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-7) RESTEASY002225: Deploying javax.ws.rs.core.Application: class org.wildfly.extension.rts.jaxrs.CoordinatorApplication
14:52:41,928 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-1) RESTEASY002200: Adding class resource org.jboss.narayana.rest.integration.VolatileParticipantResource from Application class org.wildfly.extension.rts.jaxrs.VolatileParticipantApplication
14:52:41,928 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-7) RESTEASY002200: Adding class resource org.jboss.jbossts.star.service.Coordinator from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication
14:52:41,928 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-7) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.HttpResponseMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication
14:52:41,945 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-7) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TransactionStatusMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication
14:52:41,945 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-7) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.NotFoundMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication
14:52:41,945 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-5) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]
14:52:41,945 INFO [org.jboss.resteasy.resteasy_jaxrs.i18n] (MSC service thread 1-7) RESTEASY002205: Adding provider class org.jboss.jbossts.star.provider.TMUnavailableMapper from Application class org.wildfly.extension.rts.jaxrs.CoordinatorApplication
14:52:41,978 INFO [org.hibernate.validator.internal.util.Version] (MSC service thread 1-4) HV000001: Hibernate Validator 5.3.5.Final-redhat-2
14:52:42,028 INFO [org.jboss.resteasy.plugins.validation.i18n] (MSC service thread 1-4) RESTEASY008550: Unable to find CDI supporting ValidatorFactory. Using default ValidatorFactory
14:52:42,061 INFO [org.jboss.resteasy.plugins.validation.i18n] (MSC service thread 1-1) RESTEASY008550: Unable to find CDI supporting ValidatorFactory. Using default ValidatorFactory
14:52:42,061 INFO [org.jboss.resteasy.plugins.validation.i18n] (MSC service thread 1-7) RESTEASY008550: Unable to find CDI supporting ValidatorFactory. Using default ValidatorFactory
14:52:42,078 INFO [org.wildfly.iiop.openjdk] (MSC service thread 1-6) WFLYIIOP0009: CORBA ORB Service started
14:52:42,111 INFO [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0021: Registered web context: 'volatile-rest-at-participant' for server 'default-server'
14:52:42,111 INFO [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0021: Registered web context: 'rest-at-participant' for server 'default-server'
14:52:42,111 INFO [org.wildfly.extension.undertow] (MSC servicbe thread 1-7) WFLYUT0021: Registered web context: '/rest-at-coordinator' for server 'default-server'
14:52:42,111 WARN [org.wildfly.iiop.openjdk] (MSC service thread 1-6) WFLYIIOP0109: SSL socket is required by server but secure connections have not been configured
14:52:42,261 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=false,journalDirectory=C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1\standalone\data\activemq\journal,bindingsDirectory=C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1\standalone\data\activemq\bindings,largeMessagesDirectory=C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1\standalone\data\activemq\largemessages,pagingDirectory=C:\Users\still\Documents\jbosstm\eap-71\jboss-as\dist\target\jboss-eap-7.1\standalone\data\activemq\paging)
14:52:42,328 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221013: Using NIO Journal
14:52:42,328 INFO [org.wildfly.extension.undertow] (MSC service thread 1-5) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443
14:52:42,378 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE
14:52:42,393 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ
14:52:42,394 INFO [org.jboss.ws.common.management] (MSC service thread 1-5) JBWS022052: Starting JBossWS 5.1.9.Final-redhat-1 (Apache CXF 3.1.12.redhat-1)
14:52:42,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
14:52:42,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor
14:52:42,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-3) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
14:52:42,594 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor
14:52:42,694 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221007: Server is now live
14:52:42,694 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.5.008-redhat-1 [default, nodeID=898b63b9-1584-11e8-95ac-00ff595e8492]
14:52:42,711 INFO [org.wildfly.extension.blacktie] (MSC service thread 1-8) Starting StompConnect tcp://127.0.0.1:61613
14:52:42,711 INFO [org.codehaus.stomp.tcp.TcpTransportServer] (MSC service thread 1-8) Listening for connections at: tcp://127.0.0.1:61613
14:52:42,711 INFO [org.wildfly.extension.blacktie] (MSC service thread 1-8) Started StompConnect tcp://127.0.0.1:61613
14:52:42,711 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory
14:52:42,744 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: Deploying queue jms.queue.ExpiryQueue
14:52:42,761 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-8) WFLYJCA0007: Registered connection factory java:/JmsXA
14:52:42,777 INFO [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 69) AMQ221003: Deploying queue jms.queue.DLQ
14:52:42,777 INFO [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 71) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory
14:52:42,828 INFO [org.apache.activemq.artemis.ra] (MSC service thread 1-8) Resource adaptor started
14:52:42,828 INFO [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-8) IJ020002: Deployed: file://RaActivatoractivemq-ra
14:52:42,828 INFO [org.jboss.as.connector.deployment] (MSC service thread 1-5) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]
14:52:42,828 INFO [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory
14:52:42,878 INFO [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
14:52:42,878 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
14:52:42,878 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
14:52:42,878 INFO [org.jboss.as] (Controller Boot Thread) WFLYSRV0025: JBoss EAP 7.1.0.GA (WildFly Core 3.0.9.Final-redhat-1) started in 3866ms - Started 318 of 632 services (418 services are lazy, passive or on-demand)

Assuming you are in the bin folder, what do you get when you type:
$ ls ../modules/system/layers/base/org/wildfly/extension/blacktie/main/
module.xml wildfly-blacktie-5.7.2.Final.jar
1 of 1 people found this helpful
Actions
4. Re: Failed to execute BlackTie quickstarts

ashuprabhune Feb 21, 2018 4:42 AM (in response to tomjenkinson)
Hi tomjenkinson
I didn't have blacktie folder in $JBOSS_HOME/modules/system/layers/base/org/wildfly/extension
So I copied it from ~/blacktie-5.7.2.Final/wildfly/modules/system/layers/base/org/wildfly/extension/blacktie to $JBOSS_HOME/modules/system/layers/base/org/wildfly/extension
I was able to start JBOSS with ./standalone.sh -c standalone-blacktie.xml -Djboss.bind.address=localhost -Djboss.bind.address.unsecure=localhost
I got the following output after running the fooapp example

Quickstart: Running fooapp
Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/lib/tools.jar

BUILD SUCCESSFUL
Total time: 4 seconds
Checking for host: hj-fsbfsd9761.persistent.co.in or ip: 10.51.230.186 or loopback: 127.0.0.1
2018-02-21 10:24:57,280 [0x7f39e80ba780] INFO (AtmiBrokerServer        :938 ) - advertised service .fooapp1
2018-02-21 10:24:57,669 [0x7f39e80ba780] INFO (AtmiBrokerServer        :938 ) - advertised service FOOAPP
2018-02-21 10:24:57,669 [0x7f39e80ba780] INFO (AtmiBrokerServer        :243 ) - Server 1 Running
2018-02-21 10:24:57,670 [0x7f39e80ba780] INFO (AtmiBrokerServer        :645 ) - Server waiting for requests...
2018-02-21 10:24:58,034 [0x7ff366fd9780] INFO (AtmiBrokerServer        :938 ) - advertised service .fooapp2
2018-02-21 10:24:58,266 [0x7ff366fd9780] INFO (AtmiBrokerServer        :938 ) - advertised service FOOAPP
2018-02-21 10:24:58,266 [0x7ff366fd9780] INFO (AtmiBrokerServer        :243 ) - Server 2 Running
2018-02-21 10:24:58,268 [0x7ff366fd9780] INFO (AtmiBrokerServer        :645 ) - Server waiting for requests...
Unable to locate tools.jar. Expected to find it in /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.65-3.b17.el7.x86_64/lib/tools.jar

BUILD SUCCESSFUL
Total time: 1 second
2018-02-21 10:25:00,645 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:00,871 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:00,874 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:01,086 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:01,092 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:01,307 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:01,312 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:01,528 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:01,533 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:01,739 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:01,742 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:01,949 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:01,953 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:02,161 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:02,167 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:02,376 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:02,382 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:02,589 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
2018-02-21 10:25:02,595 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Calling tpcall with input: THIS IS YOUR CLIENT SPEAKING
2018-02-21 10:25:02,801 [0x7f8321b32780] INFO (AtmiBrokerLogc          :60 ) - Called tpcall with length: 15 output: BAR SAYS HELLO and status: 0 and tperrno: 0
Checking for host: hj-fsbfsd9761.persistent.co.in or ip: 10.51.230.186 or loopback: 127.0.0.1
Server shutdown successfully: fooapp with id: 1
waiting for fooapp:1 shutdown complete
fooapp:1 shutdown complete
Server shutdown successfully: fooapp with id: 2
waiting for fooapp:2 shutdown complete
fooapp:2 shutdown complete

I have attached the steps I required to execute the quick starts.
Thank You!

Running Blacktie Quick-starts.rtf 3.0 KB
Actions
5. Re: Failed to execute BlackTie quickstarts

tomjenkinson Feb 21, 2018 5:31 AM (in response to ashuprabhune)

Thanks Ashish - it all seems to be working now!
Actions

Go to original post