8 Replies Latest reply on Oct 5, 2017 6:33 AM by Hrvoje Djurdjevic

    Failed deployment of wmq.jmsra.ivt.ear

    Hrvoje Djurdjevic Newbie

      Hello,

       

       

      I tried to deploy wmq.jmsra.ivt.ear (installation verification test program for IBM MQ resource adapter) to jboss EAP 7.1 standalone application server, and got this error:

       

       

      2017-10-03 14:17:50,989 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location C:\Users\hradjh\EAP-7.1.0\standalone\data\content\22\4a4698974cdbdfcc6b0fffbc7d89e5a64c1e31\content

      2017-10-03 14:17:51,343 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0001: Content added at location C:\Users\hradjh\EAP-7.1.0\standalone\data\content\5e\56af85b9035756887d5fff0f59d4e859c7aaa8\content

      2017-10-03 14:17:51,560 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "wmq.jmsra.ivt.ear" (runtime-name: "wmq.jmsra.ivt.ear")

      2017-10-03 14:17:51,612 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2) WFLYSRV0027: Starting deployment of "wmq.jmsra.rar" (runtime-name: "wmq.jmsra.rar")

      2017-10-03 14:17:52,160 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0207: Starting subdeployment (runtime-name: "WMQ_IVT_MDB.jar")

      2017-10-03 14:17:52,160 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "WMQ_IVT.war")

      2017-10-03 14:18:16,934 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "wmq.jmsra.ivt.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.\"wmq.jmsra.ivt.ear\".\"WMQ_IVT.war\".PARSE",

              "jboss.deployment.subunit.\"wmq.jmsra.ivt.ear\".\"WMQ_IVT_MDB.jar\".PARSE",

              "jboss.deployment.unit.\"wmq.jmsra.ivt.ear\".PARSE"

          ],

          "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]

      }}

      2017-10-03 14:18:16,946 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 1) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "wmq.jmsra.rar")]) - 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.unit.\"wmq.jmsra.rar\".PARSE"],

          "Services that may be the cause:" => ["jboss.remoting.remotingConnectorInfoService.http-remoting-connector"]

      }}

      2017-10-03 14:18:18,965 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "wmq.jmsra.rar" (runtime-name : "wmq.jmsra.rar")

      2017-10-03 14:18:18,965 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0010: Deployed "wmq.jmsra.ivt.ear" (runtime-name : "wmq.jmsra.ivt.ear")

      2017-10-03 14:18:18,966 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report

      WFLYCTL0186:   Services which failed to start:      service org.wildfly.undertow.listener.default: Address already in use: bind /127.0.0.1:8080

       

      I tried both:

       

       

       

      Specification-Title: JavaEE Connector Architecture

      Specification-Version: 1.7

      Implementation-Title: IBM MQ Resource Adapter

      Implementation-Version: 9.0.0.0-p900-L160512.4

      Implementation-Vendor: IBM Corporation

       

       

      and

       

       

       

      Specification-Title: JavaEE Connector Architecture

      Specification-Version: 1.7

      Implementation-Title: WebSphere MQ Resource Adapter

      Implementation-Version: 8.0.0.4-p800-004-151017

      Implementation-Vendor: IBM Corporation

       

       

      and got the same error. I followed exactly the instructions given here:

      https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q129260_.htm

      I didn't do anything with http-remoting-connector, and I'm not sure am I supposed to do it, in order for this work, or what's the problem here?

        • 1. Re: Failed deployment of wmq.jmsra.ivt.ear
          Hrvoje Djurdjevic Newbie

          OK, I realized I already had an http listener for another service on the port 8080, so I stopped that service, but I still have some issues:

           

          2017-10-03 16:30:17,882 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "wmq.jmsra.ivt.ear")]) - failure description: {
              "WFLYCTL0412: Required services that are not installed:" => [
                  "jboss.naming.context.java.comp.\"wmq.jmsra.ivt\".WMQ_IVT_MDB.WMQ_IVT_MDB.env.JMS2CF",
                  "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTCF",
                  "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTQueue"
              ],
              "WFLYCTL0180: Services with missing/unavailable dependencies" => [
                  "jboss.naming.context.java.comp.\"wmq.jmsra.ivt\".WMQ_IVT_MDB.WMQ_IVT_MDB.env.jms.cf1 is missing [jboss.naming.context.java.comp.\"wmq.jmsra.ivt\".WMQ_IVT_MDB.WMQ_IVT_MDB.env.JMS2CF]",
                  "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.IVTQueue is missing [jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTQueue]",
                  "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.IVTCF is missing [jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTCF]"
              ]
          }
          2017-10-03 16:30:17,913 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 40) WFLYSRV0010: Deployed "wmq.jmsra.rar" (runtime-name : "wmq.jmsra.rar")
          2017-10-03 16:30:17,913 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 40) WFLYSRV0010: Deployed "wmq.jmsra.ivt.ear" (runtime-name : "wmq.jmsra.ivt.ear")
          2017-10-03 16:30:17,916 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
          WFLYCTL0184:    New missing/unsatisfied dependencies:
                service jboss.naming.context.java.comp."wmq.jmsra.ivt".WMQ_IVT_MDB.WMQ_IVT_MDB.env.JMS2CF (missing) dependents: [service jboss.naming.context.java.comp."wmq.jmsra.ivt".WMQ_IVT_MDB.WMQ_IVT_MDB.env.jms.cf1]
                service jboss.naming.context.java.module."wmq.jmsra.ivt".WMQ_IVT.env.jms.ivt.IVTCF (missing) dependents: [service jboss.naming.context.java.module."wmq.jmsra.ivt".WMQ_IVT.env.IVTCF]
                service jboss.naming.context.java.module."wmq.jmsra.ivt".WMQ_IVT.env.jms.ivt.IVTQueue (missing) dependents: [service jboss.naming.context.java.module."wmq.jmsra.ivt".WMQ_IVT.env.IVTQueue]

          2017-10-03 16:30:18,210 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server
          2017-10-03 16:30:18,213 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management
          2017-10-03 16:30:18,215 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990
          2017-10-03 16:30:18,215 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: JBoss EAP 7.1.0.Beta1 (WildFly Core 3.0.0.Beta26-redhat-1) started (with errors) in 13469ms - Started 657 of 896 services (17 services failed or missing dependencies, 435 services are lazy, passive or on-demand)
          2017-10-03 16:30:18,290 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0208: Stopped subdeployment (runtime-name: WMQ_IVT_MDB.jar) in 38ms
          2017-10-03 16:30:18,305 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0208: Stopped subdeployment (runtime-name: WMQ_IVT.war) in 54ms
          2017-10-03 16:30:18,310 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment wmq.jmsra.ivt.ear (runtime-name: wmq.jmsra.ivt.ear) in 58ms
          2017-10-03 16:30:18,374 INFO  [org.jboss.as.repository] (DeploymentScanner-threads - 1) WFLYDR0002: Content removed from location C:\Users\hradjh\EAP-7.1.0\standalone\data\content\22\4a4698974cdbdfcc6b0fffbc7d89e5a64c1e31\content
          2017-10-03 16:30:18,375 INFO  [org.jboss.as.server] (DeploymentScanner-threads - 1) WFLYSRV0009: Undeployed "wmq.jmsra.ivt.ear" (runtime-name: "wmq.jmsra.ivt.ear")
          2017-10-03 16:30:18,375 INFO  [org.jboss.as.controller] (DeploymentScanner-threads - 1) WFLYCTL0183: Service status report
          WFLYCTL0185:    Newly corrected services:
                service jboss.naming.context.java.comp."wmq.jmsra.ivt".WMQ_IVT_MDB.WMQ_IVT_MDB.env.JMS2CF (no longer required)
                service jboss.naming.context.java.module."wmq.jmsra.ivt".WMQ_IVT.env.jms.ivt.IVTCF (no longer required)
                service jboss.naming.context.java.module."wmq.jmsra.ivt".WMQ_IVT.env.jms.ivt.IVTQueue (no longer required)

          • 2. Re: Failed deployment of wmq.jmsra.ivt.ear
            Frank Langelage Master

            The most important message is

            WFLYCTL0186:   Services which failed to start: 

            service org.wildfly.undertow.listener.default: Address already in use: bind /127.0.0.1:8080

            Something else is occupying port 8080 on this host and therefore services using the http-listener are not started.

            1 of 1 people found this helpful
            • 3. Re: Failed deployment of wmq.jmsra.ivt.ear
              Frank Langelage Master

              Did you check that the adapter got deployed succesful?

              The 3 jndi entries are there (Use web-console, runtime, subsystems, JNDI View to check):

              - jndi-name="java:jboss/jms/ivt/IVTCF"

              - jndi-name="java:jboss/jms/ivt/JMS2CF"

              - jndi-name="java:jboss/jms/ivt/IVTQueue"

               

              How do you lookup those names inside your code?

              • 4. Re: Failed deployment of wmq.jmsra.ivt.ear
                Hrvoje Djurdjevic Newbie

                Hi Frank, thanks for answering my question.

                 

                Here is everything that I have in runtime, subsystems, JNDI View about wmq.jmsra.rar, the rest is about org.apache.activemq.artemis.jms.client:

                In Configuration: Subsystems  >  Subsystem: Resource Adapters I have:

                 

                rar.jpgivtcf.jpg

                jms2cf.jpgqueue.jpg

                 

                Resource adapter configuration is I guess a result of copying the wmq.jmsra.rar file into the directory <WildFly_Home>/standalone/deployments, while the other is a result of

                editing the configuration file <WildFly_Home>/standalone/configuration/standalone-full.xml before issuing standalone.bat -c standalone-full.xml, as

                suggested in IBM Knowledge Center . So, something from rar maybe got deployed, but I don't know if anything from ear did. Anyway, if I try http://localhost:8080/WMQ_IVT/ ,

                I get http error 404 - Not Found.

                • 5. Re: Failed deployment of wmq.jmsra.ivt.ear
                  Hrvoje Djurdjevic Newbie

                  The difference in comparison to the IBM cook book, which is for Wildfly V10 (while I am using JBoss EAP 7.1.0.Beta1 (WildFly Core 3.0.0.Beta26-redhat-1) - does that make a substantial difference?) is that I had:

                   

                   

                   

                          <subsystem xmlns="urn:jboss:domain:resource-adapters:5.0"/>

                   

                   

                  so I inserted it there like this:

                   

                   

                   

                          <subsystem xmlns="urn:jboss:domain:resource-adapters:5.0">

                              <resource-adapters>

                                  <resource-adapter id="wmq.jmsra">

                  . . .

                                  </resource-adapter>

                              </resource-adapters>

                          </subsystem>

                   

                   

                  while the IBM cook book mentions this:

                   

                   

                   

                  <subsystem xmlns="urn:jboss:domain:resource-adapters:4.0">

                   

                   

                  So I basically inserted v4.0 resource-adapters definition into a slot for v5.0, but the application server picked it up OK, as can be seen from the web-console.

                  And then, there was an issue of an occupied port. After I stopped that service, I just stopped the standalone server and restarted it with the same command,

                  standalone.bat -c standalone-full.xml, with both rar and ear being there in the directory <WildFly_Home>/standalone/deployments. Do I have to do something

                  else in order to correctly deploy it?

                  I don't know much about that code, it's IBM's code, but I guess it should be working with these JNDI entries.

                  • 6. Re: Failed deployment of wmq.jmsra.ivt.ear
                    Hrvoje Djurdjevic Newbie

                    OK, I realized that I shouldn't have posted the server log from the point where the first ERROR entry is written, because the INFO and WARNING lines that precede it, may be crucial:

                     

                    2017-10-03 16:30:05,201 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.0.Beta9-redhat-1

                    2017-10-03 16:30:05,731 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1-redhat-1

                    2017-10-03 16:30:05,917 INFO  [org.jboss.as] (MSC service thread 1-1) WFLYSRV0049: JBoss EAP 7.1.0.Beta1 (WildFly Core 3.0.0.Beta26-redhat-1) starting

                    2017-10-03 16:30:05,918 DEBUG [org.jboss.as.config] (MSC service thread 1-1) Configured system properties:

                    awt.toolkit = sun.awt.windows.WToolkit

                    file.encoding = Cp1250

                    file.encoding.pkg = sun.io

                    file.separator = \

                    java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment

                    java.awt.printerjob = sun.awt.windows.WPrinterJob

                    java.class.path = C:\Users\hradjh\EAP-7.1.0\jboss-modules.jar

                    java.class.version = 52.0

                    java.endorsed.dirs = C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\endorsed

                    java.ext.dirs = C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\ext;C:\Windows\Sun\Java\lib\ext

                    java.home = C:\Program Files (x86)\Java\jdk1.8.0_111\jre

                    java.io.tmpdir = C:\Users\hradjh\AppData\Local\Temp\

                    java.library.path = C:\Program Files (x86)\Java\jdk1.8.0_111\bin;C:\Windows\Sun\Java\bin;C:\Windows\system32;C:\Windows;C:\Program Files\mingw-w64\x86_64-6.2.0-posix-seh-rt_v5-rev1\mingw64\bin;C:\app\client\hradjh\product\12.1.0\client_1\bin;C:\ProgramData\Oracle\Java\javapath;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;C:\SQLLIB\BIN;C:\SQLLIB\FUNCTION;C:\SQLLIB\SAMPLES\REPL;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC;C:\Program Files\IBM\MQ\bin64;C:\Program Files\IBM\MQ\bin;C:\Program Files (x86)\ActivIdentity\ActivClient\;C:\Program Files\ActivIdentity\ActivClient\;C:\Program Files\TortoiseSVN\bin;C:\Program Files\mingw-w64\x86_64-6.2.0-posix-seh-rt_v5-rev1\mingw64\bin;C:\Program Files (x86)\IBM\WebSphere MQ\bin;C:\Program Files (x86)\Microsoft Visual Studio 12.0\VC\;C:\Program Files (x86)\IDM Computer Solutions\UltraEdit\;.

                    java.net.preferIPv4Stack = true

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

                    java.runtime.version = 1.8.0_111-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_111

                    java.vm.info = mixed mode

                    java.vm.name = Java HotSpot(TM) Client 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.111-b14

                    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.home.dir = C:\Users\hradjh\EAP-7.1.0

                    jboss.host.name = zgmag-514886

                    jboss.modules.dir = C:\Users\hradjh\EAP-7.1.0\modules

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

                    jboss.node.name = zgmag-514886

                    jboss.qualified.host.name = zgmag-514886

                    jboss.server.base.dir = C:\Users\hradjh\EAP-7.1.0\standalone

                    jboss.server.config.dir = C:\Users\hradjh\EAP-7.1.0\standalone\configuration

                    jboss.server.data.dir = C:\Users\hradjh\EAP-7.1.0\standalone\data

                    jboss.server.deploy.dir = C:\Users\hradjh\EAP-7.1.0\standalone\data\content

                    jboss.server.log.dir = C:\Users\hradjh\EAP-7.1.0\standalone\log

                    jboss.server.name = zgmag-514886

                    jboss.server.persist.config = true

                    jboss.server.temp.dir = C:\Users\hradjh\EAP-7.1.0\standalone\tmp

                    line.separator =

                     

                     

                    logging.configuration = file:C:\Users\hradjh\EAP-7.1.0\standalone\configuration/logging.properties

                    module.path = C:\Users\hradjh\EAP-7.1.0\modules

                    org.jboss.boot.log.file = C:\Users\hradjh\EAP-7.1.0\standalone\log\server.log

                    org.jboss.resolver.warning = true

                    org.xml.sax.driver = __redirected.__XMLReaderFactory

                    os.arch = x86

                    os.name = Windows 7

                    os.version = 6.1

                    path.separator = ;

                    program.name = standalone.bat

                    sun.arch.data.model = 32

                    sun.boot.class.path = C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\resources.jar;C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\rt.jar;C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\sunrsasign.jar;C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\jsse.jar;C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\jce.jar;C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\charsets.jar;C:\Program Files (x86)\Java\jdk1.8.0_111\jre\lib\jfr.jar;C:\Program Files (x86)\Java\jdk1.8.0_111\jre\classes

                    sun.boot.library.path = C:\Program Files (x86)\Java\jdk1.8.0_111\jre\bin

                    sun.cpu.endian = little

                    sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx pentium i486 i386 i86

                    sun.desktop = windows

                    sun.io.unicode.encoding = UnicodeLittle

                    sun.java.command = C:\Users\hradjh\EAP-7.1.0\jboss-modules.jar -mp C:\Users\hradjh\EAP-7.1.0\modules org.jboss.as.standalone -Djboss.home.dir=C:\Users\hradjh\EAP-7.1.0 -c standalone-full.xml

                    sun.java.launcher = SUN_STANDARD

                    sun.jnu.encoding = Cp1250

                    sun.management.compiler = HotSpot Client Compiler

                    sun.os.patch.level = Service Pack 1

                    sun.stderr.encoding = cp852

                    sun.stdout.encoding = cp852

                    user.country = US

                    user.country.format = HR

                    user.dir = C:\Users\hradjh\EAP-7.1.0\bin

                    user.home = C:\Users\hradjh

                    user.language = en

                    user.language.format = hr

                    user.name = hradjh

                    user.script =

                    user.timezone = Europe/Belgrade

                    user.variant =

                    2017-10-03 16:30:05,919 DEBUG [org.jboss.as.config] (MSC service thread 1-1) VM Arguments: -Dprogram.name=standalone.bat -Xms1G -Xmx1G -XX:MetaspaceSize=96M -XX:MaxMetaspaceSize=256m -Djava.net.preferIPv4Stack=true -Djboss.modules.system.pkgs=org.jboss.byteman -verbose:gc -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -Xloggc:C:\Users\hradjh\EAP-7.1.0\standalone\log\gc.log -XX:GCLogFileSize=3M -XX:-TraceClassUnloading -Dorg.jboss.boot.log.file=C:\Users\hradjh\EAP-7.1.0\standalone\log\server.log -Dlogging.configuration=file:C:\Users\hradjh\EAP-7.1.0\standalone\configuration/logging.properties

                    2017-10-03 16:30:08,032 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.

                    2017-10-03 16:30:08,084 INFO  [org.wildfly.security] (ServerService Thread Pool -- 2) ELY00001: WildFly Elytron version 1.1.0.Beta52-redhat-1

                    2017-10-03 16:30:08,102 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 32) 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.

                    2017-10-03 16:30:08,118 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment wmq.jmsra.ivt.ear

                    2017-10-03 16:30:08,121 INFO  [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) WFLYDS0015: Re-attempting failed deployment wmq.jmsra.rar

                    2017-10-03 16:30:08,361 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 12) WFLYDR0001: Content added at location C:\Users\hradjh\EAP-7.1.0\standalone\data\content\22\4a4698974cdbdfcc6b0fffbc7d89e5a64c1e31\content

                    2017-10-03 16:30:08,828 INFO  [org.jboss.as.repository] (ServerService Thread Pool -- 12) WFLYDR0001: Content added at location C:\Users\hradjh\EAP-7.1.0\standalone\data\content\5e\56af85b9035756887d5fff0f59d4e859c7aaa8\content

                    2017-10-03 16:30:08,841 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

                    2017-10-03 16:30:08,856 INFO  [org.xnio] (MSC service thread 1-1) XNIO version 3.5.0.Beta7-redhat-1

                    2017-10-03 16:30:08,866 INFO  [org.xnio.nio] (MSC service thread 1-1) XNIO NIO Implementation Version 3.5.0.Beta7-redhat-1

                    2017-10-03 16:30:08,927 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 66) WFLYWS0002: Activating WebServices Extension

                    2017-10-03 16:30:08,950 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 64) 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.

                    2017-10-03 16:30:08,967 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 55) WFLYNAM0001: Activating Naming Subsystem

                    2017-10-03 16:30:08,989 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 63) WFLYSEC0002: Activating Security Subsystem

                    2017-10-03 16:30:09,054 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 51) WFLYJSF0007: Activated the following JSF Implementations: [main]

                    2017-10-03 16:30:09,070 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 44) WFLYCLINF0001: Activating Infinispan subsystem.

                    2017-10-03 16:30:09,071 INFO  [org.jboss.as.connector] (MSC service thread 1-2) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.5.Final-redhat-1)

                    2017-10-03 16:30:09,076 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 46) WFLYRS0016: RESTEasy version 3.0.23.Final-redhat-1

                    2017-10-03 16:30:09,126 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 45) WFLYIIOP0001: Activating IIOP Subsystem

                    2017-10-03 16:30:09,132 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 43) WFLYIO001: Worker 'default' has auto-configured to 4 core threads with 32 task threads based on your 2 available processors

                    2017-10-03 16:30:09,148 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 39) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)

                    2017-10-03 16:30:09,187 INFO  [org.jboss.as.security] (MSC service thread 1-3) WFLYSEC0001: Current PicketBox version=5.0.2.Final-redhat-1

                    2017-10-03 16:30:09,296 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-3) WFLYUT0003: Undertow 1.4.16.Final-redhat-1 starting

                    2017-10-03 16:30:09,304 INFO  [org.jboss.as.naming] (MSC service thread 1-1) WFLYNAM0003: Starting Naming Service

                    2017-10-03 16:30:09,323 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0018: Started Driver service with driver-name = h2

                    2017-10-03 16:30:09,329 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-1) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

                    2017-10-03 16:30:09,363 INFO  [org.jboss.remoting] (MSC service thread 1-2) JBoss Remoting version 5.0.0.Beta25-redhat-1

                    2017-10-03 16:30:09,582 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0482: Strict pool mdb-strict-max-pool is using a max instance size of 8 (per class), which is derived from the number of CPUs on this host.

                    2017-10-03 16:30:09,583 INFO  [org.jboss.as.ejb3] (MSC service thread 1-3) WFLYEJB0481: Strict pool slsb-strict-max-pool is using a max instance size of 32 (per class), which is derived from thread worker pool sizing.

                    2017-10-03 16:30:09,699 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 65) WFLYUT0014: Creating file handler for path 'C:\Users\hradjh\EAP-7.1.0/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']

                    2017-10-03 16:30:09,743 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0012: Started server default-server.

                    2017-10-03 16:30:09,807 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080

                    2017-10-03 16:30:09,831 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting

                    2017-10-03 16:30:09,969 INFO  [org.jboss.as.patching] (MSC service thread 1-4) WFLYPAT0050: JBoss EAP cumulative patch ID is: base, one-off patches include: none

                    2017-10-03 16:30:10,037 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-3) WFLYDM0111: Keystore C:\Users\hradjh\EAP-7.1.0\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost

                    2017-10-03 16:30:10,038 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\hradjh\EAP-7.1.0\standalone\deployments

                    2017-10-03 16:30:10,047 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.

                    2017-10-03 16:30:10,048 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0027: Starting deployment of "wmq.jmsra.ivt.ear" (runtime-name: "wmq.jmsra.ivt.ear")

                    2017-10-03 16:30:10,051 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-3) WFLYSRV0027: Starting deployment of "wmq.jmsra.rar" (runtime-name: "wmq.jmsra.rar")

                    2017-10-03 16:30:10,177 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-3) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.6.Final-redhat-1

                    2017-10-03 16:30:10,254 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) WFLYEJB0493: EJB subsystem suspension complete

                    2017-10-03 16:30:10,476 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443

                    2017-10-03 16:30:10,617 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "WMQ_IVT.war")

                    2017-10-03 16:30:10,617 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0207: Starting subdeployment (runtime-name: "WMQ_IVT_MDB.jar")

                    2017-10-03 16:30:10,728 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-2) WFLYIIOP0009: CORBA ORB Service started

                    2017-10-03 16:30:10,781 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

                    2017-10-03 16:30:11,374 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\hradjh\EAP-7.1.0\standalone\data\activemq\journal,bindingsDirectory=C:\Users\hradjh\EAP-7.1.0\standalone\data\activemq\bindings,largeMessagesDirectory=C:\Users\hradjh\EAP-7.1.0\standalone\data\activemq\largemessages,pagingDirectory=C:\Users\hradjh\EAP-7.1.0\standalone\data\activemq\paging)

                    2017-10-03 16:30:11,509 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221013: Using NIO Journal

                    2017-10-03 16:30:12,001 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE

                    2017-10-03 16:30:12,008 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ

                    2017-10-03 16:30:12,388 INFO  [org.jboss.ws.common.management] (MSC service thread 1-1) JBWS022052: Starting JBossWS 5.1.8.Final-redhat-1 (Apache CXF 3.1.11.redhat-1)

                    2017-10-03 16:30:15,206 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

                    2017-10-03 16:30:15,206 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor

                    2017-10-03 16:30:15,206 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor

                    2017-10-03 16:30:15,208 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

                    2017-10-03 16:30:15,331 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221007: Server is now live

                    2017-10-03 16:30:15,331 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 68) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.5.002-redhat-1 [default, nodeID=5cdf1e5b-a847-11e7-bb29-38b920524153]

                    2017-10-03 16:30:15,497 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 68) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

                    2017-10-03 16:30:15,841 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0007: Registered connection factory java:/JmsXA

                    2017-10-03 16:30:15,891 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-2) IJ020001: Required license terms for file:/C:/Users/hradjh/EAP-7.1.0/standalone/tmp/vfs/temp/temp46c84f60eeeeb371/content-ef1e504b8f5b2f15/contents/

                    2017-10-03 16:30:15,999 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 70) AMQ221003: Deploying queue jms.queue.DLQ

                    2017-10-03 16:30:16,407 INFO  [org.apache.activemq.artemis.ra] (MSC service thread 1-1) Resource adaptor started

                    2017-10-03 16:30:16,407 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-1) IJ020002: Deployed: file://RaActivatoractivemq-ra

                    2017-10-03 16:30:16,442 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 71) AMQ221003: Deploying queue jms.queue.ExpiryQueue

                    2017-10-03 16:30:16,552 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 69) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory

                    2017-10-03 16:30:17,171 WARN  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-2) IJ020017: Invalid archive: file:/C:/Users/hradjh/EAP-7.1.0/standalone/tmp/vfs/temp/temp46c84f60eeeeb371/content-ef1e504b8f5b2f15/contents/

                    2017-10-03 16:30:17,251 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]

                    2017-10-03 16:30:17,248 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-3) IJ020001: Required license terms for file:/C:/Users/hradjh/EAP-7.1.0/standalone/tmp/vfs/temp/temp46c84f60eeeeb371/content-ef1e504b8f5b2f15/contents/

                    2017-10-03 16:30:17,251 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-4) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

                    2017-10-03 16:30:17,303 WARN  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0006: ActivationConfigProperty ConnectionFactoryLookup will be ignored since it is not allowed by resource adapter: activemq-ra

                    2017-10-03 16:30:17,303 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:jboss/jms/ivt/IVTCF

                    2017-10-03 16:30:17,303 WARN  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0006: ActivationConfigProperty DestinationLookup will be ignored since it is not allowed by resource adapter: activemq-ra

                    2017-10-03 16:30:17,306 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0007: Registered connection factory java:jboss/jms/ivt/JMS2CF

                    2017-10-03 16:30:17,389 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0006: Registered admin object at java:jboss/jms/ivt/IVTQueue

                    2017-10-03 16:30:17,392 WARN  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-3) IJ020017: Invalid archive: file:/C:/Users/hradjh/EAP-7.1.0/standalone/tmp/vfs/temp/temp46c84f60eeeeb371/content-ef1e504b8f5b2f15/contents/

                    2017-10-03 16:30:17,396 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-3) IJ020002: Deployed: file:/C:/Users/hradjh/EAP-7.1.0/standalone/tmp/vfs/temp/temp46c84f60eeeeb371/content-ef1e504b8f5b2f15/contents/

                    2017-10-03 16:30:17,401 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0002: Bound JCA ConnectionFactory [java:jboss/jms/ivt/IVTCF]

                    2017-10-03 16:30:17,401 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-3) WFLYJCA0002: Bound JCA AdminObject [java:jboss/jms/ivt/IVTQueue]

                    2017-10-03 16:30:17,401 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-4) WFLYJCA0002: Bound JCA ConnectionFactory [java:jboss/jms/ivt/JMS2CF]

                    2017-10-03 16:30:17,484 INFO  [org.jboss.as.ejb3] (MSC service thread 1-1) WFLYEJB0042: Started message driven bean 'WMQ_IVT_MDB' with 'activemq-ra.rar' resource adapter

                    2017-10-03 16:30:17,882 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("deploy") failed - address: ([("deployment" => "wmq.jmsra.ivt.ear")]) - failure description: {

                        "WFLYCTL0412: Required services that are not installed:" => [

                            "jboss.naming.context.java.comp.\"wmq.jmsra.ivt\".WMQ_IVT_MDB.WMQ_IVT_MDB.env.JMS2CF",

                            "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTCF",

                            "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTQueue"

                        ],

                        "WFLYCTL0180: Services with missing/unavailable dependencies" => [

                            "jboss.naming.context.java.comp.\"wmq.jmsra.ivt\".WMQ_IVT_MDB.WMQ_IVT_MDB.env.jms.cf1 is missing [jboss.naming.context.java.comp.\"wmq.jmsra.ivt\".WMQ_IVT_MDB.WMQ_IVT_MDB.env.JMS2CF]",

                            "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.IVTQueue is missing [jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTQueue]",

                            "jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.IVTCF is missing [jboss.naming.context.java.module.\"wmq.jmsra.ivt\".WMQ_IVT.env.jms.ivt.IVTCF]"

                        ]

                    }

                     

                     

                    Obviously the problem is that message driven bean 'WMQ_IVT_MDB' gets started with default activemq-ra.rar instead of with wmq.jmsra.rar resource adapter,

                    also, in C:\Users\hradjh\EAP-7.1.0\standalone\deployments, after server restart I have two new files: wmq.jmsra.ivt.ear.failed and wmq.jmsra.rar.deployed,

                    so I thought the problem might be in the order of deployment, so I repeated the deployment of wmq.jmsra.ivt.ear through web-console, after wmq.jmsra.rar was succesfully deployed,

                    but the result was the same. Any suggestions?

                    • 7. Re: Failed deployment of wmq.jmsra.ivt.ear
                      Hrvoje Djurdjevic Newbie

                      Basically, what I need to know is, is this an MQ problem (I am opening a PMR with IBM), or jboss problem, or my problem, because I did something wrong. If any of you guys knows that, please let me know.