January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4727) Unclear message when user tries to bind a fact on the Background tab

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4727?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4727: ------------------------------- Story Points: (was: 1) > Unclear message when user tries to bind a fact on the Background tab > -------------------------------------------------------------------- > > Key: DROOLS-4727 > URL: https://issues.redhat.com/browse/DROOLS-4727 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bind.webm > > > See the attached video. There is confusing message when user bind a fact on Background tab and tries to continue work with the editor. The current message is like _Can not read GJg undefined property_. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4727) Unclear message when user tries to bind a fact on the Background tab

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4727?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4727: ------------------------------- Story Points: 1 > Unclear message when user tries to bind a fact on the Background tab > -------------------------------------------------------------------- > > Key: DROOLS-4727 > URL: https://issues.redhat.com/browse/DROOLS-4727 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bind.webm > > > See the attached video. There is confusing message when user bind a fact on Background tab and tries to continue work with the editor. The current message is like _Can not read GJg undefined property_. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4727) Unclear message when user tries to bind a fact on the Background tab

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4727?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4727: ------------------------------------ [~jomarko] No reproducible in Master: it's not possibile to rename a header cell in Background grid. Can you please double check it? > Unclear message when user tries to bind a fact on the Background tab > -------------------------------------------------------------------- > > Key: DROOLS-4727 > URL: https://issues.redhat.com/browse/DROOLS-4727 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bind.webm > > > See the attached video. There is confusing message when user bind a fact on Background tab and tries to continue work with the editor. The current message is like _Can not read GJg undefined property_. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4727) Unclear message when user tries to bind a fact on the Background tab

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4727?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4727: ------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Unclear message when user tries to bind a fact on the Background tab > -------------------------------------------------------------------- > > Key: DROOLS-4727 > URL: https://issues.redhat.com/browse/DROOLS-4727 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bind.webm > > > See the attached video. There is confusing message when user bind a fact on Background tab and tries to continue work with the editor. The current message is like _Can not read GJg undefined property_. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4726) Bound facts from model are available on Background

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4726?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-4726: ------------------------------- Sprint: 2020 Week 04-06 (from Jan 20) > Bound facts from model are available on Background > -------------------------------------------------- > > Key: DROOLS-4726 > URL: https://issues.redhat.com/browse/DROOLS-4726 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bound-facts-on-background.webm > > > See the attached video. The bound facts from main model tab are available in the Background tab. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4726) Bound facts from model are available on Background

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4726?page=com.atlassian.jira.plug... ] Yeser Amer commented on DROOLS-4726: ------------------------------------ [~jomarko] No more reproducible, can you please confirm? > Bound facts from model are available on Background > -------------------------------------------------- > > Key: DROOLS-4726 > URL: https://issues.redhat.com/browse/DROOLS-4726 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bound-facts-on-background.webm > > > See the attached video. The bound facts from main model tab are available in the Background tab. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4726) Bound facts from model are available on Background

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-4726?page=com.atlassian.jira.plug... ] Yeser Amer edited comment on DROOLS-4726 at 1/28/20 10:37 AM: -------------------------------------------------------------- [~jomarko] No more reproducible in Master, can you please confirm? was (Author: yamer): [~jomarko] No more reproducible, can you please confirm? > Bound facts from model are available on Background > -------------------------------------------------- > > Key: DROOLS-4726 > URL: https://issues.redhat.com/browse/DROOLS-4726 > Project: Drools > Issue Type: Bug > Components: Scenario Simulation and Testing > Affects Versions: 7.30.0.Final > Reporter: Jozef Marko > Assignee: Yeser Amer > Priority: Major > Labels: ScenarioSimulation, drools-tools > Attachments: bound-facts-on-background.webm > > > See the attached video. The bound facts from main model tab are available in the Background tab. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12948) When shutting down, JDBC_PING tries to use a closed connection

by Aliaksei Makarevich (Jira)

