January 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1778) Enhanced Audit Logging - Feature parity with legacy audit logging

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1778?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1778: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Enhanced Audit Logging - Feature parity with legacy audit logging > ----------------------------------------------------------------- > > Key: ELY-1778 > URL: https://issues.redhat.com/browse/ELY-1778 > Project: WildFly Elytron > Issue Type: Feature Request > Components: Audit > Reporter: Justin Cook > Priority: Major > Fix For: 1.11.0.CR5 > > > This RFE for Enhanced Audit Logging in WildFly Elytron is for feature parity with legacy audit logging via: > * Additional audit events > * An "Audit" annotation -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1740) Clean up the 'wildfly-elytron-sasl' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1740?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1740: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Clean up the 'wildfly-elytron-sasl' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1740 > URL: https://issues.redhat.com/browse/ELY-1740 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha7, 1.11.0.CR5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1739) Clean up the 'wildfly-elytron-jaspi' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1739?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1739: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Clean up the 'wildfly-elytron-jaspi' module as it currently contains both public and private API > ------------------------------------------------------------------------------------------------ > > Key: ELY-1739 > URL: https://issues.redhat.com/browse/ELY-1739 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha7, 1.11.0.CR5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1745) The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration.

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1745?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1745: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1745 > URL: https://issues.redhat.com/browse/ELY-1745 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR5 > > > The NPE is due to the following code: - > {noformat} > } else if (callback instanceof AvailableRealmsCallback) { > Collection<String> names = stateRef.get().getMechanismConfiguration().getMechanismRealmNames(); > if (log.isTraceEnabled()) { > log.tracef("Handling AvailableRealmsCallback: realms = [%s]", String.join(", ", names)); > } > if (! names.isEmpty()) { > ((AvailableRealmsCallback) callback).setRealmNames(names.toArray(new String[names.size()])); > } > handleOne(callbacks, idx + 1); > {noformat} > If mechanism configuration is mandatory this should report an appropriate error, if not it should fallback to specifying an empty list. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1809) Update JAPICMP on a module by module basis

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1809?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1809: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Update JAPICMP on a module by module basis > ------------------------------------------ > > Key: ELY-1809 > URL: https://issues.redhat.com/browse/ELY-1809 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR5 > > > Each module should test it's own compatibility - however the compatible version should likely be defined in the root pom. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1842) Update the tool to support generating and exporting / importing a secret key to the credential store

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1842?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1842: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Update the tool to support generating and exporting / importing a secret key to the credential store > ---------------------------------------------------------------------------------------------------- > > Key: ELY-1842 > URL: https://issues.redhat.com/browse/ELY-1842 > Project: WildFly Elytron > Issue Type: Requirement > Components: Command-Line Tool, Credential Store > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR5 > > > In general the following options should be supported: - > * `--generate-secret-key` > * `--export-secret-key` > * `--import-secret-key` -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1749) Code review of WildFlyElytronProvider

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1749?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1749: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Code review of WildFlyElytronProvider > ------------------------------------- > > Key: ELY-1749 > URL: https://issues.redhat.com/browse/ELY-1749 > Project: WildFly Elytron > Issue Type: Task > Components: API / SPI > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.11.0.CR5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1765) Review authentication client dependencies on credential sources

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1765?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1765: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Review authentication client dependencies on credential sources > --------------------------------------------------------------- > > Key: ELY-1765 > URL: https://issues.redhat.com/browse/ELY-1765 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.11.0.CR5 > > > Could these credential sources be discoverable from java.security.Provider with a more generic configuration API? This could help break any dependency from authentication client to the implementation. > _In the opposite direction I think it is Ok for the impl to depend on the client._ -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1808) Undertake further review of all duplicate packages to ensure we can make unique

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1808?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1808: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Undertake further review of all duplicate packages to ensure we can make unique > ------------------------------------------------------------------------------- > > Key: ELY-1808 > URL: https://issues.redhat.com/browse/ELY-1808 > Project: WildFly Elytron > Issue Type: Task > Components: Build > Reporter: Darran Lofthouse > Priority: Blocker > Fix For: 1.11.0.CR5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1744) Remove use of java.security.acl APIs

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1744?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1744: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Remove use of java.security.acl APIs > ------------------------------------ > > Key: ELY-1744 > URL: https://issues.redhat.com/browse/ELY-1744 > Project: WildFly Elytron > Issue Type: Task > Components: Realms > Reporter: Darran Lofthouse > Priority: Critical > Fix For: 1.11.0.CR5 > > > The 'java.security.acls' packages has been deprecated and flagged for removal, this will be removed in Java 13 > https://bugs.openjdk.java.net/browse/JDK-8191138 > Within WildFly Elytron we only seem to use it in the JAAS security realm which I don't believe is used although likely is public API. I believe the use was to mirror some PicketBox behaviour. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1742) Clean up the 'wildfly-elytron-x500-cert' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1742?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1742: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Clean up the 'wildfly-elytron-x500-cert' module as it currently contains both public and private API > ---------------------------------------------------------------------------------------------------- > > Key: ELY-1742 > URL: https://issues.redhat.com/browse/ELY-1742 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha7, 1.11.0.CR5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1741) Clean up the 'wildfly-elytron-x500' module as it currently contains both public and private API

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1741?page=com.atlassian.jira.plugin.... ] Farah Juma updated ELY-1741: ---------------------------- Fix Version/s: 1.11.0.CR5 (was: 1.11.0.CR4) > Clean up the 'wildfly-elytron-x500' module as it currently contains both public and private API > ----------------------------------------------------------------------------------------------- > > Key: ELY-1741 > URL: https://issues.redhat.com/browse/ELY-1741 > Project: WildFly Elytron > Issue Type: Task > Reporter: Farah Juma > Priority: Major > Fix For: 2.0.0.Alpha7, 1.11.0.CR5 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1916) Release WildFly Elytron 1.11.0.CR4

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1916?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-1916. ----------------------------- Resolution: Done > Release WildFly Elytron 1.11.0.CR4 > ---------------------------------- > > Key: ELY-1916 > URL: https://issues.redhat.com/browse/ELY-1916 > Project: WildFly Elytron > Issue Type: Release > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Fix For: 1.11.0.CR4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1448) [XLS Decision Table] Integer values for Double attributes causes validation error

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-1448?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-1448. --------------------------------- Resolution: Won't Fix I reproduced the problem, but since the SpreadsheetCompiler is unaware of the underlying domain model, there is nothing we can do about it. In other words, in order to generate a drl that is compatible with the model, the SpreadsheetCompiler should know the type of the object accepted by the setter method and rewrite the consequence accordingly, but this is not possible because that compiler purely translate the xls into a drl without any knowledge of the actual classes used in the domain. That said I don't think this is a big issue since either changing the type accepted by the setter from Double to a primitive double or modifying the decision table to have doubles in the consequence's column fix the problem. > [XLS Decision Table] Integer values for Double attributes causes validation error > --------------------------------------------------------------------------------- > > Key: DROOLS-1448 > URL: https://issues.redhat.com/browse/DROOLS-1448 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Jozef Marko > Assignee: Mario Fusco > Priority: Minor > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > Attachments: Driver.java, ExamplePolicyPricing.xls, Policy.java, Screenshot from 2017-02-02 10-22-21.png > > > If the XLS decision contains Integer values for column ( attribute ) that is Double data type, then the XLS decision table is not validated successfully. After conversion to guided decision table is the table validated successfully. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4777) Upgrade JBoss Remoting from 5.0.16 to 5.0.17

