[Red Hat JIRA] (WFCORE-4214) VaultPasswordsInCLITestCase fails with Elytron profile
by Marek Kopecky (Jira)
[ https://issues.redhat.com/browse/WFCORE-4214?page=com.atlassian.jira.plug... ]
Marek Kopecky updated WFCORE-4214:
----------------------------------
Affects Version/s: 13.0.2.Final
> VaultPasswordsInCLITestCase fails with Elytron profile
> ------------------------------------------------------
>
> Key: WFCORE-4214
> URL: https://issues.redhat.com/browse/WFCORE-4214
> Project: WildFly Core
> Issue Type: Bug
> Components: Security, Test Suite
> Affects Versions: 7.0.0.Alpha5, 13.0.2.Final
> Reporter: Martin Choma
> Priority: Major
>
> cd testsuite/manualmode/
> mvn test -Delytron -Dtest=VaultPasswordsInCLITestCase
> {code}
> [INFO] Running org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.006 s <<< FAILURE! - in org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase
> [ERROR] org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase Time elapsed: 0.005 s <<< ERROR!
> java.lang.RuntimeException:
> {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.core.management.security.realm.ManagementRealm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.core.management.security.realm.ManagementRealm]"]
> }
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:265)
> at org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase$ManagementInterfacesSetup.setup(VaultPasswordsInCLITestCase.java:215)
> at org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.prepareServer(VaultPasswordsInCLITestCase.java:107)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [ERROR] org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase Time elapsed: 0.006 s <<< ERROR!
> java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://127.0.0.1:9999. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80)
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:257)
> at org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.resetHttpInterfaceConfiguration(VaultPasswordsInCLITestCase.java:274)
> at org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.resetConfigurationForNativeInterface(VaultPasswordsInCLITestCase.java:150)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote://127.0.0.1:9999. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:60)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 32 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:571)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:533)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:521)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:204)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> ... 42 more
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase.org.jboss.as.test.manualmode.vault.VaultPasswordsInCLITestCase
> [ERROR] Run 1: VaultPasswordsInCLITestCase.prepareServer:107 » Runtime {
> "WFLYCTL0412: Re...
> [ERROR] Run 2: VaultPasswordsInCLITestCase.resetConfigurationForNativeInterface:150->resetHttpInterfaceConfiguration:274 » IO
> [INFO]
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[Red Hat JIRA] (WFCORE-4216) HTTPSManagementInterfaceTestCase fails with Elytron profile
by Marek Kopecky (Jira)
[ https://issues.redhat.com/browse/WFCORE-4216?page=com.atlassian.jira.plug... ]
Marek Kopecky resolved WFCORE-4216.
-----------------------------------
Resolution: Done
This issue is fixed in WF-core 13.0.2.Final
> HTTPSManagementInterfaceTestCase fails with Elytron profile
> -----------------------------------------------------------
>
> Key: WFCORE-4216
> URL: https://issues.redhat.com/browse/WFCORE-4216
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Priority: Major
> Fix For: 13.0.2.Final
>
>
> {noformat}
> cd testsuite/manualmode/
> mvn test -Delytron -Dtest=HTTPSManagementInterfaceTestCase
> {noformat}
> {noformat}
> [INFO] Running org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.005 s <<< FAILURE! - in org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase
> [ERROR] org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase Time elapsed: 0.004 s <<< ERROR!
> java.lang.RuntimeException:
> {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.core.management.security.realm.ManagementRealm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.core.management.security.realm.ManagementRealm]"]
> }
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:265)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.serverSetup(HTTPSManagementInterfaceTestCase.java:328)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.startAndSetupContainer(HTTPSManagementInterfaceTestCase.java:121)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [ERROR] org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase Time elapsed: 0.005 s <<< ERROR!
> java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remoting://127.0.0.1:9999. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80)
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:257)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.resetHttpInterfaceConfiguration(HTTPSManagementInterfaceTestCase.java:380)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.stopContainer(HTTPSManagementInterfaceTestCase.java:238)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remoting://127.0.0.1:9999. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:60)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 32 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:571)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:533)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:521)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:204)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> ... 42 more
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase
> [ERROR] Run 1: HTTPSManagementInterfaceTestCase.startAndSetupContainer:121->serverSetup:328 » Runtime
> [ERROR] Run 2: HTTPSManagementInterfaceTestCase.stopContainer:238->resetHttpInterfaceConfiguration:380 » IO
> [INFO]
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[Red Hat JIRA] (WFCORE-4216) HTTPSManagementInterfaceTestCase fails with Elytron profile
by Marek Kopecky (Jira)
[ https://issues.redhat.com/browse/WFCORE-4216?page=com.atlassian.jira.plug... ]
Marek Kopecky updated WFCORE-4216:
----------------------------------
Fix Version/s: 13.0.2.Final
> HTTPSManagementInterfaceTestCase fails with Elytron profile
> -----------------------------------------------------------
>
> Key: WFCORE-4216
> URL: https://issues.redhat.com/browse/WFCORE-4216
> Project: WildFly Core
> Issue Type: Bug
> Components: Management, Security, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Priority: Major
> Fix For: 13.0.2.Final
>
>
> {noformat}
> cd testsuite/manualmode/
> mvn test -Delytron -Dtest=HTTPSManagementInterfaceTestCase
> {noformat}
> {noformat}
> [INFO] Running org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.005 s <<< FAILURE! - in org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase
> [ERROR] org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase Time elapsed: 0.004 s <<< ERROR!
> java.lang.RuntimeException:
> {
> "WFLYCTL0412: Required services that are not installed:" => ["org.wildfly.core.management.security.realm.ManagementRealm"],
> "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.remoting.server.management is missing [org.wildfly.core.management.security.realm.ManagementRealm]"]
> }
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:265)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.serverSetup(HTTPSManagementInterfaceTestCase.java:328)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.startAndSetupContainer(HTTPSManagementInterfaceTestCase.java:121)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> [ERROR] org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase Time elapsed: 0.005 s <<< ERROR!
> java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remoting://127.0.0.1:9999. The connection failed
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:149)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:80)
> at org.jboss.as.test.integration.security.common.CoreUtils.applyUpdate(CoreUtils.java:257)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.resetHttpInterfaceConfiguration(HTTPSManagementInterfaceTestCase.java:380)
> at org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.stopContainer(HTTPSManagementInterfaceTestCase.java:238)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
> at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
> at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:33)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:109)
> at org.junit.runners.Suite.runChild(Suite.java:128)
> at org.junit.runners.Suite.runChild(Suite.java:27)
> at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
> at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
> at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
> at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
> at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
> at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
> at org.apache.maven.surefire.junitcore.JUnitCore.run(JUnitCore.java:55)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.createRequestAndRun(JUnitCoreWrapper.java:137)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.executeEager(JUnitCoreWrapper.java:107)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:83)
> at org.apache.maven.surefire.junitcore.JUnitCoreWrapper.execute(JUnitCoreWrapper.java:75)
> at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:158)
> at org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:383)
> at org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:344)
> at org.apache.maven.surefire.booter.ForkedBooter.execute(ForkedBooter.java:125)
> at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:417)
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remoting://127.0.0.1:9999. The connection failed
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:128)
> at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:259)
> at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70)
> at org.jboss.as.protocol.mgmt.ManagementClientChannelStrategy$Establishing.getChannel(ManagementClientChannelStrategy.java:167)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:146)
> at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:60)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:135)
> at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:110)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:263)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:168)
> at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:147)
> ... 32 more
> Caused by: java.net.ConnectException: Connection refused
> at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
> at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:717)
> at org.xnio.nio.WorkerThread$ConnectHandle.handleReady(WorkerThread.java:327)
> at org.xnio.nio.WorkerThread.run(WorkerThread.java:591)
> at ...asynchronous invocation...(Unknown Source)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:571)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:533)
> at org.jboss.remoting3.EndpointImpl.connect(EndpointImpl.java:521)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connect(ProtocolConnectionUtils.java:204)
> at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:120)
> ... 42 more
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase.org.wildfly.core.test.standalone.mgmt.HTTPSManagementInterfaceTestCase
> [ERROR] Run 1: HTTPSManagementInterfaceTestCase.startAndSetupContainer:121->serverSetup:328 » Runtime
> [ERROR] Run 2: HTTPSManagementInterfaceTestCase.stopContainer:238->resetHttpInterfaceConfiguration:380 » IO
> [INFO]
> [INFO]
> [ERROR] Tests run: 1, Failures: 0, Errors: 1, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> {noformat}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[Red Hat JIRA] (WFLY-13949) JNDI lookup for JMS Queue failing
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13949?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet edited comment on WFLY-13949 at 10/14/20 9:44 AM:
--------------------------------------------------------------------
Your JNDI name is incorrect, you should be using (note the removed /) :
{code:java}
/subsystem=messaging-activemq/server=default/jms-queue=test1/:add(entries=["java:jboss/exported/jms/queue/test1"]){code}
was (Author: ehugonnet):
Your JNDI name is incorrect, you should be using :
{code:java}
/subsystem=messaging-activemq/server=default/jms-queue=test1/:add(entries=["java:jboss/exported/jms/queue/test1"]) {code}
> JNDI lookup for JMS Queue failing
> ---------------------------------
>
> Key: WFLY-13949
> URL: https://issues.redhat.com/browse/WFLY-13949
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.1.Final
> Reporter: Francis Griffin
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Attachments: dpsrTest.tgz
>
>
> I have a JMS app which has been running successfully under WF10 for some years. I'm trying to migrate to WF20, but getting an error trying to look up the JMS Queue. The JDK is OpenJDK 11.
> I've tried to make the reproducible case as simple as possible. The server is unpacked from the downloaded tar.gz, and is not modified except to add a guest user for JMS (which is not needed for the reproducible case, since we never actually create a Connection). The queue is the DLQ queue defined in the distribution.
> The error is a NameNotFoundException:
> Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
> at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
> at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> No matter what queue name I use, the lookup is failing on the string jms/queue rather than the expected jms/queue/DLQ.
> I fully expect that this is some stupid error on my part, something I'm looking at and just not seeing, because I know of others (albeit using Windows) who are using 20.0.1.Final for the full app without issue. But I can't for the life of me see what it is.
> Tha actual full application looks up a ConnectionFactory of "jms/RemoteConnectionFactory" and creates Connections and Sessions before looking up the Queue name. The lookup for the factory name works perfectly, as does the other stuff, but the lookup for the Queue name gets the same NameNotFoundException shown above.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[Red Hat JIRA] (WFLY-13949) JNDI lookup for JMS Queue failing
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13949?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet commented on WFLY-13949:
------------------------------------------
Your JNDI name is incorrect, you should be using :
{code:java}
/subsystem=messaging-activemq/server=default/jms-queue=test1/:add(entries=["java:jboss/exported/jms/queue/test1"]) {code}
> JNDI lookup for JMS Queue failing
> ---------------------------------
>
> Key: WFLY-13949
> URL: https://issues.redhat.com/browse/WFLY-13949
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.1.Final
> Reporter: Francis Griffin
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Attachments: dpsrTest.tgz
>
>
> I have a JMS app which has been running successfully under WF10 for some years. I'm trying to migrate to WF20, but getting an error trying to look up the JMS Queue. The JDK is OpenJDK 11.
> I've tried to make the reproducible case as simple as possible. The server is unpacked from the downloaded tar.gz, and is not modified except to add a guest user for JMS (which is not needed for the reproducible case, since we never actually create a Connection). The queue is the DLQ queue defined in the distribution.
> The error is a NameNotFoundException:
> Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
> at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
> at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> No matter what queue name I use, the lookup is failing on the string jms/queue rather than the expected jms/queue/DLQ.
> I fully expect that this is some stupid error on my part, something I'm looking at and just not seeing, because I know of others (albeit using Windows) who are using 20.0.1.Final for the full app without issue. But I can't for the life of me see what it is.
> Tha actual full application looks up a ConnectionFactory of "jms/RemoteConnectionFactory" and creates Connections and Sessions before looking up the Queue name. The lookup for the factory name works perfectly, as does the other stuff, but the lookup for the Queue name gets the same NameNotFoundException shown above.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months
[Red Hat JIRA] (WFLY-13949) JNDI lookup for JMS Queue failing
by Emmanuel Hugonnet (Jira)
[ https://issues.redhat.com/browse/WFLY-13949?page=com.atlassian.jira.plugi... ]
Emmanuel Hugonnet edited comment on WFLY-13949 at 10/14/20 9:30 AM:
--------------------------------------------------------------------
Found the shell scripts under src/main/resources
was (Author: ehugonnet):
Your shell scripts are not present
> JNDI lookup for JMS Queue failing
> ---------------------------------
>
> Key: WFLY-13949
> URL: https://issues.redhat.com/browse/WFLY-13949
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 20.0.1.Final
> Reporter: Francis Griffin
> Assignee: Emmanuel Hugonnet
> Priority: Major
> Attachments: dpsrTest.tgz
>
>
> I have a JMS app which has been running successfully under WF10 for some years. I'm trying to migrate to WF20, but getting an error trying to look up the JMS Queue. The JDK is OpenJDK 11.
> I've tried to make the reproducible case as simple as possible. The server is unpacked from the downloaded tar.gz, and is not modified except to add a guest user for JMS (which is not needed for the reproducible case, since we never actually create a Connection). The queue is the DLQ queue defined in the distribution.
> The error is a NameNotFoundException:
> Exception in thread "main" javax.naming.NameNotFoundException: jms/queue -- service jboss.naming.context.java.jboss.exported.jms.queue
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:106)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:207)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:193)
> at org.jboss.as.naming@20.0.1.Final//org.jboss.as.naming.NamingContext.lookup(NamingContext.java:189)
> at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport.handleLookup(RemoteServerTransport.java:203)
> at org.wildfly.naming-client@1.0.13.Final//org.wildfly.naming.client.remote.RemoteServerTransport$1.handleMessage(RemoteServerTransport.java:123)
> at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.remote.RemoteConnectionChannel.lambda$handleMessageData$3(RemoteConnectionChannel.java:430)
> at org.jboss.remoting@5.0.18.Final//org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:991)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
> at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
> at java.base/java.lang.Thread.run(Thread.java:834)
> No matter what queue name I use, the lookup is failing on the string jms/queue rather than the expected jms/queue/DLQ.
> I fully expect that this is some stupid error on my part, something I'm looking at and just not seeing, because I know of others (albeit using Windows) who are using 20.0.1.Final for the full app without issue. But I can't for the life of me see what it is.
> Tha actual full application looks up a ConnectionFactory of "jms/RemoteConnectionFactory" and creates Connections and Sessions before looking up the Queue name. The lookup for the factory name works perfectly, as does the other stuff, but the lookup for the Queue name gets the same NameNotFoundException shown above.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
5 years, 6 months