April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13126) Refactor EJB client affinity processing

by Cheng Fang (Jira)

[ https://issues.redhat.com/browse/WFLY-13126?page=com.atlassian.jira.plugi... ] Cheng Fang commented on WFLY-13126: ----------------------------------- [~rchakrab] this is a major refactoring and Richard has been working on it. [~rachmato] can you link the Analysis Document PR (which should contain more details)? > Refactor EJB client affinity processing > --------------------------------------- > > Key: WFLY-13126 > URL: https://issues.redhat.com/browse/WFLY-13126 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Cheng Fang > Assignee: Richard Achmatowicz > Priority: Major > Labels: EAP-CD20 > > Refactor of jboss-ejb-client internal operation: change the way in which proxy affinity (an object that decides on which node invocation should be performed) is determined. Instead of calculating it on client side we would let server set the affinity when necessary and propagate it to the client. > This refactor is supposed to reduce the complexity of jboss-ejb-client code and as a result, make it significantly easier to maintain. Richard has prepared a comprehensive document describing the suggested modifications: https://mojo.redhat.com/docs/DOC-1204767 > Parallelly, the test suite has to be refactored to make it compatible with the new algorithm and to provide broad coverage of jboss-ejb-client operation. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11442) Remove unused dependencies from org.jboss.as.ejb3

by Ranabir Chakraborty (Jira)

[ https://issues.redhat.com/browse/WFLY-11442?page=com.atlassian.jira.plugi... ] Ranabir Chakraborty updated WFLY-11442: --------------------------------------- Git Pull Request: https://github.com/wildfly/wildfly/pull/13164 > Remove unused dependencies from org.jboss.as.ejb3 > ------------------------------------------------- > > Key: WFLY-11442 > URL: https://issues.redhat.com/browse/WFLY-11442 > Project: WildFly > Issue Type: Bug > Components: Server > Reporter: Yeray Borges Santana > Assignee: Ranabir Chakraborty > Priority: Major > > Initial analisys checking only first level dependencies from the resource exposed by {{org.jboss.as.ejb3}} shows that these dependencies are being unused: > * org.jboss.jts > * org.wildfly.security.elytron-web.undertow-server > * org.jboss.as.weld > * org.wildfly.clustering.marshalling.spi > * org.wildfly.clustering.marshalling.api > * org.wildfly.client.config > * org.hibernate > The task here is verify that they are not used by any other machanism besides of being a first level dependency. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2463) TransferQueueBundler: Message to stopped node blocks the bundler thread

by Dan Berindei (Jira)

[ https://issues.redhat.com/browse/JGRP-2463?page=com.atlassian.jira.plugin... ] Dan Berindei commented on JGRP-2463: ------------------------------------ I missed those {{try..catch}} blocks, but perhaps we should have log exceptions in {{TransferQueueBundler.run()}} as well, in case there's an exception elsewhere? Looking again at the logs from KEYCLOAK-13310, {{UNICAST3}} isn't logging any message except for resending the {{LEAVE_RSP}}, so perhaps the problem is somewhere else. > TransferQueueBundler: Message to stopped node blocks the bundler thread > ----------------------------------------------------------------------- > > Key: JGRP-2463 > URL: https://issues.redhat.com/browse/JGRP-2463 > Project: JGroups > Issue Type: Bug > Affects Versions: 4.2.1 > Reporter: Dan Berindei > Assignee: Bela Ban > Priority: Major > Fix For: 4.2.2, 5.0.0.Alpha4 > > > {{TransferQueueBundler}} sends all the messages from a single thread. When one of the {{TP.doSend()}} calls blocks, the bundler thread no longer makes any progress, and it doesn't send messages to any destination, even if {{TP.doSend()}} is only slow for one particular destination. > One example is when sending a message to a stopped node, e.g. the coordinator sending a {{LEAVE_RSP}} after the leaver has already stopped. The bundler thread calls {{TP.doSend()}}, the connection no longer exists, so it ends up calling {{BaseServer.createConnection()}}. If the stopped node's machine is no longer up or it is configured to drop messages to closed ports, the connection open blocks the bundler thread for {{TCP.sock_conn_timeout}}(default: 2s). > {{UNICAST3}} also retransmits the highest sent message every {{UNICAST3.xmit_interval}} (default: 500ms), for {{UNICAST3.max_retransmit_time}}(default: 1 min), so the bundler thread will block more than once for the same message. > I assume the bundler thread will also block if the transport is {{TCP}}, one of the destinations is overloaded, and the TCP connection's send buffer is full. Normally applications try to spread the workload evenly among members, but e.g. with RELAY2 not all the members will be site masters. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1101) Automate DR to Service Link

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1101?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan updated SWSQE-1101: ---------------------------------- Summary: Automate DR to Service Link (was: Automate VS to Gateway Link) Description: https://github.com/kiali/kiali-ui/pull/1706 (was: Verify the link and verify that in a case of "*" wildcards there is no link set.) > Automate DR to Service Link > --------------------------- > > Key: SWSQE-1101 > URL: https://issues.redhat.com/browse/SWSQE-1101 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > https://github.com/kiali/kiali-ui/pull/1706 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-13318) Add a "Smoke" JWT test case to use as a basis for further tests.

by Darran Lofthouse (Jira)

Darran Lofthouse created WFLY-13318: --------------------------------------- Summary: Add a "Smoke" JWT test case to use as a basis for further tests. Key: WFLY-13318 URL: https://issues.redhat.com/browse/WFLY-13318 Project: WildFly Issue Type: Task Components: MP JWT, Test Suite Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 20.0.0.Beta1 -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12899) Failing JMXPropertyEditorsTestCase in 18.0.0.Final

by Bartosz Baranowski (Jira)

[ https://issues.redhat.com/browse/WFLY-12899?page=com.atlassian.jira.plugi... ] Bartosz Baranowski commented on WFLY-12899: ------------------------------------------- Made simple change. I dont like it, but it might do the job. ( There seems to be no way to do this inside of test, atleast Arq guys went silent) > Failing JMXPropertyEditorsTestCase in 18.0.0.Final > -------------------------------------------------- > > Key: WFLY-12899 > URL: https://issues.redhat.com/browse/WFLY-12899 > Project: WildFly > Issue Type: Bug > Components: Test Suite > Affects Versions: 18.0.0.Final > Reporter: James Crowley > Assignee: Bartosz Baranowski > Priority: Major > > When calling "./mvnw install -DallTests", it gets up to the JMXPropertyEditorsTestCase and fails with this error, "Caused by: java.lang.IllegalStateException: Failed to resolve expression: env.USER"}}}}". > Looking at the source code for the test [here|https://github.com/wildfly/wildfly/blob/1bf993be72b570a0c780a58ba05c...], it looks like USER is suppose to be defined by USER_SYS_PROP. > I am not sure what the problem is but I know it is failing somewhere in the above test. > You can see the full log in the in Adopt's test [here|https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1436/conso...]. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-1101) Automate VS to Gateway Link

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1101?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan reassigned SWSQE-1101: ------------------------------------- Assignee: Hayk Hovsepyan > Automate VS to Gateway Link > --------------------------- > > Key: SWSQE-1101 > URL: https://issues.redhat.com/browse/SWSQE-1101 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Verify the link and verify that in a case of "*" wildcards there is no link set. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2402) SOS report

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2402?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2402: --------------------------- Description: Add the ability to dump the most important attributes to a file / log (configurable), e.g.: * Max threads * Number of rejected messages * Size of retransmission tables (NAKACK2, UNICAST3) This should be done periodically (e.g. every 15 minutes). This log should be enabled by default, e.g. in Infinispan. These files can then be sent to support via an SOS report. This can be used to diagnose issues by telling the customer to invoke this command and attach the resulting file to a ticket. was: Add the ability to dump the most important attributes to a file / log (configurable), e.g.: * Max threads * Number of rejected messages * Size of retransmission tables (NAKACK2, UNICAST3) This can be used to diagnose issues by telling the customer to invoke this command and attach the resulting file to a ticket > SOS report > ---------- > > Key: JGRP-2402 > URL: https://issues.redhat.com/browse/JGRP-2402 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.2, 5.0.0.Alpha4 > > > Add the ability to dump the most important attributes to a file / log (configurable), e.g.: > * Max threads > * Number of rejected messages > * Size of retransmission tables (NAKACK2, UNICAST3) > This should be done periodically (e.g. every 15 minutes). This log should be enabled by default, e.g. in Infinispan. > These files can then be sent to support via an SOS report. > This can be used to diagnose issues by telling the customer to invoke this command and attach the resulting file to a ticket. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2403) Dump information in panic scenarios

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2403?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2403: --------------------------- Description: When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. was: When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. Also dump the most important information to another log (file) periodically (e.g. every 15 minutes). This log should be enabled by default, e.g. in Infinispan. These files can be sent to support via an SOS report. > Dump information in panic scenarios > ----------------------------------- > > Key: JGRP-2403 > URL: https://issues.redhat.com/browse/JGRP-2403 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.2.2, 5.0.0.Alpha4 > > > When there is a panic situation (e.g. thread pool exhausted), dump information (e.g. including a thread dump) to a file at FATAL level. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JGRP-2404) Better configuration sanity checks

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2404?page=com.atlassian.jira.plugin... ] Bela Ban deleted JGRP-2404: --------------------------- > Better configuration sanity checks > ---------------------------------- > > Key: JGRP-2404 > URL: https://issues.redhat.com/browse/JGRP-2404 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > > Investigate whether more sanity checks can be applied to a configuration, e.g. missing UNICAST3 when TCP is configured etc. -- This message was sent by Atlassian Jira (v7.13.8#713008)

4 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2020