by Darran Lofthouse (Jira)

[ https://issues.redhat.com/browse/WFCORE-4777?page=com.atlassian.jira.plug... ] Darran Lofthouse updated WFCORE-4777: ------------------------------------- Fix Version/s: 11.0.0.Beta6 > Upgrade JBoss Remoting from 5.0.16 to 5.0.17 > -------------------------------------------- > > Key: WFCORE-4777 > URL: https://issues.redhat.com/browse/WFCORE-4777 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Flavia Rainone > Priority: Major > Fix For: 11.0.0.Beta6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4783) Upgrade WildFly Elytron to 1.11.0.CR4

by Farah Juma (Jira)

Farah Juma created WFCORE-4783: ---------------------------------- Summary: Upgrade WildFly Elytron to 1.11.0.CR4 Key: WFCORE-4783 URL: https://issues.redhat.com/browse/WFCORE-4783 Project: WildFly Core Issue Type: Component Upgrade Components: Security Reporter: Farah Juma Assignee: Farah Juma -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4892) in evaluators for type Double does not work with executable model

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4892?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4892. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/ec7d928cfc1bae0ea9e325087d761dd... > in evaluators for type Double does not work with executable model > ------------------------------------------------------------------ > > Key: DROOLS-4892 > URL: https://issues.redhat.com/browse/DROOLS-4892 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.26.0.Final, 7.31.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: executable-model-DoubleTest.zip > > > The constraint like the following does not match when using executable model. > {noformat} > rule "Double nnn" > when > f : Fact( doubleVal in ( 100, 200, 300 ) ) > then > ... > end > {noformat} > This rule can fire if executable model is not used. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1884) Add new elytron-jwt module with SmallRye and MP JWT dependencies

by Farah Juma (Jira)

[ https://issues.redhat.com/browse/ELY-1884?page=com.atlassian.jira.plugin.... ] Farah Juma resolved ELY-1884. ----------------------------- Resolution: Done > Add new elytron-jwt module with SmallRye and MP JWT dependencies > ---------------------------------------------------------------- > > Key: ELY-1884 > URL: https://issues.redhat.com/browse/ELY-1884 > Project: WildFly Elytron > Issue Type: Task > Components: MicroProfile > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Major > Fix For: 1.11.0.CR4 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1916) Release WildFly Elytron 1.11.0.CR4

by Farah Juma (Jira)

Farah Juma created ELY-1916: ------------------------------- Summary: Release WildFly Elytron 1.11.0.CR4 Key: ELY-1916 URL: https://issues.redhat.com/browse/ELY-1916 Project: WildFly Elytron Issue Type: Release Reporter: Farah Juma Assignee: Farah Juma Fix For: 1.11.0.CR4 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12898) Multiversion Testing for wildfly images

by Panagiotis Sotiropoulos (Jira)

[ https://issues.redhat.com/browse/WFLY-12898?page=com.atlassian.jira.plugi... ] Panagiotis Sotiropoulos commented on WFLY-12898: ------------------------------------------------ Not finished yet. Some Instructions are needed to be added. > Multiversion Testing for wildfly images > ---------------------------------------- > > Key: WFLY-12898 > URL: https://issues.redhat.com/browse/WFLY-12898 > Project: WildFly > Issue Type: Task > Components: Test Suite > Reporter: Panagiotis Sotiropoulos > Assignee: Panagiotis Sotiropoulos > Priority: Major > > Multiversion Testing for wildfly images with EAT -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4879) [UX] [DMN Designer] unification of import flash messages

by Daniel José dos Santos (Jira)

[ https://issues.redhat.com/browse/DROOLS-4879?page=com.atlassian.jira.plug... ] Daniel José dos Santos commented on DROOLS-4879: ------------------------------------------------ [~jomarko] We don't have, but can't we change this JIRA to track the change? > [UX] [DMN Designer] unification of import flash messages > -------------------------------------------------------- > > Key: DROOLS-4879 > URL: https://issues.redhat.com/browse/DROOLS-4879 > Project: Drools > Issue Type: Bug > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: drools-tools > > We should unify the flash messages related to import data types. See the github comment here https://github.com/kiegroup/kie-wb-common/pull/3071#issuecomment-566436373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12860) IIOPTimeoutTestCase sometimes fails

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/WFLY-12860?page=com.atlassian.jira.plugi... ] Thomas Jenkinson commented on WFLY-12860: ----------------------------------------- I think the null is from https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jts/classes/com... I am wondering if that might be null due the timeout? Maybe something [here | https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jts/classes/com...] or [here | https://github.com/jbosstm/narayana/blob/master/ArjunaJTS/jts/classes/com...] > IIOPTimeoutTestCase sometimes fails > ----------------------------------- > > Key: WFLY-12860 > URL: https://issues.redhat.com/browse/WFLY-12860 > Project: WildFly > Issue Type: Quality Risk > Components: IIOP, Test Suite, Transactions > Affects Versions: 18.0.1.Final > Reporter: Michael Musgrove > Assignee: Tomasz Adamski > Priority: Major > Fix For: No Release > > > The test has been seen to fail twice in the last few months (see [link title|https://github.com/wildfly/wildfly/pull/12833] ,for example) and it would be useful to isolate why it fails. > The stack trace also shows an unexpected NPE coming from the transaction subsystem which on code inspection should never happen: > {code} > &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) java.lang.NullPointerException > &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.addFirst(ArrayDeque.java:287) > &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.push(ArrayDeque.java:580) > &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.arjuna.thread.ThreadActionData.pushAction(ThreadActionData.java:85) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12860) IIOPTimeoutTestCase sometimes fails

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/WFLY-12860?page=com.atlassian.jira.plugi... ] Thomas Jenkinson updated WFLY-12860: ------------------------------------ Component/s: Transactions > IIOPTimeoutTestCase sometimes fails > ----------------------------------- > > Key: WFLY-12860 > URL: https://issues.redhat.com/browse/WFLY-12860 > Project: WildFly > Issue Type: Quality Risk > Components: IIOP, Test Suite, Transactions > Affects Versions: 18.0.1.Final > Reporter: Michael Musgrove > Assignee: Tomasz Adamski > Priority: Major > Fix For: No Release > > > The test has been seen to fail twice in the last few months (see [link title|https://github.com/wildfly/wildfly/pull/12833] ,for example) and it would be useful to isolate why it fails. > The stack trace also shows an unexpected NPE coming from the transaction subsystem which on code inspection should never happen: > {code} > &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) java.lang.NullPointerException > &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.addFirst(ArrayDeque.java:287) > &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.push(ArrayDeque.java:580) > &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.arjuna.thread.ThreadActionData.pushAction(ThreadActionData.java:85) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12860) IIOPTimeoutTestCase sometimes fails

by Thomas Jenkinson (Jira)

[ https://issues.redhat.com/browse/WFLY-12860?page=com.atlassian.jira.plugi... ] Thomas Jenkinson commented on WFLY-12860: ----------------------------------------- Adding a bit more from the stack trace on https://ci.wildfly.org/viewLog.html?buildId=176876&tab=buildResultsDiv&bu... {code} &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) java.lang.NullPointerException &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.addFirst(ArrayDeque.java:287) &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.push(ArrayDeque.java:580) &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.arjuna.thread.ThreadActionData.pushAction(ThreadActionData.java:85) &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.arjuna.thread.ThreadActionData.pushAction(ThreadActionData.java:69) &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.jts.context.ContextManager.pushAction(ContextManager.java:575) &amp#27;[0m&amp#27;[31m06:26:32,519 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.jts.orbspecific.CurrentImple.resumeImple(CurrentImple.java:809) &amp#27;[0m&amp#27;[31m06:26:32,519 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.jts.orbspecific.CurrentImple.resumeWrapper(CurrentImple.java:840) &amp#27;[0m&amp#27;[31m06:26:32,519 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.jta.transaction.jts.TransactionManagerImple.resume(TransactionManagerImple.java:169) &amp#27;[0m&amp#27;[31m06:26:32,519 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts.integration@5.10.1.Final//com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.resume(BaseTransactionManagerDelegate.java:127) &amp#27;[0m&amp#27;[31m06:26:32,519 ERROR [stderr] (p: default-threadpool; w: Idle) at org.wildfly.transaction.client@1.1.8.Final//org.wildfly.transaction.client.LocalTransaction.resume(LocalTransaction.java:239) &amp#27;[0m&amp#27;[31m06:26:32,520 ERROR [stderr] (p: default-threadpool; w: Idle) at org.wildfly.transaction.client@1.1.8.Final//org.wildfly.transaction.client.ContextTransactionManager.resume(ContextTransactionManager.java:158) &amp#27;[0m&amp#27;[31m06:26:32,520 ERROR [stderr] (p: default-threadpool; w: Idle) at org.wildfly.transaction.client@1.1.8.Final//org.wildfly.transaction.client.ContextTransactionManager.resume(ContextTransactionManager.java:150) &amp#27;[0m&amp#27;[31m06:26:32,520 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.safeResume(CMTTxInterceptor.java:292) &amp#27;[0m&amp#27;[31m06:26:32,520 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.requiresNew(CMTTxInterceptor.java:385) &amp#27;[0m&amp#27;[31m06:26:32,520 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.LifecycleCMTTxInterceptor.processInvocation(LifecycleCMTTxInterceptor.java:68) &amp#27;[0m&amp#27;[31m06:26:32,521 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,521 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) &amp#27;[0m&amp#27;[31m06:26:32,521 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,521 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ee@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) &amp#27;[0m&amp#27;[31m06:26:32,521 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,522 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) &amp#27;[0m&amp#27;[31m06:26:32,522 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,522 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) &amp#27;[0m&amp#27;[31m06:26:32,522 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ee@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ee.component.BasicComponentInstance.destroy(BasicComponentInstance.java:125) &amp#27;[0m&amp#27;[31m06:26:32,522 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent$1.destroy(StatelessSessionComponent.java:69) &amp#27;[0m&amp#27;[31m06:26:32,523 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.stateless.StatelessSessionComponent$1.destroy(StatelessSessionComponent.java:61) &amp#27;[0m&amp#27;[31m06:26:32,523 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.pool.AbstractPool.doRemove(AbstractPool.java:80) &amp#27;[0m&amp#27;[31m06:26:32,523 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.pool.strictmax.StrictMaxPool.discard(StrictMaxPool.java:81) &amp#27;[0m&amp#27;[31m06:26:32,523 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:64) &amp#27;[0m&amp#27;[31m06:26:32,523 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,524 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) &amp#27;[0m&amp#27;[31m06:26:32,524 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,524 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:237) &amp#27;[0m&amp#27;[31m06:26:32,524 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:362) &amp#27;[0m&amp#27;[31m06:26:32,524 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:144) &amp#27;[0m&amp#27;[31m06:26:32,525 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,525 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:509) &amp#27;[0m&amp#27;[31m06:26:32,525 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.weld.core@3.1.2.Final//org.jboss.weld.module.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:81) &amp#27;[0m&amp#27;[31m06:26:32,525 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.weld.common@19.0.0.Beta1-SNAPSHOT//org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:89) &amp#27;[0m&amp#27;[31m06:26:32,525 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,526 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) &amp#27;[0m&amp#27;[31m06:26:32,526 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,526 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:47) &amp#27;[0m&amp#27;[31m06:26:32,526 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,526 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) &amp#27;[0m&amp#27;[31m06:26:32,527 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,527 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.deployment.processors.StartupAwaitInterceptor.processInvocation(StartupAwaitInterceptor.java:22) &amp#27;[0m&amp#27;[31m06:26:32,527 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,527 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) &amp#27;[0m&amp#27;[31m06:26:32,527 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,528 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.deployment.processors.EjbSuspendInterceptor.processInvocation(EjbSuspendInterceptor.java:57) &amp#27;[0m&amp#27;[31m06:26:32,528 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,528 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:67) &amp#27;[0m&amp#27;[31m06:26:32,528 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,528 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.component.interceptors.EjbExceptionTransformingInterceptorFactories$1.processInvocation(EjbExceptionTransformingInterceptorFactories.java:80) &amp#27;[0m&amp#27;[31m06:26:32,529 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,529 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ee@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) &amp#27;[0m&amp#27;[31m06:26:32,529 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,529 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:60) &amp#27;[0m&amp#27;[31m06:26:32,529 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,530 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:438) &amp#27;[0m&amp#27;[31m06:26:32,530 ERROR [stderr] (p: default-threadpool; w: Idle) at org.wildfly.security.elytron-private@1.11.0.CR2//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:627) &amp#27;[0m&amp#27;[31m06:26:32,530 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:57) &amp#27;[0m&amp#27;[31m06:26:32,530 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:422) &amp#27;[0m&amp#27;[31m06:26:32,530 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.invocation@1.5.2.Final//org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:53) &amp#27;[0m&amp#27;[31m06:26:32,531 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ee@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:198) &amp#27;[0m&amp#27;[31m06:26:32,531 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.as.ejb3@19.0.0.Beta1-SNAPSHOT//org.jboss.as.ejb3.iiop.EjbCorbaServant._invoke(EjbCorbaServant.java:371) &amp#27;[0m&amp#27;[31m06:26:32,531 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatchToServant(CorbaServerRequestDispatcherImpl.java:654) &amp#27;[0m&amp#27;[31m06:26:32,531 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.protocol.CorbaServerRequestDispatcherImpl.dispatch(CorbaServerRequestDispatcherImpl.java:205) &amp#27;[0m&amp#27;[31m06:26:32,531 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequestRequest(CorbaMessageMediatorImpl.java:1700) &amp#27;[0m&amp#27;[31m06:26:32,532 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:1558) &amp#27;[0m&amp#27;[31m06:26:32,532 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleInput(CorbaMessageMediatorImpl.java:940) &amp#27;[0m&amp#27;[31m06:26:32,532 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.protocol.giopmsgheaders.RequestMessage_1_2.callback(RequestMessage_1_2.java:198) &amp#27;[0m&amp#27;[31m06:26:32,532 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.protocol.CorbaMessageMediatorImpl.handleRequest(CorbaMessageMediatorImpl.java:712) &amp#27;[0m&amp#27;[31m06:26:32,532 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.dispatch(SocketOrChannelConnectionImpl.java:474) &amp#27;[0m&amp#27;[31m06:26:32,532 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.transport.SocketOrChannelConnectionImpl.doWork(SocketOrChannelConnectionImpl.java:1237) &amp#27;[0m&amp#27;[31m06:26:32,533 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.performWork(ThreadPoolImpl.java:490) &amp#27;[0m&amp#27;[31m06:26:32,533 ERROR [stderr] (p: default-threadpool; w: Idle) at javax.orb.api@8.1.4.Final//com.sun.corba.se.impl.orbutil.threadpool.ThreadPoolImpl$WorkerThread.run(ThreadPoolImpl.java:519) {code} > IIOPTimeoutTestCase sometimes fails > ----------------------------------- > > Key: WFLY-12860 > URL: https://issues.redhat.com/browse/WFLY-12860 > Project: WildFly > Issue Type: Quality Risk > Components: IIOP, Test Suite > Affects Versions: 18.0.1.Final > Reporter: Michael Musgrove > Assignee: Tomasz Adamski > Priority: Major > Fix For: No Release > > > The test has been seen to fail twice in the last few months (see [link title|https://github.com/wildfly/wildfly/pull/12833] ,for example) and it would be useful to isolate why it fails. > The stack trace also shows an unexpected NPE coming from the transaction subsystem which on code inspection should never happen: > {code} > &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) java.lang.NullPointerException > &amp#27;[0m&amp#27;[31m06:26:32,517 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.addFirst(ArrayDeque.java:287) > &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at java.base/java.util.ArrayDeque.push(ArrayDeque.java:580) > &amp#27;[0m&amp#27;[31m06:26:32,518 ERROR [stderr] (p: default-threadpool; w: Idle) at org.jboss.jts@5.10.1.Final//com.arjuna.ats.internal.arjuna.thread.ThreadActionData.pushAction(ThreadActionData.java:85) > {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12919) Test for WEJBHTTP-29 - WildFlyClientInputStream hangs on close

by Daniel Cihak (Jira)

[ https://issues.redhat.com/browse/WFLY-12919?page=com.atlassian.jira.plugi... ] Daniel Cihak reassigned WFLY-12919: ----------------------------------- Assignee: Daniel Cihak (was: Cheng Fang) > Test for WEJBHTTP-29 - WildFlyClientInputStream hangs on close > -------------------------------------------------------------- > > Key: WFLY-12919 > URL: https://issues.redhat.com/browse/WFLY-12919 > Project: WildFly > Issue Type: Task > Components: EJB > Reporter: Daniel Cihak > Assignee: Daniel Cihak > Priority: Major > Labels: test > > Create test case for WEJBHTTP-29. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12919) Test for WEJBHTTP-29 - WildFlyClientInputStream hangs on close

by Daniel Cihak (Jira)

Daniel Cihak created WFLY-12919: ----------------------------------- Summary: Test for WEJBHTTP-29 - WildFlyClientInputStream hangs on close Key: WFLY-12919 URL: https://issues.redhat.com/browse/WFLY-12919 Project: WildFly Issue Type: Task Components: EJB Reporter: Daniel Cihak Assignee: Cheng Fang Create test case for WEJBHTTP-29. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12918) Support JBeret's job repository table prefix and suffix

by Fabrizio Stellato (Jira)

[ https://issues.redhat.com/browse/WFLY-12918?page=com.atlassian.jira.plugi... ] Fabrizio Stellato updated WFLY-12918: ------------------------------------- Description: On jberet.properties you can set suffix and prefix of repository table. See [this link|https://github.com/jberet/jsr352/blob/master/jberet-distribution/src...] On [Wildfly configuration|https://access.redhat.com/documentation/en-us/red_hat_jboss...] I cannot see any config like the above, can you enhance it ? was: On jberet.properties you can set suffix and prefix of repository table. See [this link|https://github.com/jberet/jsr352/blob/master/jberet-distribution/src...] Can you enhance Wildfly's configuration in order to have this feature on web server too ? > Support JBeret's job repository table prefix and suffix > ------------------------------------------------------- > > Key: WFLY-12918 > URL: https://issues.redhat.com/browse/WFLY-12918 > Project: WildFly > Issue Type: Feature Request > Reporter: Fabrizio Stellato > Assignee: Brian Stansberry > Priority: Major > > On jberet.properties you can set suffix and prefix of repository table. > See [this link|https://github.com/jberet/jsr352/blob/master/jberet-distribution/src...] > On [Wildfly configuration|https://access.redhat.com/documentation/en-us/red_hat_jboss...] I cannot see any config like the above, > can you enhance it ? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12918) Support JBeret's job repository table prefix and suffix

by Fabrizio Stellato (Jira)

Fabrizio Stellato created WFLY-12918: ---------------------------------------- Summary: Support JBeret's job repository table prefix and suffix Key: WFLY-12918 URL: https://issues.redhat.com/browse/WFLY-12918 Project: WildFly Issue Type: Feature Request Reporter: Fabrizio Stellato Assignee: Brian Stansberry On jberet.properties you can set suffix and prefix of repository table. See [this link|https://github.com/jberet/jsr352/blob/master/jberet-distribution/src...] Can you enhance Wildfly's configuration in order to have this feature on web server too ? -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4879) [UX] [DMN Designer] unification of import flash messages

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4879?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4879: ------------------------------------- Thank you [~uxdlc], [~dadossan] please do we have a ticket where we track this change? > [UX] [DMN Designer] unification of import flash messages > -------------------------------------------------------- > > Key: DROOLS-4879 > URL: https://issues.redhat.com/browse/DROOLS-4879 > Project: Drools > Issue Type: Bug > Affects Versions: 7.32.0.Final > Reporter: Jozef Marko > Assignee: Elizabeth Clayton > Priority: Major > Labels: drools-tools > > We should unify the flash messages related to import data types. See the github comment here https://github.com/kiegroup/kie-wb-common/pull/3071#issuecomment-566436373 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4898) Accumulates: min does not work after retracting fact.

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4898?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4898. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/cf80a213c7a678fe2d39058135e28c1... The same fix for DROOLS-4896 also solved this problem. Consider however that when you modify an object in the working memory you should always notify the engine calling an update. > Accumulates: min does not work after retracting fact. > ----------------------------------------------------- > > Key: DROOLS-4898 > URL: https://issues.redhat.com/browse/DROOLS-4898 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.26.0.Final, 7.31.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > > The following rules does not work with specific facts. > {noformat} > rule "rule1_long" > when > accumulate( Fact( $longVal: longVal), $minVal : min($longVal)) > accumulate( Fact( $longVal2: longVal, $longVal2 > $minVal), $minVal2 : min($longVal2)) > $minFact: Fact( longVal == $minVal) > $minFact2: Fact( longVal == $minVal2) > then > System.out.println("Rule ["+kcontext.getRule().getName()+ "] fires!"); > Long $diff = (Long)$minVal2 - (Long)$minVal; > $minFact2.setDiff($diff); > // update($minFact2); > String errmsg = $diff == 0? " !!!!! ERROR !!!!!" : ""; > System.out.println( drools.getRule().getName() + " diff：" + $minFact2.getLongVal() + " - " + $minFact.getLongVal() + " = " + $diff + errmsg); > System.out.println("\tretract <= "+$minFact ); > retract($minFact); > end > {noformat} > There seems to be 2 kind of issues (root cause might be same though). > - 2nd accumulate return same min value with 1st one. > - rule fire count is less than expected. > This does not work with specific set of facts, but works with another set of facts. > If update is called for the fact like above commented out line, this does not happen. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4896) Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-4896?page=com.atlassian.jira.plug... ] Mario Fusco resolved DROOLS-4896. --------------------------------- Resolution: Done Fixed by https://github.com/kiegroup/drools/commit/cf80a213c7a678fe2d39058135e28c1... > Accumulate: min with BigDecimal doesn't work as expected when drools.propertySpecific=ALLOWED > --------------------------------------------------------------------------------------------- > > Key: DROOLS-4896 > URL: https://issues.redhat.com/browse/DROOLS-4896 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.14.0.Final, 7.26.0.Final, 7.31.0.Final > Reporter: Hiroko Miura > Assignee: Mario Fusco > Priority: Major > Labels: support > Attachments: bigdecimal-accumulate-test.zip > > > Regarding accumulate, min function with BigDecimal does not work as expected when drools.propertySpecific is "ALLOWED". > The following rule worked with BRMS6.1.4(6.2.0.Final-redhat-13). > {noformat} > rule "rule1_BigDecimal" > agenda-group "BigDecimal" > when > accumulate( Fact( $bdVal: bdVal), $minVal : min($bdVal)) > accumulate( Fact( $bdVal2: bdVal, $bdVal2 > $minVal), $minVal2 : min($bdVal2)) > > $minFact: Fact( bdVal == new BigDecimal($minVal.intValue())) > $minFact2: Fact( bdVal == new BigDecimal($minVal2.intValue())) > then > ... > end > {noformat} > But after upgrading to RHPAM 7 and setting drools.propertySpecific=ALLOWED, this does not work. > i.e. rule fires one more time than expected even though there is only one fact at the last iteration. > This does not happen at least with Long type. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4606) DMN alpha network

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4606?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4606: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 01-03 (from Dec 30)) > DMN alpha network > ----------------- > > Key: DROOLS-4606 > URL: https://issues.redhat.com/browse/DROOLS-4606 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Start refactoring work to support alpha network -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4607) DMN DT Analysis for symbols

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-4607?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-4607: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 01-03 (from Dec 30)) > DMN DT Analysis for symbols > --------------------------- > > Key: DROOLS-4607 > URL: https://issues.redhat.com/browse/DROOLS-4607 > Project: Drools > Issue Type: Feature Request > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > > Extend analysis to symbolic processing in the possible cases -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3928) DMN refactor codegen for same strategy

by Matteo Mortari (Jira)

[ https://issues.redhat.com/browse/DROOLS-3928?page=com.atlassian.jira.plug... ] Matteo Mortari updated DROOLS-3928: ----------------------------------- Sprint: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 04-06 (from Jan 20) (was: 2019 Week 41-43 (from Okt 7), 2019 Week 44-46 (from Okt 28), 2019 Week 47-49 (from Nov 18), 2020 Week 01-03 (from Dec 30)) > DMN refactor codegen for same strategy > -------------------------------------- > > Key: DROOLS-3928 > URL: https://issues.redhat.com/browse/DROOLS-3928 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1448) [XLS Decision Table] Integer values for Double attributes causes validation error

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-1448?page=com.atlassian.jira.plug... ] Mario Fusco updated DROOLS-1448: -------------------------------- Sprint: 2020 Week 01-03 (from Dec 30) > [XLS Decision Table] Integer values for Double attributes causes validation error > --------------------------------------------------------------------------------- > > Key: DROOLS-1448 > URL: https://issues.redhat.com/browse/DROOLS-1448 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Jozef Marko > Assignee: Mario Fusco > Priority: Minor > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > Attachments: Driver.java, ExamplePolicyPricing.xls, Policy.java, Screenshot from 2017-02-02 10-22-21.png > > > If the XLS decision contains Integer values for column ( attribute ) that is Double data type, then the XLS decision table is not validated successfully. After conversion to guided decision table is the table validated successfully. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1448) [XLS Decision Table] Integer values for Double attributes causes validation error

by Mario Fusco (Jira)

[ https://issues.redhat.com/browse/DROOLS-1448?page=com.atlassian.jira.plug... ] Mario Fusco reopened DROOLS-1448: --------------------------------- I was confused by the fact that the jira from which this one was cloned was also closed as resolved. However in this case it was cloned from the GUVNOR-2874 just because it uses same assets in steps to reproduce. I'll give a look at the reproducer. > [XLS Decision Table] Integer values for Double attributes causes validation error > --------------------------------------------------------------------------------- > > Key: DROOLS-1448 > URL: https://issues.redhat.com/browse/DROOLS-1448 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Jozef Marko > Assignee: Mario Fusco > Priority: Minor > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > Attachments: Driver.java, ExamplePolicyPricing.xls, Policy.java, Screenshot from 2017-02-02 10-22-21.png > > > If the XLS decision contains Integer values for column ( attribute ) that is Double data type, then the XLS decision table is not validated successfully. After conversion to guided decision table is the table validated successfully. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4771) Fix validation for background/wrong dmn scesim files

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-4771?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-4771: ------------------------------------- [~gabriolo] hello, could you please shaare the scesim file you have used, or the error that will be shown to the user? > Fix validation for background/wrong dmn scesim files > ---------------------------------------------------- > > Key: DROOLS-4771 > URL: https://issues.redhat.com/browse/DROOLS-4771 > Project: Drools > Issue Type: Bug > Reporter: Gabriele Cardosi > Assignee: Gabriele Cardosi > Priority: Major > > Validation should be enabled also for background data. > Beside that, when importing a scesim file related to a missing dmn, the validation on import should fail (currently is does not) -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1448) [XLS Decision Table] Integer values for Double attributes causes validation error

by Jozef Marko (Jira)

[ https://issues.redhat.com/browse/DROOLS-1448?page=com.atlassian.jira.plug... ] Jozef Marko commented on DROOLS-1448: ------------------------------------- [~mfusco] hello, I think if this was closed without any PR, I think we should move the jira into the Closed(can not reproduce) state rather than Resolved. What do you think? > [XLS Decision Table] Integer values for Double attributes causes validation error > --------------------------------------------------------------------------------- > > Key: DROOLS-1448 > URL: https://issues.redhat.com/browse/DROOLS-1448 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.0.0.Beta6 > Reporter: Jozef Marko > Assignee: Mario Fusco > Priority: Minor > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > Attachments: Driver.java, ExamplePolicyPricing.xls, Policy.java, Screenshot from 2017-02-02 10-22-21.png > > > If the XLS decision contains Integer values for column ( attribute ) that is Double data type, then the XLS decision table is not validated successfully. After conversion to guided decision table is the table validated successfully. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 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