April 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3614) [DMN Designer] Maximize Event brings palette to expression editor

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3614?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3614: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Maximize Event brings palette to expression editor > ----------------------------------------------------------------- > > Key: DROOLS-3614 > URL: https://issues.redhat.com/browse/DROOLS-3614 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Jozef Marko > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screenshot from 2019-02-07 16-06-01.png > > > If the expression editor is maximized, there appears the palette, that should be shown just for diagram editor. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3273) [DMN Designer] Literal Expression: Font consistency

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3273?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3273: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Literal Expression: Font consistency > --------------------------------------------------- > > Key: DROOLS-3273 > URL: https://issues.redhat.com/browse/DROOLS-3273 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Affects Versions: 7.14.0.Final > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > Reported by [~tirelli]: > {quote} > Literal expressions currently use very different fonts and sizes when editing and when presenting. This looks really odd. Also, if the text of the literal expression goes past the border, it is presented clipped, without any visual clue that the expression was clipped. > {quote} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3634) [DMN Designer] Decision Table: OutputClause improvements

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3634?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3634: -------------------------------------- Assignee: Guilherme Gomes (was: Michael Anstis) > [DMN Designer] Decision Table: OutputClause improvements > -------------------------------------------------------- > > Key: DROOLS-3634 > URL: https://issues.redhat.com/browse/DROOLS-3634 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Michael Anstis > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > The {{Name}} and {{TypeRef}} of {{OutputClauses}} should be components of the parents {{TypeRef}}. For example a {{Decision}} has a {{TypeRef}} of {{tPerson}} that is a structure with fields {{age}}/{{number}} and {{name}}/{{string}}. {{OutputClause}}'s should be defined for {{age}}/{{number}} and {{name}}/{{string}} by default. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 commented on JGRP-2402: -------------------------------- This could be done in a separate protocol ({{SOS)}}? It would be configurable with a time interval and a list of protocols and their attributes to be fetched. This list could be updated by reading them from an external list. > 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)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3777) Receiving error IndexOutOfBoundsException on jdk11

by Michael Anstis (Jira)

[ https://issues.redhat.com/browse/DROOLS-3777?page=com.atlassian.jira.plug... ] Michael Anstis reassigned DROOLS-3777: -------------------------------------- Assignee: Daniel José dos Santos (was: Michael Anstis) > Receiving error IndexOutOfBoundsException on jdk11 > -------------------------------------------------- > > Key: DROOLS-3777 > URL: https://issues.redhat.com/browse/DROOLS-3777 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.20.0.Final > Environment: * jdk11 > * Apache Maven 3.5.4 (Red Hat 3.5.4-4) > Reporter: Yevgeniy Fomin > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools, jdk11 > Attachments: Error log array > > > There is IndexOutOfBoundsException on AddInputClauseCommandTest and AddOutputClauseCommandTest if they are run on jdk 11. The tests can be found in [module|https://github.com/kiegroup/kie-wb-common/tree/master/kie-wb-commo...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 1 month

1
0
0 / 0

[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)

6 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)

6 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)

6 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)

6 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)

6 years, 1 month

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 April 2020