October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1801) [Guided Decision Table] Work Item Parameter values are not initialized properly

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1801?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1801. ------------------------------- Release Notes Text: No more reproducible due to GUVNOR-3143 Fix Version/s: 7.5.0.Final Resolution: Cannot Reproduce Bug > [Guided Decision Table] Work Item Parameter values are not initialized properly > ------------------------------------------------------------------------------- > > Key: DROOLS-1801 > URL: https://issues.jboss.org/browse/DROOLS-1801 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Affects Versions: 7.1.0.Beta2 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > Fix For: 7.5.0.Final > > > Is user wants to execute the same Work Item multiple times, he must always clear the parameter values from previous time. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1788) [Guided Decision Table] "Entry point" and "Binding" cannot be updated

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1788?page=com.atlassian.jira.plugi... ] Jozef Marko resolved DROOLS-1788. --------------------------------- Fix Version/s: 7.5.0.Final Resolution: Done > [Guided Decision Table] "Entry point" and "Binding" cannot be updated > --------------------------------------------------------------------- > > Key: DROOLS-1788 > URL: https://issues.jboss.org/browse/DROOLS-1788 > Project: Drools > Issue Type: Bug > Components: Guided Decision Table Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Fix For: 7.5.0.Final > > Attachments: bug-1.gif > > > It's impossible to update the "Entry point" and "Binding" fields in a "Condition Column". See: > !bug-1.gif|thumbnail! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2000) Test Scenario: Not possible to use a global

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2000?page=com.atlassian.jira.plugi... ] Jozef Marko reassigned DROOLS-2000: ----------------------------------- Assignee: Jozef Marko > Test Scenario: Not possible to use a global > ------------------------------------------- > > Key: DROOLS-2000 > URL: https://issues.jboss.org/browse/DROOLS-2000 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Jozef Marko > Priority: Blocker > > Tried with two globals. One added into a DRL file and another added with menu New->Global Variable(s). > Neither of these two show up in the Test Scenario popup. Tried a full build, reopening the test scenario and even restarting the workbench. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1993. ------------------------------- Resolution: Cannot Reproduce Bug > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Fix For: 7.5.0.Final > > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Jozef Marko closed DROOLS-1993. ------------------------------- Release Notes Text: Seems to be no more reproducible. Resolution: Cannot Reproduce Bug > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Jozef Marko reopened DROOLS-1993: --------------------------------- > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Fix For: 7.5.0.Final > > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1993) Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1993?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-1993: -------------------------------- Fix Version/s: 7.5.0.Final > Test Scenarios: Boolean dropdown does not set the default value, even when it is shown for the user > --------------------------------------------------------------------------------------------------- > > Key: DROOLS-1993 > URL: https://issues.jboss.org/browse/DROOLS-1993 > Project: Drools > Issue Type: Bug > Components: Test Scenarios Editor > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Critical > Fix For: 7.5.0.Final > > > # Open "Are they old enough" > # Add new expect for 'application'. "true" is selected in the dropdown > # Run the scenario. Log shows that "" was compared instead of "true" -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2228) ASYM_ENCRYPT: test with encrypt_entire_msg=true

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2228?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2228: -------------------------------- The attached {{asym-encrypt.xml}} dated Nov 1 is supposed to reproduce the issue with {{encrypt_entire_msg == true}}. > ASYM_ENCRYPT: test with encrypt_entire_msg=true > ----------------------------------------------- > > Key: JGRP-2228 > URL: https://issues.jboss.org/browse/JGRP-2228 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.9 > > Attachments: asym-encrypt.xml, asym-encrypt.xml > > > * Start a few nodes with {{ASYM_ENCRYPT}} and {{encrypt_entire_msg}} set to {{true}} > * Kill and restart a member > * Apparently, restarting is not possible, as the new member won't be able to join the cluster > -> Verify this is true and - if yes - fix it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2228) ASYM_ENCRYPT: test with encrypt_entire_msg=true

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2228?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2228: --------------------------- Attachment: asym-encrypt.xml > ASYM_ENCRYPT: test with encrypt_entire_msg=true > ----------------------------------------------- > > Key: JGRP-2228 > URL: https://issues.jboss.org/browse/JGRP-2228 > Project: JGroups > Issue Type: Task > Reporter: Bela Ban > Assignee: Bela Ban > Fix For: 4.0.9 > > Attachments: asym-encrypt.xml, asym-encrypt.xml > > > * Start a few nodes with {{ASYM_ENCRYPT}} and {{encrypt_entire_msg}} set to {{true}} > * Kill and restart a member > * Apparently, restarting is not possible, as the new member won't be able to join the cluster > -> Verify this is true and - if yes - fix it -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9501) Container is not cleaning up container-managed JMSContext

by Jiri Ondrusek (JIRA)

[ https://issues.jboss.org/browse/WFLY-9501?page=com.atlassian.jira.plugin.... ] Jiri Ondrusek moved JBEAP-13666 to WFLY-9501: --------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9501 (was: JBEAP-13666) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: EE EJB JMS (was: EE) (was: EJB) (was: JMS) Affects Version/s: 12.0.0.Alpha1 (was: 7.0.0.GA) > Container is not cleaning up container-managed JMSContext > --------------------------------------------------------- > > Key: WFLY-9501 > URL: https://issues.jboss.org/browse/WFLY-9501 > Project: WildFly > Issue Type: Bug > Components: EE, EJB, JMS > Affects Versions: 12.0.0.Alpha1 > Environment: JBoss-EAP-7.0.0 > JDK 1.8 > Reporter: Jiri Ondrusek > Assignee: Jiri Ondrusek > > The container is not cleaning up container managed JMSContext, causing a connection leak. > The JMS 2.0 API doc[1] states the following : > <quote> > Applications running in the Java EE web and EJB containers may alternatively inject a JMSContext into their application using the @Inject annotation. A JMSContext that is created in this way is described as being container-managed. A container-managed JMSContext will be closed automatically by the container. > </quote> > However the JCA's CacheConnectionManager (CCM) complains a connection leak if the application didn't explicitly close the JMSContext, which is not required for container managed JMSContext. > [1] http://docs.oracle.com/javaee/7/api/javax/jms/JMSContext.html -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 5 months

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 October 2017