October 2020 - jboss-jira - Jboss List Archives

[Red Hat JIRA] (WFLY-13959) WildFly management API should allow configuration of AMQ 7 broker's critical analyser

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13959?page=com.atlassian.jira.plugi... ] Brian Stansberry edited comment on WFLY-13959 at 10/12/20 12:41 PM: -------------------------------------------------------------------- Can you change the title etc then? It's clearer to only use the term CLI when we are talking about things that are specific to that tool. Sorry; we cross-posted. :) was (Author: brian.stansberry): Can you change the title etc then? It's clearer to only use the term CLI when we are talking about things that are specific to that tool. > WildFly management API should allow configuration of AMQ 7 broker's critical analyser > ------------------------------------------------------------------------------------- > > Key: WFLY-13959 > URL: https://issues.redhat.com/browse/WFLY-13959 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 21.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Increasingly we are getting cases where embedded AMQ brokers get shutdown because of some issues with critical sections. This can be prevented by changing critical analyser policy but currently there is no way of configuring it in JBoss CLI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13959) WildFly management API should allow configuration of AMQ 7 broker's critical analyser

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13959?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFLY-13959: ----------------------------------------- Can you change the title etc then? It's clearer to only use the term CLI when we are talking about things that are specific to that tool. > WildFly management API should allow configuration of AMQ 7 broker's critical analyser > ------------------------------------------------------------------------------------- > > Key: WFLY-13959 > URL: https://issues.redhat.com/browse/WFLY-13959 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 21.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Increasingly we are getting cases where embedded AMQ brokers get shutdown because of some issues with critical sections. This can be prevented by changing critical analyser policy but currently there is no way of configuring it in JBoss CLI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13959) WildFly management API should allow configuration of AMQ 7 broker's critical analyser

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13959?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet updated WFLY-13959: ------------------------------------- Summary: WildFly management API should allow configuration of AMQ 7 broker's critical analyser (was: WildFly cli should allow configuration of AMQ 7 broker's critical analyser) > WildFly management API should allow configuration of AMQ 7 broker's critical analyser > ------------------------------------------------------------------------------------- > > Key: WFLY-13959 > URL: https://issues.redhat.com/browse/WFLY-13959 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 21.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Increasingly we are getting cases where embedded AMQ brokers get shutdown because of some issues with critical sections. This can be prevented by changing critical analyser policy but currently there is no way of configuring it in JBoss CLI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13959) WildFly cli should allow configuration of AMQ 7 broker's critical analyser

by Emmanuel Hugonnet (Jira)

