[JBoss JIRA] (DROOLS-3327) Duplicate an instance
by Liz Clayton (Jira)
[ https://issues.jboss.org/browse/DROOLS-3327?page=com.atlassian.jira.plugi... ]
Liz Clayton commented on DROOLS-3327:
-------------------------------------
[~kkufova] Can I mark this as resolved? If not, [~danielezonca] and [~gabriolo] please let me know what additional info you need from me. Thanks!
> Duplicate an instance
> ---------------------
>
> Key: DROOLS-3327
> URL: https://issues.jboss.org/browse/DROOLS-3327
> Project: Drools
> Issue Type: Sub-task
> Components: Test Scenarios Editor
> Reporter: Liz Clayton
> Assignee: Liz Clayton
> Priority: Major
> Labels: ScenarioSimulation, UX, UXTeam
> Attachments: multiDO.png
>
>
> As a user I want to be able to duplicate a Given/Expect statement (column) so that I can create a statement with an instance of the same data object.
> *_ refer to [parent jira|https://issues.jboss.org/browse/DROOLS-3193] for details and documentation. _
> _Note: The "duplicate" action is possible only for "instance" header (not for single property)._
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (DROOLS-3270) [DMN Designer] Cannot add BKM from Decision in DRG
by Edson Tirelli (Jira)
[ https://issues.jboss.org/browse/DROOLS-3270?page=com.atlassian.jira.plugi... ]
Edson Tirelli commented on DROOLS-3270:
---------------------------------------
Michael,
Ok, now I understand why it doesn't show up.
Having said that, it is very common to create a decision node in a diagram and them create a BKM that is invoked by that decision node. So, while you are correct, the arrow always points from the BKM to the Decision Node, it would be helpful from a user experience perspective, to be able to select a decision node and be able to create the BKM from there.
> [DMN Designer] Cannot add BKM from Decision in DRG
> --------------------------------------------------
>
> Key: DROOLS-3270
> URL: https://issues.jboss.org/browse/DROOLS-3270
> Project: Drools
> Issue Type: Bug
> Components: DMN Editor
> Affects Versions: 7.14.0.Final
> Reporter: Michael Anstis
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
>
> When selecting a Decision node in the Graph view there is no quick action to add a BKM node. There should be.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFLY-9639) Messages are stuck in a Queue that is configured on HornetQ
by Rajendra Mallampati (Jira)
[ https://issues.jboss.org/browse/WFLY-9639?page=com.atlassian.jira.plugin.... ]
Rajendra Mallampati commented on WFLY-9639:
-------------------------------------------
This issue can be closed. We found the problem (configuration.)
On Monday, November 19, 2018, 6:28:02 AM EST, Miroslav Novak (Jira) <issues(a)jboss.org> wrote:
Message Title
|
|
Rajendra Mallampati Hi Rajendra, i'm doing jira clean-up. Do you still see this issue in Wildfly 14, please?
|
|
|
|
|
|
|
> Messages are stuck in a Queue that is configured on HornetQ
> -----------------------------------------------------------
>
> Key: WFLY-9639
> URL: https://issues.jboss.org/browse/WFLY-9639
> Project: WildFly
> Issue Type: Bug
> Components: JMS
> Affects Versions: 9.x.x TBD
> Environment: RHEL 7.2, JDK 1.8_144
> Reporter: Rajendra Mallampati
> Assignee: Jeff Mesnil
> Priority: Major
>
> We use WildFly 9.0.2 for hosting our web application and it has both real time and batch processing components. One of the functions supported on the web includes uploading a file with a number of lines any where from 1 to 10K, If the file is valid (virus scan etc passed) it is parsed into that may messages and published to a queue. Each message will have two counters total number of messages that are published to the queue, and the message number.
> The consuming side is implemented using Spring DefaultMessageListenerContainer (DMLC) with a concurrency of 50 and maxConcurrency of 75. The listeners that implement MessageListener interface are integrated into DMLC. sometimes, if the producing side published 100 messages the consuming side only receiving 98 (per say) and gets stuck because two more messages should be in the Queue. Those two messages are not delivered and don't know where they are going. We tried even persistent Queues and the result is same (getting stuck).
> This is happening in production and any insight into this issue is highly appreciated.
> Here are the software details:
> App server : Wildfly 9.0.2
> HornetQ : 2.4.7
> JDK : 1_8_144
> If you need additional details I will be very glad to provide.
> Thanks
> Rajendra
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (SWSQE-523) Kiali-Istio-Checker can miss periodically crashing pods
by Matt Mahoney (Jira)
[ https://issues.jboss.org/browse/SWSQE-523?page=com.atlassian.jira.plugin.... ]
Matt Mahoney commented on SWSQE-523:
------------------------------------
This may just be a workaround to satisfy a Galley crashing bug. On some OS clusters, Galley seems to never stays up, which would mean that istio deploys would ALWAYS fail because of galley. In turn, some testing would be blocked which currently is not, because the deployment would never complete successfully until Galley is fixed.
> Kiali-Istio-Checker can miss periodically crashing pods
> -------------------------------------------------------
>
> Key: SWSQE-523
> URL: https://issues.jboss.org/browse/SWSQE-523
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Filip Brychta
> Assignee: Michael Foley
> Priority: Major
>
> Kiali-Istio-Checker periodically checks if istio pods are running. Problem is that some pods (e.g. istio-galley) can be running only for a few seconds and then crash showing CrashLoopBackOff status. When checker hits correct moment when the pod is running it incorrectly shows success. But the pod will crash again a few seconds later.
> So we need to update the checker to check that pods are running for more then a few seconds or that they are not crashing periodically.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (SWSQE-523) Kiali-Istio-Checker can miss periodically crashing pods
by Filip Brychta (Jira)
Filip Brychta created SWSQE-523:
-----------------------------------
Summary: Kiali-Istio-Checker can miss periodically crashing pods
Key: SWSQE-523
URL: https://issues.jboss.org/browse/SWSQE-523
Project: Kiali QE
Issue Type: Bug
Reporter: Filip Brychta
Assignee: Michael Foley
Kiali-Istio-Checker periodically checks if istio pods are running. Problem is that some pods (e.g. istio-galley) can be running only for a few seconds and then crash showing CrashLoopBackOff status. When checker hits correct moment when the pod is running it incorrectly shows success. But the pod will crash again a few seconds later.
So we need to update the checker to check that pods are running for more then a few seconds or that they are not crashing periodically.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (SWSQE-523) Kiali-Istio-Checker can miss periodically crashing pods
by Filip Brychta (Jira)
[ https://issues.jboss.org/browse/SWSQE-523?page=com.atlassian.jira.plugin.... ]
Filip Brychta updated SWSQE-523:
--------------------------------
Sprint: Kiali Sprint #14
> Kiali-Istio-Checker can miss periodically crashing pods
> -------------------------------------------------------
>
> Key: SWSQE-523
> URL: https://issues.jboss.org/browse/SWSQE-523
> Project: Kiali QE
> Issue Type: Bug
> Reporter: Filip Brychta
> Assignee: Michael Foley
> Priority: Major
>
> Kiali-Istio-Checker periodically checks if istio pods are running. Problem is that some pods (e.g. istio-galley) can be running only for a few seconds and then crash showing CrashLoopBackOff status. When checker hits correct moment when the pod is running it incorrectly shows success. But the pod will crash again a few seconds later.
> So we need to update the checker to check that pods are running for more then a few seconds or that they are not crashing periodically.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4219) SecurityAuthCommandsTestCase fails with Elytron profile
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4219?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise updated WFCORE-4219:
-----------------------------------------
Component/s: CLI
> SecurityAuthCommandsTestCase fails with Elytron profile
> -------------------------------------------------------
>
> Key: WFCORE-4219
> URL: https://issues.jboss.org/browse/WFCORE-4219
> Project: WildFly Core
> Issue Type: Bug
> Components: CLI, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
> Priority: Major
>
> {noformat}
> cd testsuite/standalone/
> mvn test -Delytron -Dtest=SecurityAuthCommandsTestCase
> {noformat}
> {noformat}
> [INFO] Running org.jboss.as.test.integration.management.cli.SecurityAuthCommandsTestCase
> [ERROR] Tests run: 14, Failures: 0, Errors: 3, Skipped: 0, Time elapsed: 7.44 s <<< FAILURE! - in null
> [ERROR] testDisableAuthManagement(org.jboss.as.test.integration.management.cli.SecurityAuthCommandsTestCase) Time elapsed: 0.261 s <<< ERROR!
> java.lang.Exception: Should have fail
> at org.jboss.as.test.integration.management.cli.SecurityAuthCommandsTestCase.testDisableAuthManagement(SecurityAuthCommandsTestCase.java:705)
> 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.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 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] testOOBSASLManagementNative(org.jboss.as.test.integration.management.cli.SecurityAuthCommandsTestCase) Time elapsed: 0.17 s <<< ERROR!
> org.jboss.as.cli.CommandLineException:
> {
> "outcome" => "failed",
> "failure-description" => {
> "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]"]
> },
> "rolled-back" => true
> }
> at org.jboss.as.cli.handlers.OperationRequestHandler.handle(OperationRequestHandler.java:94)
> at org.jboss.as.cli.impl.CommandContextImpl.handleOperation(CommandContextImpl.java:1800)
> at org.jboss.as.cli.impl.CommandContextImpl.handle(CommandContextImpl.java:809)
> at org.jboss.as.test.integration.management.cli.SecurityCommandsTestCase.enableNative(SecurityCommandsTestCase.java:678)
> at org.jboss.as.test.integration.management.cli.SecurityAuthCommandsTestCase.testOOBSASLManagementNative(SecurityAuthCommandsTestCase.java:423)
> 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.InvokeMethod.evaluate(InvokeMethod.java:17)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
> at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
> 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.internal.runners.statements.RunBefores.evaluate(RunBefores.java:26)
> at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
> at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:48)
> at org.junit.rules.RunRules.evaluate(RunRules.java:20)
> 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] Failure when constructing test Time elapsed: 0.431 s <<< ERROR!
> java.lang.RuntimeException: java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:238)
> at org.wildfly.core.testrunner.WildflyTestRunner.checkServerState(WildflyTestRunner.java:167)
> at org.wildfly.core.testrunner.WildflyTestRunner.runTearDownTasks(WildflyTestRunner.java:138)
> at org.wildfly.core.testrunner.WildflyTestRunner.run(WildflyTestRunner.java:111)
> 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.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. 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:75)
> at org.jboss.as.controller.client.helpers.DelegatingModelControllerClient.execute(DelegatingModelControllerClient.java:63)
> at org.wildfly.core.testrunner.ManagementClient.executeForResult(ManagementClient.java:234)
> ... 21 more
> Caused by: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. 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)
> ... 24 more
> Caused by: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed:
> ANONYMOUS: javax.security.sasl.SaslException: ELY05092: Authentication name is empty
> at org.jboss.remoting3.remote.ClientConnectionOpenListener.allMechanismsFailed(ClientConnectionOpenListener.java:109)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:402)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.handleEvent(ClientConnectionOpenListener.java:242)
> at org.xnio.ChannelListeners.invokeChannelListener(ChannelListeners.java:92)
> at org.xnio.conduits.ReadReadyHandler$ChannelListenerHandler.readReady(ReadReadyHandler.java:66)
> at org.xnio.nio.NioSocketConduit.handleReady(NioSocketConduit.java:89)
> 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)
> ... 34 more
> Suppressed: javax.security.sasl.SaslException: ELY05092: Authentication name is empty
> at org.wildfly.security.sasl.anonymous.AnonymousSaslClient.evaluateMessage(AnonymousSaslClient.java:74)
> at org.wildfly.security.sasl.util.AbstractSaslParticipant.evaluateMessage(AbstractSaslParticipant.java:199)
> at org.wildfly.security.sasl.util.AbstractSaslClient.evaluateChallenge(AbstractSaslClient.java:79)
> at org.wildfly.security.sasl.util.AbstractDelegatingSaslClient.evaluateChallenge(AbstractDelegatingSaslClient.java:54)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.lambda$evaluateChallenge$0(PrivilegedSaslClient.java:55)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.wildfly.security.sasl.util.PrivilegedSaslClient.evaluateChallenge(PrivilegedSaslClient.java:55)
> at org.jboss.remoting3.remote.ClientConnectionOpenListener$Capabilities.lambda$handleEvent$1(ClientConnectionOpenListener.java:460)
> at org.jboss.remoting3.EndpointImpl$TrackingExecutor.lambda$execute$0(EndpointImpl.java:949)
> 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:1378)
> at java.lang.Thread.run(Thread.java:748)
> [INFO]
> [INFO] Results:
> [INFO]
> [ERROR] Errors:
> [ERROR] java.io.IOException: java.net.ConnectException: WFLYPRT0053: Could not connect to remote+http://127.0.0.1:9990. The connection failed
> [ERROR] SecurityAuthCommandsTestCase.testDisableAuthManagement:705 Should have fail
> [ERROR] SecurityAuthCommandsTestCase.testOOBSASLManagementNative:423 » CommandLine {
> ...
> [INFO]
> [ERROR] Tests run: 14, Failures: 0, Errors: 3, Skipped: 0
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 8 months
[JBoss JIRA] (WFCORE-4215) HTTPSConnectionWithCLITestCase fails with Elytron profile
by Jean-Francois Denise (Jira)
[ https://issues.jboss.org/browse/WFCORE-4215?page=com.atlassian.jira.plugi... ]
Jean-Francois Denise reassigned WFCORE-4215:
--------------------------------------------
Assignee: Jean-Francois Denise
> HTTPSConnectionWithCLITestCase fails with Elytron profile
> ---------------------------------------------------------
>
> Key: WFCORE-4215
> URL: https://issues.jboss.org/browse/WFCORE-4215
> Project: WildFly Core
> Issue Type: Bug
> Components: Security, Test Suite
> Affects Versions: 7.0.0.Alpha5
> Reporter: Martin Choma
> Assignee: Jean-Francois Denise
> Priority: Major
>
> {noformat}
> cd testsuite/manualmode/
> mvn test -Delytron -Dtest=HTTPSConnectionWithCLITestCase
> {noformat}
> {noformat}
> [INFO] Running org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase
> [ERROR] Tests run: 2, Failures: 0, Errors: 2, Skipped: 0, Time elapsed: 0.004 s <<< FAILURE! - in org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase
> [ERROR] org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase Time elapsed: 0.003 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.HTTPSConnectionWithCLITestCase$ServerResourcesSetup.setup(HTTPSConnectionWithCLITestCase.java:234)
> at org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase.prepareServer(HTTPSConnectionWithCLITestCase.java:105)
> 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.HTTPSConnectionWithCLITestCase Time elapsed: 0.004 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.HTTPSConnectionWithCLITestCase.resetTestConfiguration(HTTPSConnectionWithCLITestCase.java:155)
> 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.HTTPSConnectionWithCLITestCase.org.wildfly.core.test.standalone.mgmt.HTTPSConnectionWithCLITestCase
> [ERROR] Run 1: HTTPSConnectionWithCLITestCase.prepareServer:105 » Runtime {
> "WFLYCTL0412:...
> [ERROR] Run 2: HTTPSConnectionWithCLITestCase.resetTestConfiguration:155 » IO java.net.Connec...
> [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.12.1#712002)
7 years, 8 months