September 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3652: -------------------------------- Description: When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! p.s. this is the pop-over that needs to be updated to support Expression instead of Name. h3. Clarified behavior - "Enter" = apply and close in every case, even when the dropdown is focused (but not open) - "ESC" = close without apply in every case - "Enter" when dropdown is focused, apply and close was: When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! p.s. this is the pop-over that needs to be updated to support Expression instead of Name. > DMN popover - Enter to apply > ----------------------------- > > Key: DROOLS-3652 > URL: https://issues.jboss.org/browse/DROOLS-3652 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Daniel José dos Santos > Priority: Major > Labels: UX, drools-tools > Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png > > > When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. > !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! > p.s. this is the pop-over that needs to be updated to support Expression instead of Name. > h3. Clarified behavior > - "Enter" = apply and close in every case, even when the dropdown is focused (but not open) > - "ESC" = close without apply in every case > - "Enter" when dropdown is focused, apply and close -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3652) DMN popover - Enter to apply

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3652?page=com.atlassian.jira.plugi... ] Jozef Marko commented on DROOLS-3652: ------------------------------------- Ok, I read gchat discussion and updated the jira. > DMN popover - Enter to apply > ----------------------------- > > Key: DROOLS-3652 > URL: https://issues.jboss.org/browse/DROOLS-3652 > Project: Drools > Issue Type: Enhancement > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Daniel José dos Santos > Priority: Major > Labels: UX, drools-tools > Attachments: Screen Shot 2019-02-13 at 1.20.35 PM.png > > > When the user changes the field value (name in this example), it would be nice if hitting ENTER would apply the name, and take the focus highlight off. The other field is being applied dynamically, so the assumption is that this one is as well. > !Screen Shot 2019-02-13 at 1.20.35 PM.png|thumbnail! > p.s. this is the pop-over that needs to be updated to support Expression instead of Name. > h3. Clarified behavior > - "Enter" = apply and close in every case, even when the dropdown is focused (but not open) > - "ESC" = close without apply in every case > - "Enter" when dropdown is focused, apply and close -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4513) s2i build fails at KieServerContainerVerifier if multiple listeners are set

by Luca Molteni (Jira)

