5 Replies Latest reply on Mar 8, 2018 10:09 AM by Patrick Nodder

    Exception on startup when using Generic JMS RA and domain security

    Patrick Nodder Newbie

      Hello,

       

      I am using Wildfly 11 and have configured the generic JMS RA with Tibco EMS 8.3. I am using security-domain-and-application for the RA's security. The security domain is configured in the legacy security subsystem like so:

       

       

                      <security-domain name="TibcoEmsRealm" cache-type="default">

       

                          <authentication>

                              <login-module code="ConfiguredIdentity" flag="required">

                                  <module-option name="principal" value="xxxx"/>

                                  <module-option name="userName" value="xxxx"/>

                                  <module-option name="password" value="xxxx"/>

                              </login-module>

                          </authentication>

                      </security-domain>


      And the RA like so:

       

       

                      <resource-adapter id="generic-jms-ra">

       

                          <module slot="main" id="org.jboss.genericjms"/>

                          <transaction-support>LocalTransaction</transaction-support>

                          <connection-definitions>

                              <connection-definition class-name="org.jboss.resource.adapter.jms.JmsManagedConnectionFactory" jndi-name="java:/jms/TibcoEmsLocalTxFactory" enabled="true" use-java-context="true" pool-name="GenericJmsXA" use-ccm="true">

                                  <config-property name="ConnectionFactory">

                                      QueueConnectionFactory

                                  </config-property>

                                  <config-property name="SessionDefaultType">

                                      javax.jms.Queue

                                  </config-property>

                                  <config-property name="JndiParameters">

                                      java.naming.factory.initial=com.tibco.tibjms.naming.TibjmsInitialContextFactory;java.naming.provider.url=tcp:/xxxxx

                                  </config-property>

                                  <pool>

                                      <min-pool-size>0</min-pool-size>

                                      <max-pool-size>20</max-pool-size>

                                      <prefill>false</prefill>

                                      <use-strict-min>false</use-strict-min>

                                      <flush-strategy>FailingConnectionOnly</flush-strategy>

                                  </pool>

                                  <security>

                                      <security-domain-and-application>TibcoEmsRealm</security-domain-and-application>

                                  </security>

                              </connection-definition>

                          </connection-definitions>

                      </resource-adapter>



      However, sometimes when I start Wildfly I immediately get the following error (it doesn't happen on every startup):

       

       

      14:17:27,265 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]

       

      at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332)

      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)

      at org.jboss.threads.JBossThread.run(JBossThread.java:320)

      Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/C:/Users/PNodder/dev/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

      at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064)

      at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$WildFlyRaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)

      at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)

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

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

      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: java.lang.IllegalStateException

      at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)

      at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:635)

      at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1666)

      ... 7 more



      I'm thinking it may be related to the TibcoEmsRealm security config (the reference to getSubjectFactory()). Does anyone have any ideas how to resolve this? Is this RA security configuration correct (i.e. using a domain in the legacy security)?

       

       

      Environment:

       

      Wildfly-11.0.0.Final

      Java 8

      Windows 10 and Centos7

      IntellijJ IDEA

      Using the genericjms that is included in Wildfly i.e. at wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

       

       

       

      Any help would be much appreciated.

       

      Patrick

        • 1. Re: Exception on startup when using Generic JMS RA and domain security
          simkam Newbie

          Hi,

           

          can you please share full server.log? ideally with enabled TRACE logging for org.jboss.security and org.jboss.as.security (/subsystem=logging/logger=org.jboss.security:add(level=TRACE) and /subsystem=logging/logger=org.jboss.as.security:add(level=TRACE)) .

           

          Thanks

          • 2. Re: Exception on startup when using Generic JMS RA and domain security
            Nagaraju Chitimilla Newbie

            Even I have the same problem.

             

            Wildfly 11.0.0.Final

            Java 8

             

            Below is my configuration.

             

            <mdb>

                            <resource-adapter-ref resource-adapter-name="jms-ra.rar"/>

                            <bean-instance-pool-ref pool-name="mdb-strict-max-pool"/>

                        </mdb>

             

                    <subsystem xmlns="urn:jboss:domain:messaging-activemq:2.0">

                        <server name="default">

                            <security-setting name="#">

                                <role name="guest" send="true" consume="true" create-non-durable-queue="true" delete-non-durable-queue="true"/>

                            </security-setting>

                            <address-setting name="#" dead-letter-address="jms.queue.DLQ" expiry-address="jms.queue.ExpiryQueue" max-size-bytes="10485760" page-size-bytes="2097152" message-counter-history-day-limit="10"/>

                            <http-connector name="http-connector" socket-binding="http" endpoint="http-acceptor"/>

                            <http-connector name="http-connector-throughput" socket-binding="http" endpoint="http-acceptor-throughput">

                                <param name="batch-delay" value="50"/>

                            </http-connector>

                            <in-vm-connector name="in-vm" server-id="0">

                                <param name="buffer-pooling" value="false"/>

                            </in-vm-connector>

                            <http-acceptor name="http-acceptor" http-listener="default"/>

                            <http-acceptor name="http-acceptor-throughput" http-listener="default">

                                <param name="batch-delay" value="50"/>

                                <param name="direct-deliver" value="false"/>

                            </http-acceptor>

                            <in-vm-acceptor name="in-vm" server-id="0">

                                <param name="buffer-pooling" value="false"/>

                            </in-vm-acceptor>

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

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

                            <connection-factory name="InVmConnectionFactory" entries="java:/ConnectionFactory" connectors="in-vm"/>

                            <connection-factory name="RemoteConnectionFactory" entries="java:jboss/exported/jms/RemoteConnectionFactory" connectors="http-connector"/>

                            <pooled-connection-factory name="jms-ra" entries="java:/ActivemqJms java:jboss/DefaultJMSConnectionFactory" connectors="in-vm" transaction="xa"/>

                        </server>

                    </subsystem>

             

            <resource-adapter id="jms-ra.rar">

                                <!-- <archive> -->

                                    <!-- IdentityMinder.ear#jms-ra.rar -->

                                <!-- </archive> -->

            <module slot="main" id="org.jboss.genericjms"/>

                                <transaction-support>XATransaction</transaction-support>

                                <connection-definitions>

                                    <connection-definition class-name="org.jboss.resource.adapter.jms.JmsManagedConnectionFactory" jndi-name="java:/ActivemqJms" enabled="true" use-java-context="true" pool-name="ActivemqJms" use-ccm="true">

                                        <config-property name="SessionDefaultType">

                                            javax.jms.Queue

                                        </config-property>

                                        <config-property name="ConnectionFactory">

                                            ConnectionFactory

                                        </config-property>

                                        <config-property name="JndiParameters">

                                            java.naming.security.principal=guest;java.naming.factory.initial=com.ca.jms.utils.ActiveMQJndiContextFactory;java.naming.provider.url=ssl://localhost:61616?socket.enabledProtocols=TLSv1.1,TLSv1.2

                                        </config-property>

                                        <xa-pool>

                                            <min-pool-size>1</min-pool-size>

                                            <max-pool-size>150</max-pool-size>

                                        </xa-pool>

                                        <security>

                                            <security-domain>ActivemqRealm</security-domain>

                                        </security>

                                        <timeout>

                                            <blocking-timeout-millis>32000</blocking-timeout-millis>

                                        </timeout>

                                    </connection-definition>

                                </connection-definitions>

                            </resource-adapter>

             

            10:36:10,843 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 68) MSC000001: Failed to start service jboss.ra.deployment."org.jboss.genericjms:main_jms-ra.rar": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.genericjms:main_jms-ra.rar": WFLYJCA0046: Failed to start RA deployment [jms-ra.rar]

                    at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332)

                    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)

                    at org.jboss.threads.JBossThread.run(JBossThread.java:320)

            Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/C:/Users/Administrator/Desktop/wildfly/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

                    at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064)

                    at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$WildFlyRaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)

                    at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)

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

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

                    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: java.lang.IllegalStateException

                    at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)

                    at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:635)

                    at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1666)

                    ... 7 more

            • 3. Re: Exception on startup when using Generic JMS RA and domain security
              Patrick Nodder Newbie

              Please find the log up to the point of failure.

               

              2018-03-07 09:48:58,544 INFO  [org.jboss.modules] (main) JBoss Modules version 1.6.2.Final

              2018-03-07 09:49:02,091 INFO  [org.jboss.msc] (main) JBoss MSC version 1.2.7.SP1

              2018-03-07 09:49:02,231 INFO  [org.jboss.as] (MSC service thread 1-8) WFLYSRV0049: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) starting

              2018-03-07 09:49:09,534 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.

              2018-03-07 09:49:09,564 INFO  [org.jboss.as.controller.management-deprecated] (ServerService Thread Pool -- 11) 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.

              2018-03-07 09:49:09,564 INFO  [org.wildfly.security] (ServerService Thread Pool -- 32) ELY00001: WildFly Elytron version 1.1.6.Final

              2018-03-07 09:49:10,089 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0039: Creating http management service using socket-binding (management-http)

              2018-03-07 09:49:10,111 INFO  [org.xnio] (MSC service thread 1-5) XNIO version 3.5.4.Final

              2018-03-07 09:49:10,118 INFO  [org.xnio.nio] (MSC service thread 1-5) XNIO NIO Implementation Version 3.5.4.Final

              2018-03-07 09:49:10,162 WARN  [org.jboss.as.txn] (ServerService Thread Pool -- 70) 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.

              2018-03-07 09:49:10,164 INFO  [org.wildfly.iiop.openjdk] (ServerService Thread Pool -- 49) WFLYIIOP0001: Activating IIOP Subsystem

              2018-03-07 09:49:10,175 INFO  [org.jboss.as.clustering.jgroups] (ServerService Thread Pool -- 53) WFLYCLJG0001: Activating JGroups subsystem. JGroups version 3.6.13

              2018-03-07 09:49:10,176 INFO  [org.jboss.as.naming] (ServerService Thread Pool -- 61) WFLYNAM0001: Activating Naming Subsystem

              2018-03-07 09:49:10,177 INFO  [org.jboss.as.jsf] (ServerService Thread Pool -- 56) WFLYJSF0007: Activated the following JSF Implementations: [main]

              2018-03-07 09:49:10,184 INFO  [org.jboss.as.security] (ServerService Thread Pool -- 68) WFLYSEC0002: Activating Security Subsystem

              2018-03-07 09:49:10,184 INFO  [org.jboss.as.jaxrs] (ServerService Thread Pool -- 50) WFLYRS0016: RESTEasy version 3.0.24.Final

              2018-03-07 09:49:10,214 INFO  [org.jboss.as.webservices] (ServerService Thread Pool -- 72) WFLYWS0002: Activating WebServices Extension

              2018-03-07 09:49:10,225 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 48) WFLYCLINF0001: Activating Infinispan subsystem.

              2018-03-07 09:49:10,226 DEBUG [org.jboss.as.security] (MSC service thread 1-8) Starting SecurityBootstrapService

              2018-03-07 09:49:10,227 INFO  [org.jboss.as.security] (MSC service thread 1-8) WFLYSEC0001: Current PicketBox version=5.0.2.Final

              2018-03-07 09:49:10,227 DEBUG [org.jboss.as.security] (MSC service thread 1-8) Initializing JACC from legacy subsystem.

              2018-03-07 09:49:10,250 INFO  [org.jboss.as.connector] (MSC service thread 1-6) WFLYJCA0009: Starting JCA Subsystem (WildFly/IronJacamar 1.4.6.Final)

              2018-03-07 09:49:10,266 DEBUG [org.jboss.as.security] (MSC service thread 1-7) Starting JaasConfigurationService

              2018-03-07 09:49:10,271 DEBUG [org.jboss.as.security] (MSC service thread 1-4) Starting SecurityManagementService

              2018-03-07 09:49:10,314 INFO  [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 42) WFLYJCA0004: Deploying JDBC-compliant driver class org.h2.Driver (version 1.4)

              2018-03-07 09:49:10,386 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-6) WFLYJCA0018: Started Driver service with driver-name = h2

              2018-03-07 09:49:10,388 DEBUG [org.jboss.as.security] (MSC service thread 1-4) Starting SubjectFactoryService

              2018-03-07 09:49:10,399 INFO  [org.jboss.as.naming] (MSC service thread 1-8) WFLYNAM0003: Starting Naming Service

              2018-03-07 09:49:10,400 INFO  [org.jboss.as.mail.extension] (MSC service thread 1-8) WFLYMAIL0001: Bound mail session [java:jboss/mail/Default]

              2018-03-07 09:49:10,455 DEBUG [org.jboss.as.security] (MSC service thread 1-8) Starting SecurityDomainService(dms-domain)

              2018-03-07 09:49:10,455 DEBUG [org.jboss.as.security] (MSC service thread 1-1) Starting SecurityDomainService(other)

              2018-03-07 09:49:10,460 DEBUG [org.jboss.as.security] (MSC service thread 1-1) Creating SDC for domain = other

              2018-03-07 09:49:10,463 DEBUG [org.jboss.as.security] (MSC service thread 1-8) Creating SDC for domain = dms-domain

              2018-03-07 09:49:10,477 DEBUG [org.jboss.as.security] (MSC service thread 1-6) Starting SecurityDomainService(jboss-web-policy)

              2018-03-07 09:49:10,478 DEBUG [org.jboss.as.security] (MSC service thread 1-6) Creating SDC for domain = jboss-web-policy

              2018-03-07 09:49:10,477 DEBUG [org.jboss.as.security] (MSC service thread 1-4) Starting SecurityDomainService(jboss-ejb-policy)

              2018-03-07 09:49:10,478 DEBUG [org.jboss.as.security] (MSC service thread 1-4) Creating SDC for domain = jboss-ejb-policy

              2018-03-07 09:49:10,516 DEBUG [org.jboss.as.security] (MSC service thread 1-6) Starting SecurityDomainService(jaspitest)

              2018-03-07 09:49:10,516 DEBUG [org.jboss.as.security] (MSC service thread 1-1) Starting SecurityDomainService(TibcoEmsRealm)

              2018-03-07 09:49:10,524 DEBUG [org.jboss.as.security] (MSC service thread 1-1) Creating SDC for domain = TibcoEmsRealm

              2018-03-07 09:49:10,736 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0003: Undertow 1.4.18.Final starting

              2018-03-07 09:49:10,922 INFO  [org.wildfly.extension.undertow] (ServerService Thread Pool -- 71) WFLYUT0014: Creating file handler for path 'C:\Users\PNodder\dev\wildfly-11.0.0.Final/welcome-content' with options [directory-listing: 'false', follow-symlink: 'false', case-sensitive: 'true', safe-symlink-paths: '[]']

              2018-03-07 09:49:11,139 TRACE [org.jboss.security] (MSC service thread 1-6) PBOX00226: addAppConfig(dummy), AuthInfo: AppConfigurationEntry[]:

              [0]

              LoginModule Class: Dummy

              ControlFlag: LoginModuleControlFlag: optional

              Options:

               

               

              2018-03-07 09:49:11,139 DEBUG [org.jboss.as.security] (MSC service thread 1-6) Creating SDC for domain = jaspitest

              2018-03-07 09:49:11,204 INFO  [org.wildfly.extension.io] (ServerService Thread Pool -- 47) WFLYIO001: Worker 'default' has auto-configured to 16 core threads with 128 task threads based on your 8 available processors

              2018-03-07 09:49:11,210 INFO  [org.jboss.as.ejb3] (MSC service thread 1-8) 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.

              2018-03-07 09:49:11,210 INFO  [org.jboss.as.ejb3] (MSC service thread 1-4) 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.

              2018-03-07 09:49:11,278 INFO  [org.jboss.remoting] (MSC service thread 1-5) JBoss Remoting version 5.0.5.Final

              2018-03-07 09:49:11,317 INFO  [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA032010: JBossTS Recovery Service (tag: 9db991) - JBoss Inc.

              2018-03-07 09:49:11,391 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0012: Started server default-server.

              2018-03-07 09:49:11,395 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0018: Host default-host starting

              2018-03-07 09:49:11,424 INFO  [com.arjuna.ats.jbossatx] (MSC service thread 1-3) ARJUNA032013: Starting transaction recovery manager

              2018-03-07 09:49:11,427 INFO  [com.arjuna.ats.arjuna] (MSC service thread 1-4) ARJUNA012389: OSB: Error constructing record header reader: com.hp.mwtests.ts.jta.jts.tools.JCAServerTransactionHeaderReader from [Module "org.jboss.jts" from local module loader @226a82c4 (finder: local module finder @731f8236 (roots: C:\Users\PNodder\dev\wildfly-11.0.0.Final\modules,C:\Users\PNodder\dev\wildfly-11.0.0.Final\modules\system\layers\base))]

              2018-03-07 09:49:11,429 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1) WFLYUT0006: Undertow HTTP listener default listening on 127.0.0.1:8080

              2018-03-07 09:49:11,430 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2) WFLYUT0006: Undertow AJP listener ajp listening on 127.0.0.1:8009

              2018-03-07 09:49:11,436 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000001: Initializing mod_cluster version 1.3.7.Final

              2018-03-07 09:49:11,439 INFO  [com.arjuna.ats.jbossatx] (MSC service thread 1-4) ARJUNA032017: JBossTS Transaction Service (JTA version - tag: 9db991) - JBoss Inc.

              2018-03-07 09:49:11,444 INFO  [org.jboss.modcluster] (ServerService Thread Pool -- 74) MODCLUSTER000032: Listening to proxy advertisements on /224.0.1.105:23364

              2018-03-07 09:49:11,489 INFO  [org.jboss.as.ejb3] (MSC service thread 1-5) WFLYEJB0493: EJB subsystem suspension complete

              2018-03-07 09:49:11,518 INFO  [org.jboss.as.connector.deployers.RADeployer] (MSC service thread 1-8) IJ020001: Required license terms for file:/C:/Users/PNodder/dev/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

              2018-03-07 09:49:11,550 INFO  [org.jboss.as.connector.deployers.RaXmlDeployer] (MSC service thread 1-8) IJ020001: Required license terms for file:/C:/Users/PNodder/dev/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

              2018-03-07 09:49:11,580 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 74) MSC000001: Failed to start service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": org.jboss.msc.service.StartException in service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]

              at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$2.run(AbstractResourceAdapterDeploymentService.java:332)

              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)

              at org.jboss.threads.JBossThread.run(JBossThread.java:320)

              Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/C:/Users/PNodder/dev/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

              at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:2064)

              at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService$WildFlyRaXmlDeployer.doDeploy(ResourceAdapterXmlDeploymentService.java:173)

              at org.jboss.as.connector.services.resourceadapters.deployment.ResourceAdapterXmlDeploymentService.start(ResourceAdapterXmlDeploymentService.java:116)

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

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

              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: java.lang.IllegalStateException

              at org.jboss.msc.value.InjectedValue.getValue(InjectedValue.java:47)

              at org.jboss.as.connector.services.resourceadapters.deployment.AbstractResourceAdapterDeploymentService$AbstractWildFlyRaDeployer.getSubjectFactory(AbstractResourceAdapterDeploymentService.java:635)

              at org.jboss.jca.deployers.common.AbstractResourceAdapterDeployer.createObjectsAndInjectValue(AbstractResourceAdapterDeployer.java:1666)

              ... 7 more

               

               

              2018-03-07 09:49:11,585 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-2) WFLYJCA0001: Bound data source [java:jboss/datasources/ExampleDS]

              2018-03-07 09:49:12,418 INFO  [org.wildfly.iiop.openjdk] (MSC service thread 1-7) WFLYIIOP0009: CORBA ORB Service started

              2018-03-07 09:49:17,849 INFO  [org.jboss.as.patching] (MSC service thread 1-3) WFLYPAT0050: WildFly Full cumulative patch ID is: base, one-off patches include: none

              2018-03-07 09:49:17,861 WARN  [org.jboss.as.domain.management.security] (MSC service thread 1-7) WFLYDM0111: Keystore C:\Users\PNodder\dev\wildfly-11.0.0.Final\standalone\configuration\application.keystore not found, it will be auto generated on first use with a self signed certificate for host localhost

              2018-03-07 09:49:17,867 INFO  [org.jboss.as.server.deployment.scanner] (MSC service thread 1-1) WFLYDS0013: Started FileSystemDeploymentService for directory C:\Users\PNodder\dev\wildfly-11.0.0.Final\standalone\deployments

              2018-03-07 09:49:17,868 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-6) WFLYSRV0027: Starting deployment of "mssql-jdbc-6" (runtime-name: "mssql-jdbc-6")

              2018-03-07 09:49:18,296 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-7) WFLYUT0006: Undertow HTTPS listener https listening on 127.0.0.1:8443

              2018-03-07 09:49:20,334 INFO  [org.jboss.ws.common.management] (MSC service thread 1-7) JBWS022052: Starting JBossWS 5.1.9.Final (Apache CXF 3.1.12)

              2018-03-07 09:49:21,187 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-1) WFLYJCA0004: Deploying JDBC-compliant driver class com.microsoft.sqlserver.jdbc.SQLServerDriver (version 6.2)

              2018-03-07 09:49:21,200 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service thread 1-8) WFLYJCA0018: Started Driver service with driver-name = mssql-jdbc-6

              2018-03-07 09:49:21,205 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-4) WFLYJCA0001: Bound data source [java:/MSSQLDS]

              2018-03-07 09:49:21,205 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/INSTRUMENT-INSTDB]

              2018-03-07 09:49:21,205 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) WFLYJCA0001: Bound data source [java:jboss/datasources/DMSDB]

              2018-03-07 09:49:21,205 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-6) WFLYJCA0001: Bound data source [java:jboss/datasources/INSTRUMENTDB]

              2018-03-07 09:49:21,206 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-8) WFLYJCA0001: Bound data source [java:jboss/datasources/JmsDS]

              2018-03-07 09:49:21,215 TRACE [org.jboss.security] (MSC service thread 1-2) PBOX00337: nextState for action getPolicyConfiguration: open

              2018-03-07 09:49:21,215 DEBUG [org.jboss.security] (MSC service thread 1-2) PBOX00307: Constructing JBossPolicyConfiguration with contextID mssql-jdbc-6

              2018-03-07 09:49:21,215 TRACE [org.jboss.security] (MSC service thread 1-2) PBOX00337: nextState for action getPolicyConfiguration: open

              2018-03-07 09:49:21,217 DEBUG [org.jboss.as.security] (MSC service thread 1-2) Cannot create permissions with 'null' metaData for id=mssql-jdbc-6

              2018-03-07 09:49:21,217 TRACE [org.jboss.security] (MSC service thread 1-2) PBOX00314: commit, contextID: mssql-jdbc-6

              2018-03-07 09:49:21,217 TRACE [org.jboss.security] (MSC service thread 1-2) PBOX00337: nextState for action commit: inService

              2018-03-07 09:49:21,553 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-8) WFLYMSGAMQ0001: AIO wasn't located on this platform, it will fall back to using pure Java NIO.

              2018-03-07 09:49:21,651 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221000: live Message Broker is starting with configuration Broker Configuration (clustered=true,journalDirectory=C:\Users\PNodder\dev\wildfly-11.0.0.Final\standalone\data\activemq\journal,bindingsDirectory=C:\Users\PNodder\dev\wildfly-11.0.0.Final\standalone\data\activemq\bindings,largeMessagesDirectory=C:\Users\PNodder\dev\wildfly-11.0.0.Final\standalone\data\activemq\largemessages,pagingDirectory=C:\Users\PNodder\dev\wildfly-11.0.0.Final\standalone\data\activemq\paging)

              2018-03-07 09:49:21,687 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221013: Using NIO Journal

              2018-03-07 09:49:21,890 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000078: Starting JGroups channel ejb

              2018-03-07 09:49:21,891 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000078: Starting JGroups channel ejb

              2018-03-07 09:49:21,890 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000078: Starting JGroups channel ejb

              2018-03-07 09:49:21,890 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000078: Starting JGroups channel ejb

              2018-03-07 09:49:22,019 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000094: Received new cluster view for channel ejb: [bfs-devsup-m37|0] (1) [bfs-devsup-m37]

              2018-03-07 09:49:22,019 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000094: Received new cluster view for channel ejb: [bfs-devsup-m37|0] (1) [bfs-devsup-m37]

              2018-03-07 09:49:22,019 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000094: Received new cluster view for channel ejb: [bfs-devsup-m37|0] (1) [bfs-devsup-m37]

              2018-03-07 09:49:22,019 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000094: Received new cluster view for channel ejb: [bfs-devsup-m37|0] (1) [bfs-devsup-m37]

              2018-03-07 09:49:22,024 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-2) ISPN000079: Channel ejb local address is bfs-devsup-m37, physical addresses are [127.0.0.1:55200]

              2018-03-07 09:49:22,024 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-4) ISPN000079: Channel ejb local address is bfs-devsup-m37, physical addresses are [127.0.0.1:55200]

              2018-03-07 09:49:22,024 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-7) ISPN000079: Channel ejb local address is bfs-devsup-m37, physical addresses are [127.0.0.1:55200]

              2018-03-07 09:49:22,024 INFO  [org.infinispan.remoting.transport.jgroups.JGroupsTransport] (MSC service thread 1-6) ISPN000079: Channel ejb local address is bfs-devsup-m37, physical addresses are [127.0.0.1:55200]

              2018-03-07 09:49:22,036 INFO  [org.infinispan.factories.GlobalComponentRegistry] (MSC service thread 1-2) ISPN000128: Infinispan version: Infinispan 'Chakra' 8.2.8.Final

              2018-03-07 09:49:22,037 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221043: Protocol module found: [artemis-server]. Adding protocol support for: CORE

              2018-03-07 09:49:22,208 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221043: Protocol module found: [artemis-amqp-protocol]. Adding protocol support for: AMQP

              2018-03-07 09:49:22,210 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221043: Protocol module found: [artemis-hornetq-protocol]. Adding protocol support for: HORNETQ

              2018-03-07 09:49:22,211 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221043: Protocol module found: [artemis-stomp-protocol]. Adding protocol support for: STOMP

              2018-03-07 09:49:22,437 INFO  [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 74) WFLYCLINF0002: Started client-mappings cache from ejb container

              2018-03-07 09:49:22,822 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

              2018-03-07 09:49:22,822 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-7) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

              2018-03-07 09:49:22,822 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor-throughput acceptor

              2018-03-07 09:49:22,823 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-1) WFLYMSGAMQ0016: Registered HTTP upgrade for activemq-remoting protocol handled by http-acceptor acceptor

              2018-03-07 09:49:23,189 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221007: Server is now live

              2018-03-07 09:49:23,189 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 75) AMQ221001: Apache ActiveMQ Artemis Message Broker version 1.5.5.jbossorg-008 [default, nodeID=2d4c6639-f536-11e7-a96e-0a0027000002]

              2018-03-07 09:49:23,202 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 75) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ConnectionFactory

              2018-03-07 09:49:23,210 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 95) AMQ221003: Deploying queue jms.queue.StpQueryWorkerQueue2

              2018-03-07 09:49:23,219 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 92) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/exported/jms/RemoteConnectionFactory

              2018-03-07 09:49:23,219 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 94) AMQ221003: Deploying queue jms.queue.ExpiryQueue

              2018-03-07 09:49:23,220 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 90) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue5

              2018-03-07 09:49:23,220 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 82) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue1

              2018-03-07 09:49:23,221 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 88) AMQ221003: Deploying queue jms.queue.GenerateTemplateInstanceResult

              2018-03-07 09:49:23,222 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 97) AMQ221052: Deploying topic jms.topic.dealEvent

              2018-03-07 09:49:23,233 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 96) AMQ221052: Deploying topic jms.topic.dealUpdate

              2018-03-07 09:49:23,234 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-2) WFLYJCA0007: Registered connection factory java:/JmsXA

              2018-03-07 09:49:23,234 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 98) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue4

              2018-03-07 09:49:23,234 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 91) AMQ221003: Deploying queue jms.queue.StpWorkerQueue1

              2018-03-07 09:49:23,235 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 99) AMQ221003: Deploying queue jms.queue.GenerateTemplateInstance

              2018-03-07 09:49:23,235 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 89) AMQ221052: Deploying topic jms.topic.DmsTestTopic

              2018-03-07 09:49:23,236 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactoryClustered

              2018-03-07 09:49:23,237 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name /ClusteredConnectionFactory

              2018-03-07 09:49:23,237 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name /ClusteredXAConnectionFactory

              2018-03-07 09:49:23,240 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ClusteredConnectionFactory

              2018-03-07 09:49:23,241 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ClusteredConnectionFactory

              2018-03-07 09:49:23,242 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0006: Unbound messaging object to jndi name java:/ClusteredXAConnectionFactory

              2018-03-07 09:49:23,242 INFO  [org.wildfly.extension.messaging-activemq] (ServerService Thread Pool -- 85) WFLYMSGAMQ0002: Bound messaging object to jndi name java:/ClusteredXAConnectionFactory

              2018-03-07 09:49:23,242 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 81) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue6

              2018-03-07 09:49:23,243 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 84) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue7

              2018-03-07 09:49:23,243 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 83) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue8

              2018-03-07 09:49:23,243 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 87) AMQ221052: Deploying topic jms.topic.stpEvent

              2018-03-07 09:49:23,244 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 86) AMQ221003: Deploying queue jms.queue.DLQ

              2018-03-07 09:49:23,244 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 79) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue2

              2018-03-07 09:49:23,245 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 93) AMQ221052: Deploying topic jms.topic.dmsControl

              2018-03-07 09:49:23,245 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ221003: Deploying queue jms.queue.StpQueryWorkerQueue1

              2018-03-07 09:49:23,245 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 80) AMQ221003: Deploying queue jms.queue.DmsTestWorkerQueue1

              2018-03-07 09:49:23,246 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 77) AMQ221003: Deploying queue jms.queue.StpWorkerQueue2

              2018-03-07 09:49:23,246 INFO  [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 74) AMQ221003: Deploying queue jms.queue.ExecutionWorkerQueue3

              2018-03-07 09:49:23,281 INFO  [org.apache.activemq.artemis.ra] (MSC service thread 1-2) Resource adaptor started

              2018-03-07 09:49:23,281 INFO  [org.jboss.as.connector.services.resourceadapters.ResourceAdapterActivatorService$ResourceAdapterActivator] (MSC service thread 1-2) IJ020002: Deployed: file://RaActivatoractivemq-ra

              2018-03-07 09:49:23,283 INFO  [org.wildfly.extension.messaging-activemq] (MSC service thread 1-6) WFLYMSGAMQ0002: Bound messaging object to jndi name java:jboss/DefaultJMSConnectionFactory

              2018-03-07 09:49:23,283 INFO  [org.jboss.as.connector.deployment] (MSC service thread 1-1) WFLYJCA0002: Bound JCA ConnectionFactory [java:/JmsXA]

              2018-03-07 09:49:23,287 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([

                  ("subsystem" => "resource-adapters"),

                  ("resource-adapter" => "generic-jms-ra")

              ]) - failure description: {"WFLYCTL0080: Failed services" => {"jboss.ra.deployment.\"org.jboss.genericjms:main_generic-jms-ra\"" => "WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]

                  Caused by: org.jboss.jca.deployers.common.DeployException: IJ020056: Deployment failed: file:/C:/Users/PNodder/dev/wildfly-11.0.0.Final/modules/system/layers/base/org/jboss/genericjms/main/

                  Caused by: java.lang.IllegalStateException"}}

              2018-03-07 09:49:23,299 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0010: Deployed "mssql-jdbc-6" (runtime-name : "mssql-jdbc-6")

              2018-03-07 09:49:23,303 INFO  [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report

              WFLYCTL0186:   Services which failed to start:      service jboss.ra.deployment."org.jboss.genericjms:main_generic-jms-ra": WFLYJCA0046: Failed to start RA deployment [generic-jms-ra]

               

               

              2018-03-07 09:49:23,418 INFO  [org.jboss.as.server] (Controller Boot Thread) WFLYSRV0212: Resuming server

              2018-03-07 09:49:23,420 INFO  [com.arjuna.ats.jbossatx] (Controller Boot Thread) ARJUNA032035: Resuming transaction recovery manager

              2018-03-07 09:49:23,421 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0060: Http management interface listening on http://127.0.0.1:9990/management

              2018-03-07 09:49:23,422 INFO  [org.jboss.as] (Controller Boot Thread) WFLYSRV0051: Admin console listening on http://127.0.0.1:9990

              2018-03-07 09:49:23,422 ERROR [org.jboss.as] (Controller Boot Thread) WFLYSRV0026: WildFly Full 11.0.0.Final (WildFly Core 3.0.8.Final) started (with errors) in 26870ms - Started 563 of 812 services (1 services failed or missing dependencies, 490 services are lazy, passive or on-demand)

              • 4. Re: Exception on startup when using Generic JMS RA and domain security
                simkam Newbie

                I was able to reproduce this, I filed [WFLY-9978] resource adapter sometimes fails to start when it uses legacy security-domain - JBoss Issue Tracker  . As a workaround you could replace legacy security domain with elytron authentication context (or credential reference) -- WildFly Elytron Security