[ https://issues.redhat.com/browse/WFLY-13959?page=com.atlassian.jira.plugi... ] Emmanuel Hugonnet commented on WFLY-13959: ------------------------------------------ yes :) > WildFly cli should allow configuration of AMQ 7 broker's critical analyser > -------------------------------------------------------------------------- > > Key: WFLY-13959 > URL: https://issues.redhat.com/browse/WFLY-13959 > Project: WildFly > Issue Type: Feature Request > Components: JMS > Affects Versions: 21.0.0.Beta1 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > Increasingly we are getting cases where embedded AMQ brokers get shutdown because of some issues with critical sections. This can be prevented by changing critical analyser policy but currently there is no way of configuring it in JBoss CLI. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13956) TwoConnectorsEJBFailoverTestCase sometimes hangs when running with jboss-ejb-client 4.0.35

by Tomasz Adamski (Jira)

[ https://issues.redhat.com/browse/WFLY-13956?page=com.atlassian.jira.plugi... ] Tomasz Adamski commented on WFLY-13956: --------------------------------------- [~cfang] I think I was able to reproduce TwoConnectorsEJBFailoverTestCase locally - though it requires a lot of repetitions before the test finally hangs. What is more I wasn't able to reproduce is with EJBCLIENT-356 commit reverted and was able to reproduce it with EJBCLIENT-376 reverted, which would confirm our initial suspicion that EJBCLIENT-356 is a culprit. I was able to plug with debug to maven thread and saw that it is stuck waiting on awaitResponse, but I wasn't able to find out yet what happened to the two nodes that lead to this situation. I'm suspecting that there is some discovery bug when dealing with starting/stopping nodes after introduction of eagerNodes list to RemotingEJBDiscoveryProvider but I don't know yet what is the exact failure scenario. > TwoConnectorsEJBFailoverTestCase sometimes hangs when running with jboss-ejb-client 4.0.35 > ------------------------------------------------------------------------------------------ > > Key: WFLY-13956 > URL: https://issues.redhat.com/browse/WFLY-13956 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 21.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Attachments: Screen Shot 2020-10-12 at 9.57.36 AM.png > > > When upgrading jboss-ejb-client to version 4.0.35.Final, we noticed some WildFly CI jobs sometimes hang when running {{TwoConnectorsEJBFailoverTestCase}}, causing 100+ (e.g., 466) tests to fail: > {code} > RemoteElytronSingleSignOnTestCase.testSessionTimeoutDestroysSSOorg.jboss.as.test.clustering.cluster.sso.remote > RemoteElytronSingleSignOnTestCase.testFormAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > RemoteElytronSingleSignOnTestCase.testNoAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > RemoteSingleSignOnTestCase.testSessionTimeoutDestroysSSOorg.jboss.as.test.clustering.cluster.sso.remote > RemoteSingleSignOnTestCase.testFormAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > RemoteSingleSignOnTestCase.testNoAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > CoarseHotRodPersistenceWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodPersistenceWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodPersistenceWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodSessionActivationTestCase.testorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseTransactionalHotRodWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseTransactionalHotRodWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote > CoarseTransactionalHotRodWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote > FineHotRodPersistenceWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > {code} > The error messages are like: > {code} > org.jboss.arquillian.container.spi.client.container.LifecycleException: The port 9990 is already in use. It means that either the server might be already running or there is another process using port 9990. > Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. > Please stop server (or another process) before running, change to another type of container (e.g. remote) or use jboss.socket.binding.port-offset variable to change the default port. > To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration > {code} > In a [successful CI job|https://ci.wildfly.org/buildConfiguration/WFPR/226438?], {{TwoConnectorsEJBFailoverTestCase}} runs 2 tests: {{testEJBClientUsingLegacyRemotingProtocol}} and {{testEJBClientUsingHttpUpgradeProtocol}}, each taking ~25 seconds to complete. See attached screenshot. > But in a [failed CI job|https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxJdk11/2...], filtering by {{TwoConnectorsEJBFailoverTestCase}} gives no result, which means the test hangs at {{testEJBClientUsingLegacyRemotingProtocol}} and so the test runner hasn't been able to collect the result from either test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFCORE-5155) A NullPointException was found in a wildfly-jar-maven-plugin test

by James Perkins (Jira)

James Perkins created WFCORE-5155: ------------------------------------- Summary: A NullPointException was found in a wildfly-jar-maven-plugin test Key: WFCORE-5155 URL: https://issues.redhat.com/browse/WFCORE-5155 Project: WildFly Core Issue Type: Bug Components: Logging Reporter: James Perkins Assignee: James Perkins WFCORE-5114 made a slight change with how the configuration API commits the logging changes. When upgrading the core version in wildfly-jar-maven-plugin a test failure occurred in the PR https://github.com/wildfly-extras/wildfly-jar-maven-plugin/pull/137. {code} Error: BootLoggingConfigurationTestCase.testSocketHandler:321->executeOperation:711 Operation { "operation" => "composite", "address" => [], "rollback-on-runtime-failure" => true, "steps" => [ { "operation" => "add", "address" => [ ("socket-binding-group" => "standard-sockets"), ("remote-destination-outbound-socket-binding" => "log-server") ], "host" => "127.0.0.1", "port" => 10514 }, { "operation" => "add", "address" => [ ("subsystem" => "logging"), ("socket-handler" => "socket") ], "named-formatter" => "PATTERN", "outbound-socket-binding-ref" => "log-server" }, { "operation" => "add-handler", "address" => [ ("subsystem" => "logging"), ("root-logger" => "ROOT") ], "name" => "socket" } ] } failed: {"WFLYCTL0062: Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"WFLYCTL0080: Failed services" => {"org.wildfly.logging.handler.\"org.wildfly.logging.handler.socket\"" => "Failed to start service Caused by: java.lang.NullPointerException"}}}} {code} The NPE is in the service where the {{DelayedHandler}} instance is used, but returns {{null}} for some reason. I could not reproduce this locally, however it did happen locally for me with the {{ascyn-handler}} in the test. This may be a way to reproduce this locally. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (SWSQE-1222) UI Automations - Overview - Create/Delete Traffic Policy

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1222?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1222. ----------------------------------- Resolution: Done > UI Automations - Overview - Create/Delete Traffic Policy > -------------------------------------------------------- > > Key: SWSQE-1222 > URL: https://issues.redhat.com/browse/SWSQE-1222 > Project: Kiali QE > Issue Type: Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1924 -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13956) TwoConnectorsEJBFailoverTestCase sometimes hangs when running with jboss-ejb-client 4.0.35

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13956?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-13956: ----------------------------------- [~tomekadamski] when running with previous version of jboss-ejb-client (4.0.34.Final), all passed: https://github.com/wildfly/wildfly/pull/13630 When running with 4.0.35.Final, there are always one or two CI jobs failed with the hang: https://github.com/wildfly/wildfly/pull/13632 I haven't been able to reproduce TwoConnectorsEJBFailoverTestCase hang locally. > TwoConnectorsEJBFailoverTestCase sometimes hangs when running with jboss-ejb-client 4.0.35 > ------------------------------------------------------------------------------------------ > > Key: WFLY-13956 > URL: https://issues.redhat.com/browse/WFLY-13956 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 21.0.0.Beta1 > Reporter: Cheng Fang > Assignee: Cheng Fang > Priority: Major > Attachments: Screen Shot 2020-10-12 at 9.57.36 AM.png > > > When upgrading jboss-ejb-client to version 4.0.35.Final, we noticed some WildFly CI jobs sometimes hang when running {{TwoConnectorsEJBFailoverTestCase}}, causing 100+ (e.g., 466) tests to fail: > {code} > RemoteElytronSingleSignOnTestCase.testSessionTimeoutDestroysSSOorg.jboss.as.test.clustering.cluster.sso.remote > RemoteElytronSingleSignOnTestCase.testFormAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > RemoteElytronSingleSignOnTestCase.testNoAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > RemoteSingleSignOnTestCase.testSessionTimeoutDestroysSSOorg.jboss.as.test.clustering.cluster.sso.remote > RemoteSingleSignOnTestCase.testFormAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > RemoteSingleSignOnTestCase.testNoAuthSingleSignOnorg.jboss.as.test.clustering.cluster.sso.remote > CoarseHotRodPersistenceWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodPersistenceWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodPersistenceWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodSessionActivationTestCase.testorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote > CoarseHotRodWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseTransactionalHotRodWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > CoarseTransactionalHotRodWebFailoverTestCase.testNonPrimaryOwnerorg.jboss.as.test.clustering.cluster.web.remote > CoarseTransactionalHotRodWebFailoverTestCase.testGracefulSimpleFailoverorg.jboss.as.test.clustering.cluster.web.remote > FineHotRodPersistenceWebFailoverTestCase.testGracefulUndeployFailoverorg.jboss.as.test.clustering.cluster.web.remote > {code} > The error messages are like: > {code} > org.jboss.arquillian.container.spi.client.container.LifecycleException: The port 9990 is already in use. It means that either the server might be already running or there is another process using port 9990. > Managed containers do not support connecting to running server instances due to the possible harmful effect of connecting to the wrong server. > Please stop server (or another process) before running, change to another type of container (e.g. remote) or use jboss.socket.binding.port-offset variable to change the default port. > To disable this check and allow Arquillian to connect to a running server, set allowConnectingToRunningServer to true in the container configuration > {code} > In a [successful CI job|https://ci.wildfly.org/buildConfiguration/WFPR/226438?], {{TwoConnectorsEJBFailoverTestCase}} runs 2 tests: {{testEJBClientUsingLegacyRemotingProtocol}} and {{testEJBClientUsingHttpUpgradeProtocol}}, each taking ~25 seconds to complete. See attached screenshot. > But in a [failed CI job|https://ci.wildfly.org/buildConfiguration/WF_PullRequest_LinuxJdk11/2...], filtering by {{TwoConnectorsEJBFailoverTestCase}} gives no result, which means the test hangs at {{testEJBClientUsingLegacyRemotingProtocol}} and so the test runner hasn't been able to collect the result from either test. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13960) i used this plaform to pay money from my acct to airtel network the debited but i did not see in my airtel account

by Brian Stansberry (Jira)

[ https://issues.redhat.com/browse/WFLY-13960?page=com.atlassian.jira.plugi... ] Brian Stansberry closed WFLY-13960. ----------------------------------- Resolution: Rejected The WildFly project does not provide a platform for sending money to people. This problem should be reported to whoever is providing the service you used. Perhaps they built their service on top of WildFly but they are the ones to talk to. > i used this plaform to pay money from my acct to airtel network the debited but i did not see in my airtel account > ------------------------------------------------------------------------------------------------------------------ > > Key: WFLY-13960 > URL: https://issues.redhat.com/browse/WFLY-13960 > Project: WildFly > Issue Type: Feature Request > Reporter: philip nwabuking > Assignee: Brian Stansberry > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

[Red Hat JIRA] (WFLY-13960) i used this plaform to pay money from my acct to airtel network the debited but i did not see in my airtel account

by philip nwabuking (Jira)

philip nwabuking created WFLY-13960: --------------------------------------- Summary: i used this plaform to pay money from my acct to airtel network the debited but i did not see in my airtel account Key: WFLY-13960 URL: https://issues.redhat.com/browse/WFLY-13960 Project: WildFly Issue Type: Feature Request Reporter: philip nwabuking Assignee: Brian Stansberry -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 9 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2020