November 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3406) find-non-progressing-operation doesn't return the blocking operation

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3406?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3406: ------------------------------------------ [~claudio4j] Does cancel-non-progressing-operation work? > find-non-progressing-operation doesn't return the blocking operation > -------------------------------------------------------------------- > > Key: WFCORE-3406 > URL: https://issues.jboss.org/browse/WFCORE-3406 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Claudio Miranda > Assignee: Brian Stansberry > > The find-non-progressing-operation operation of /core-service=management/service=management-operations doesn't return the operation id of a blocking operation on standalone. It works on domain mode. > To simulate the blocking operation, install the BlockingExtension from testsuite and call > {code} > /subsystem=blocker-test:block(block-point=MODEL,block-time=50000} > {code} > Open another jboss-cli.sh and call > {code} > /core-service=management/service=management-operations:find-non-progressing-operation > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (ELY-1435) Elytron BCrypt Mapper Not Working with jBCrypt

by Paul Carroll (JIRA)

Paul Carroll created ELY-1435: --------------------------------- Summary: Elytron BCrypt Mapper Not Working with jBCrypt Key: ELY-1435 URL: https://issues.jboss.org/browse/ELY-1435 Project: WildFly Elytron Issue Type: Bug Components: Passwords Affects Versions: 1.0.0.Final Environment: Wildfly 11.0.0.Final Windows Server 2008 JDK 9.0.1 Reporter: Paul Carroll Priority: Minor -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3406) find-non-progressing-operation doesn't return the blocking operation

by Claudio Miranda (JIRA)

Claudio Miranda created WFCORE-3406: --------------------------------------- Summary: find-non-progressing-operation doesn't return the blocking operation Key: WFCORE-3406 URL: https://issues.jboss.org/browse/WFCORE-3406 Project: WildFly Core Issue Type: Bug Components: Domain Management Reporter: Claudio Miranda Assignee: Brian Stansberry The find-non-progressing-operation operation of /core-service=management/service=management-operations doesn't return the operation id of a blocking operation on standalone. It works on domain mode. To simulate the blocking operation, install the BlockingExtension from testsuite and call {code} /subsystem=blocker-test:block(block-point=MODEL,block-time=50000} {code} Open another jboss-cli.sh and call {code} /core-service=management/service=management-operations:find-non-progressing-operation {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9525) [GSS](7.2.0) JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed

by Brad Maxwell (JIRA)

Brad Maxwell created WFLY-9525: ---------------------------------- Summary: [GSS](7.2.0) JPA deployer adding cross sub deployment dependencies when multiple persistence units deployed Key: WFLY-9525 URL: https://issues.jboss.org/browse/WFLY-9525 Project: WildFly Issue Type: Bug Components: JPA / Hibernate Affects Versions: 11.0.0.Final Reporter: Brad Maxwell Assignee: Scott Marlow If an ear contains two EJB sub deployments which each contain a Persistence Unit and a Stateless EJB which injects the PU that is in its jar using @PersistenceContext. There is a dependency being added where in the Stateless EJB from one deployment depends on the PU from the other jar. It appears this is happening after this bug fix WFLY-1531 {code} app.ear - ejb-with-pu1.jar - ejb-with-pu2.jar {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3405) The find-non-progressing-operation op is not accessible on a domain server

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-3405: ---------------------------------------- Summary: The find-non-progressing-operation op is not accessible on a domain server Key: WFCORE-3405 URL: https://issues.jboss.org/browse/WFCORE-3405 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 4.0.0.Alpha2 Reporter: Brian Stansberry Priority: Minor The find-non-progressing-operation op isn't marked as read-only or runtime-only (it's both) so it isn't accessible to external callers on a domain server. The related cancel-non-progressing-operation is marked runtime-only, so it's accessible. There's no point allow cancellation (which changes things) and not allowing a find (which just reads), so we should make the find visible. A requirement of fixing this though is there need to be new test methods added to OperationCancellationTest case that test finding and cancelling the op via the server resource and not just via the host. The existing testFindNonProgressingOperation() can just have a second "find" op added after the current one, and then new variants of testCancellingNonProgressingDomainRollout() and testFindNonProgressingDomainRollout() can be added that use the full server address for the find/cancel op. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2103) [Test Scenario] Test Numerical Types

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2103?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-2103: -------------------------------- Git Pull Request: https://github.com/kiegroup/drools-wb/pull/704 > [Test Scenario] Test Numerical Types > ------------------------------------ > > Key: DROOLS-2103 > URL: https://issues.jboss.org/browse/DROOLS-2103 > Project: Drools > Issue Type: Task > Components: Test Scenarios Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 7.5.0.Final > > > Prepare Some simple test scenario that will use numerical types like BigDecimal, BigInteger -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2105) [Test Scenario] Test Work Item Execution

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2105?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2105: ----------------------------------- Sprint: 2017 Week 43-44, 2017 Week 45-46 (was: 2017 Week 43-44) > [Test Scenario] Test Work Item Execution > ---------------------------------------- > > Key: DROOLS-2105 > URL: https://issues.jboss.org/browse/DROOLS-2105 > Project: Drools > Issue Type: Task > Components: Test Scenarios Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 7.5.0.Final > > > Prepare Some simple test scenario that will assert fired rules which execute some work item. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2106) [Test Scenario] Test RuleAttributes

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2106?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2106: ----------------------------------- Sprint: 2017 Week 43-44, 2017 Week 45-46 (was: 2017 Week 43-44) > [Test Scenario] Test RuleAttributes > ----------------------------------- > > Key: DROOLS-2106 > URL: https://issues.jboss.org/browse/DROOLS-2106 > Project: Drools > Issue Type: Task > Components: Test Scenarios Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 7.5.0.Final > > > Prepare Some simple test scenario that will assert fired rules. Concentrate on using some of attributes bellow in the prepared rules: > - enabled > - salience > - ruleflow group -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2108) [XLS Decision Table] Version is not refreshed after upload

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2108?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2108: ----------------------------------- Sprint: 2017 Week 43-44, 2017 Week 45-46 (was: 2017 Week 43-44) > [XLS Decision Table] Version is not refreshed after upload > ---------------------------------------------------------- > > Key: DROOLS-2108 > URL: https://issues.jboss.org/browse/DROOLS-2108 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > > User can upload new version of xls decision table, however the toolbar menu with version is not refreshed. User has to reopen the editor to see correct (up to date) list of versions. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2109) [XLS Decision Table] New Asset Dialogue misses descriptions

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2109?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-2109: ----------------------------------- Sprint: 2017 Week 43-44, 2017 Week 45-46 (was: 2017 Week 43-44) > [XLS Decision Table] New Asset Dialogue misses descriptions > ----------------------------------------------------------- > > Key: DROOLS-2109 > URL: https://issues.jboss.org/browse/DROOLS-2109 > Project: Drools > Issue Type: Bug > Components: XLS Decision Table Editor > Affects Versions: 7.5.0.Final > Reporter: Jozef Marko > Assignee: Jozef Marko > Attachments: Screenshot from 2017-11-03 10-20-21.png > > > The attached dialogue shows missing descriptions for table format and file selector. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 8 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 November 2017