[ https://issues.redhat.com/browse/WFLY-12948?page=com.atlassian.jira.plugi... ] Aliaksei Makarevich commented on WFLY-12948: -------------------------------------------- Hello [~rhusar] [~sebastian.laskawiec] Unfortunatelly this didn't help. I wrote a comment about it at [KEYCLOAK-11148 JDBC_PING example with Maria DB #204|https://github.com/keycloak/keycloak-containers/pull/204#issuecomment-575152116] > When shutting down, JDBC_PING tries to use a closed connection > -------------------------------------------------------------- > > Key: WFLY-12948 > URL: https://issues.redhat.com/browse/WFLY-12948 > Project: WildFly > Issue Type: Bug > Components: Clustering > Reporter: Sebastian Laskawiec > Assignee: Radoslav Husar > Priority: Minor > > One of the Keycloak demos use {{JDBC_PING}} as discovery protocol (see [here|https://github.com/keycloak/keycloak-containers/blob/master/docker-c...]). One of our users noticed (and I confirmed it) that when shutting Keycloak down, {{JDBC_PING}} tries to use a closed Connection Factory: > {code} > keycloak_2 | 09:14:34,807 ERROR [org.jgroups.protocols.JDBC_PING] (ServerService Thread Pool -- 23) JGRP000115: Could not open connection to database: java.sql.SQLException: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:jboss/datasources/KeycloakDS > keycloak_2 | at org.jboss.ironjacamar.jdbcadapters@1.4.17.Final//org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:159) > keycloak_2 | at org.jboss.as.connector@18.0.1.Final//org.jboss.as.connector.subsystems.datasources.WildFlyDataSource.getConnection(WildFlyDataSource.java:64) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.protocols.JDBC_PING.getConnection(JDBC_PING.java:310) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.protocols.JDBC_PING.clearTable(JDBC_PING.java:361) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.protocols.JDBC_PING.removeAll(JDBC_PING.java:190) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.protocols.JDBC_PING.stop(JDBC_PING.java:119) > keycloak_2 | at java.base/java.util.ArrayList.forEach(ArrayList.java:1540) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:906) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.JChannel.stopStack(JChannel.java:1076) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.JChannel._close(JChannel.java:1063) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.JChannel.close(JChannel.java:454) > keycloak_2 | at org.jboss.as.clustering.jgroups@18.0.1.Final//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.accept(ChannelServiceConfigurator.java:132) > keycloak_2 | at org.jboss.as.clustering.jgroups@18.0.1.Final//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.accept(ChannelServiceConfigurator.java:58) > keycloak_2 | at org.wildfly.clustering.service@18.0.1.Final//org.wildfly.clustering.service.FunctionalService.stop(FunctionalService.java:77) > keycloak_2 | at org.wildfly.clustering.service@18.0.1.Final//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$stop$1(AsyncServiceConfigurator.java:142) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > keycloak_2 | at java.base/java.lang.Thread.run(Thread.java:834) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > keycloak_2 | Caused by: javax.resource.ResourceException: IJ000470: You are trying to use a connection factory that has been shut down: java:jboss/datasources/KeycloakDS > keycloak_2 | at org.jboss.ironjacamar.impl@1.4.17.Final//org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:777) > keycloak_2 | at org.jboss.ironjacamar.jdbcadapters@1.4.17.Final//org.jboss.jca.adapters.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:151) > keycloak_2 | ... 20 more > keycloak_2 | 09:14:34,807 ERROR [org.jgroups.JChannel] (ServerService Thread Pool -- 23) JGRP000020: failed destroying the protocol stack: java.lang.NullPointerException > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.protocols.JDBC_PING.clearTable(JDBC_PING.java:362) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.protocols.JDBC_PING.removeAll(JDBC_PING.java:190) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.protocols.JDBC_PING.stop(JDBC_PING.java:119) > keycloak_2 | at java.base/java.util.ArrayList.forEach(ArrayList.java:1540) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.stack.ProtocolStack.stopStack(ProtocolStack.java:906) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.JChannel.stopStack(JChannel.java:1076) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.JChannel._close(JChannel.java:1063) > keycloak_2 | at org.jgroups@4.1.4.Final//org.jgroups.JChannel.close(JChannel.java:454) > keycloak_2 | at org.jboss.as.clustering.jgroups@18.0.1.Final//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.accept(ChannelServiceConfigurator.java:132) > keycloak_2 | at org.jboss.as.clustering.jgroups@18.0.1.Final//org.jboss.as.clustering.jgroups.subsystem.ChannelServiceConfigurator.accept(ChannelServiceConfigurator.java:58) > keycloak_2 | at org.wildfly.clustering.service@18.0.1.Final//org.wildfly.clustering.service.FunctionalService.stop(FunctionalService.java:77) > keycloak_2 | at org.wildfly.clustering.service@18.0.1.Final//org.wildfly.clustering.service.AsyncServiceConfigurator$AsyncService.lambda$stop$1(AsyncServiceConfigurator.java:142) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > keycloak_2 | at java.base/java.lang.Thread.run(Thread.java:834) > keycloak_2 | at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485) > keycloak_2 | 09:14:34,819 INFO [org.jboss.as] (MSC service thread 1-5) WFLYSRV0050: Keycloak 8.0.1 (WildFly Core 10.0.3.Final) stopped in 160ms > keycloak_2 | *** JBossAS process (510) received TERM signal *** > {code} > More information: > * Generated {{standalone-ha.xml}} used by the example: https://gist.github.com/slaskawi/7cb8eefdfa3e27f7c0f0e62e26bb0216 > * Full logs from Docker Compose: https://gist.github.com/slaskawi/239a2a1ea83d7bc98c8d0d884480c77e -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2436) Diagnostics: enable TCP by default

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2436?page=com.atlassian.jira.plugin... ] Bela Ban resolved JGRP-2436. ---------------------------- Resolution: Done > Diagnostics: enable TCP by default > ---------------------------------- > > Key: JGRP-2436 > URL: https://issues.redhat.com/browse/JGRP-2436 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0 > > > Set {{diag_enable_tcp}} to true by default; a lot of deployments happen in the cloud today, and if we don't enable this, {{probe -addr ADDR}} will only return a response from the local member. > This will open a UDP *and* TCP diagnostics socket, but if {{enable_diagnostics}} is false, then no socket will be opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2436) Diagnostics: enable TCP by default