[ https://issues.jboss.org/browse/DROOLS-4513?page=com.atlassian.jira.plugi... ] Luca Molteni commented on DROOLS-4513: -------------------------------------- Perfect [~hiroko] [~filippe.spolti] can you confirm? Can you upload your reproducer that doesn't use Openshift? > s2i build fails at KieServerContainerVerifier if multiple listeners are set > ---------------------------------------------------------------------------- > > Key: DROOLS-4513 > URL: https://issues.jboss.org/browse/DROOLS-4513 > Project: Drools > Issue Type: Bug > Components: build, kie server > Affects Versions: 7.14.0.Final, 7.18.0.Final, 7.24.0.Final > Environment: OpenShift 3.11 with rhdm72-prod-immutable-kieserver.yaml/rhdm73-prod-immutable-kieserver.yaml > Reporter: Hiroko Miura > Assignee: Ant Stephenson > Priority: Major > Labels: support > Attachments: ruleTest.zip > > > If multiple ksession are defined in kmodule.xml and Event Lister is set more than one ksession, s2i build fails at KieServerContainerVerifier with the following error. > {noformat} > [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT > java.lang.RuntimeException: Cannot find KieModule: com.redhat.gss:ruleTest:1.0.0-SNAPSHOT > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:186) > at org.drools.compiler.kie.builder.impl.KieServicesImpl.newKieContainer(KieServicesImpl.java:172) > at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:65) > at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:53) > at org.kie.server.services.impl.KieServerContainerVerifier.verify(KieServerContainerVerifier.java:40) > at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:119) > at org.kie.server.services.impl.KieServerContainerVerifier.main(KieServerContainerVerifier.java:101) > at org.jboss.modules.Module.run(Module.java:352) > at org.jboss.modules.Module.run(Module.java:320) > at org.jboss.modules.Main.main(Main.java:593) > [main] ERROR org.kie.server.services.impl.KieServerContainerVerifier - com.redhat.gss:ruleTest:1.0.0-SNAPSHOT not verified. > ERROR Aborting due to error code 1 from kie server container verification > {noformat} -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2382) Jgroup version 4.0.13.Final.jar is causing memory leaks

by Rashmi Acharya (Jira)

[ https://issues.jboss.org/browse/JGRP-2382?page=com.atlassian.jira.plugin.... ] Rashmi Acharya commented on JGRP-2382: -------------------------------------- Thanks Bela for the quick response.. I will inform our customer to upload the logs and required heap file for further analysis.. >From heap file, what I see that leaks are coming from NAKACK2 protocol with UNICAST3 settings. > Jgroup version 4.0.13.Final.jar is causing memory leaks > ------------------------------------------------------- > > Key: JGRP-2382 > URL: https://issues.jboss.org/browse/JGRP-2382 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 4.0.13 > Environment: AIX machine 7.1 with JDK 1.8 > Reporter: Rashmi Acharya > Assignee: Bela Ban > Priority: Major > > We are observing a constant memory growth and leak with JGroup version 4.0.13 .. > One of our customer is having two node cluster environment and in one node we are observing org.Group.Messages which contain org.groups.Header and org.groups.Stack.ipAddress objects.. these are not getting cleared from memory.. > We dont see any exception related to Jgroups from logs and but it is causing a gradual emory growth and OOM. > Here is the Jgroups cluster configuration we have: > dynamic.cluster.property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT2;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000" /> > <FD_ALL timeout="20000" interval="15000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48" /> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000"/> > <pbcast.GMS print_local_addr="true" join_timeout="15000" /> > </config> > ================================= > dynamic.cluster.distribution_property_string > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_port="&MULTICAST_NODE_PORT1;" /> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_SOCK/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3/> > <pbcast.STABLE desired_avg_gossip="20000" max_bytes="0" stability_delay="1000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > </config> > ================================ > dynamic.cluster.lock.protocolStack > <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="urn:org:jgroups" xsi:schemaLocation="urn:org:jgroups http://www.jgroups.org/schema/jgroups.xsd"> > <TCP bind_addr="&HOST_ADDR;" bind_port="&MULTICAST_NODE_PORT3;"/> > <TCPPING async_discovery="true" initial_hosts="&CLUSTER_INITIAL_HOSTS;" port_range="0" send_cache_on_join="true"/> > <MERGE3 min_interval="3000" max_interval="5000"/> > <FD_ALL timeout="20000" interval="5000"/> > <FD timeout="5000" max_tries="48"/> > <VERIFY_SUSPECT timeout="1500"/> > <BARRIER/> > <pbcast.NAKACK2 use_mcast_xmit="false" discard_delivered_msgs="true"/> > <UNICAST3 /> <pbcast.STABLE desired_avg_gossip="20000" /> > <pbcast.GMS print_local_addr="true" join_timeout="5000"/> > <FRAG2 frag_size="8096"/> > <CENTRAL_LOCK2/> > </config> -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4545) GDST V&V: Clean up situations where the webworker fails

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4545?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4545: -------------------------------- Labels: drools-tools (was: ) > GDST V&V: Clean up situations where the webworker fails > ------------------------------------------------------- > > Key: DROOLS-4545 > URL: https://issues.jboss.org/browse/DROOLS-4545 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Problem: If the project does not compile, you can edit the table, but editing fires errors in the Verifier Webworker. This is because the Verifier needs a project that compiles and creates a valid DMO. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4545) GDST V&V: Clean up situations where the webworker fails

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-4545?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-4545: -------------------------------- Tester: Jozef Marko > GDST V&V: Clean up situations where the webworker fails > ------------------------------------------------------- > > Key: DROOLS-4545 > URL: https://issues.jboss.org/browse/DROOLS-4545 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: drools-tools > > Problem: If the project does not compile, you can edit the table, but editing fires errors in the Verifier Webworker. This is because the Verifier needs a project that compiles and creates a valid DMO. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1880) Release WildFly Elytron 1.10.2.Final

by Darran Lofthouse (Jira)

Darran Lofthouse created ELY-1880: ------------------------------------- Summary: Release WildFly Elytron 1.10.2.Final Key: ELY-1880 URL: https://issues.jboss.org/browse/ELY-1880 Project: WildFly Elytron Issue Type: Release Reporter: Darran Lofthouse Assignee: Darran Lofthouse Fix For: 1.10.2.CR1 -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4676) Upgrade jboss-modules from 1.9.1.Final to 1.9.2.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4676?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4676: ---------------------------------- Description: Upgrade {{org.jboss.modules:jboss-lmodules}} from 1.9.1.Final to 1.9.2.Final. This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. was: Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.14.Final to 2.1.15.Final. This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. > Upgrade jboss-modules from 1.9.1.Final to 1.9.2.Final > ----------------------------------------------------- > > Key: WFCORE-4676 > URL: https://issues.jboss.org/browse/WFCORE-4676 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > > Upgrade {{org.jboss.modules:jboss-lmodules}} from 1.9.1.Final to 1.9.2.Final. > This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4676) Upgrade jboss-modules from 1.9.1.Final to 1.9.2.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4676?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4676: ---------------------------------- Labels: OpenShift jdk11 (was: OpenShift) > Upgrade jboss-modules from 1.9.1.Final to 1.9.2.Final > ----------------------------------------------------- > > Key: WFCORE-4676 > URL: https://issues.jboss.org/browse/WFCORE-4676 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > > Upgrade {{org.jboss.modules:jboss-lmodules}} from 1.9.1.Final to 1.9.2.Final. > This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4675) Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFCORE-4675?page=com.atlassian.jira.plugi... ] James Perkins updated WFCORE-4675: ---------------------------------- Labels: OpenShift jsk11 (was: OpenShift) > Upgrade jboss-logmanager from 2.1.14.Final to 2.1.15.Final > ---------------------------------------------------------- > > Key: WFCORE-4675 > URL: https://issues.jboss.org/browse/WFCORE-4675 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Logging > Reporter: James Perkins > Assignee: James Perkins > Priority: Critical > Labels: OpenShift, jdk11 > > Upgrade {{org.jboss.logmanager:jboss-logmanager}} from 2.1.14.Final to 2.1.15.Final. > This is created as a critical issue as it can cause issues in OpenShift with Java 11 and custom handlers, formatters and as of WildFly 18/EAP CD18 filters. -- This message was sent by Atlassian Jira (v7.13.5#713005)

6 years, 10 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 September 2019