[jboss-jira] [JBoss JIRA] (WFLY-10985) UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem

[Miroslav Novak (JIRA)]

Miroslav Novak created WFLY-10985:
-------------------------------------

             Summary: UnsupportedOperationException thrown during start if CredentialReference is used in messaging-activemq subsystem
                 Key: WFLY-10985
                 URL: https://issues.jboss.org/browse/WFLY-10985
             Project: WildFly
          Issue Type: Bug
          Components: JMS
    Affects Versions: 14.0.0.Final
            Reporter: Miroslav Novak
            Assignee: Jeff Mesnil
            Priority: Critical


If messaging subsystem is referencing elytron's credential store like in:
{code}
               <bridge name="myBridge" queue-name="jms.queue.InQueue" forwarding-address="jms.queue.OutQueue" ha="true" reconnect-attempts="-1" use-duplicate-detection="true" user="johnOut" static-connectors="bridge-connector">
                    <credential-reference store="bridge-cs001" alias="john_out_alias_wrong"/>
                </bridge>
{code}

then during start server throws exception:

{code}
12:49:04,367 ERROR [org.jboss.as.controller.management-operation] (ServerService Thread Pool -- 66) WFLYCTL0013: Operation ("add") failed - address: ([
    ("subsystem" => "messaging-activemq"),
    ("server" => "default")
]): java.lang.UnsupportedOperationException
	at org.jboss.msc.service.ServiceBuilderImpl.addDependency(ServiceBuilderImpl.java:409)
	at org.jboss.msc.service.DelegatingServiceBuilder.addDependency(DelegatingServiceBuilder.java:147)
	at org.jboss.as.controller.security.CredentialReference.getCredentialSourceSupplier(CredentialReference.java:323)
	at org.wildfly.extension.messaging.activemq.ServerAdd.addBridgeCredentialStoreReference(ServerAdd.java:732)
	at org.wildfly.extension.messaging.activemq.ServerAdd.access$200(ServerAdd.java:175)
	at org.wildfly.extension.messaging.activemq.ServerAdd$2.execute(ServerAdd.java:439)
	at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:999)
	at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:743)
	at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:467)
	at org.jboss.as.controller.ParallelBootOperationStepHandler$ParallelBootTask.run(ParallelBootOperationStepHandler.java:384)
	at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
	at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487)
	at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349)
	at java.lang.Thread.run(Thread.java:748)
	at org.jboss.threads.JBossThread.run(JBossThread.java:485)
{code}

Attaching standalone-full-ha.xml with which is possible to reproduce the issue.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)