by Bela Ban (Jira)

[ https://issues.redhat.com/browse/JGRP-2436?page=com.atlassian.jira.plugin... ] Bela Ban updated JGRP-2436: --------------------------- Description: Set {{diag_enable_tcp}} to true by default; a lot of deployments happen in the cloud today, and if we don't enable this, {{probe -addr ADDR}} will only return a response from the local member. This will open a UDP *and* TCP diagnostics socket, but if {{enable_diagnostics}} is false, then no socket will be opened was: Set {{diag_enable_tcp}} to true by default; a lot of deployments happen in the cloud today, and if we don't enable this, {{probe -addr ADDR}} will only retturn a response from the local member. This will open a UDP *and* TCP diagnostics socket, but if {{enable_diagnostics}} is false, then no socket will be opened > Diagnostics: enable TCP by default > ---------------------------------- > > Key: JGRP-2436 > URL: https://issues.redhat.com/browse/JGRP-2436 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 5.0, 4.2.0 > > > Set {{diag_enable_tcp}} to true by default; a lot of deployments happen in the cloud today, and if we don't enable this, {{probe -addr ADDR}} will only return a response from the local member. > This will open a UDP *and* TCP diagnostics socket, but if {{enable_diagnostics}} is false, then no socket will be opened -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 3 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 January 2020