January 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9721) AsyncInvocationTask.get() throws CancellationException

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9721?page=com.atlassian.jira.plugin.... ] David Lloyd commented on WFLY-9721: ----------------------------------- The {{get()}} method should throw {{InterruptedException}} if and only if the thread calling {{get()}} was interrupted before the result was ready. If the asynchronous task itself was cancelled (which might or might not entail interruption), then {{CancellationException}} is the correct exception. > AsyncInvocationTask.get() throws CancellationException > ------------------------------------------------------ > > Key: WFLY-9721 > URL: https://issues.jboss.org/browse/WFLY-9721 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Denis Shklyaev > Priority: Optional > > AsyncInvocationTask.get() on cancelled task in Wildfly 11 throws CancellationException via EjbLogger, but the behavior is not declared in method signature: > {code:java} > public synchronized Object get() throws InterruptedException, ExecutionException { > for (;;) switch (status) { > case ST_RUNNING: wait(); break; > *case ST_CANCELLED: throw EjbLogger.ROOT_LOGGER.taskWasCancelled();* > case ST_FAILED: throw new ExecutionException(failed); > case ST_DONE: return result; > default: throw Assert.impossibleSwitchCase(status); > } > } > {code} > Wildfly 10.01.0 code is different: > {code:java} > public synchronized Object get() throws InterruptedException, ExecutionException { > while (!isDone()) { > wait(); > } > if (failed != null) { > throw new ExecutionException(failed); > } > return result; > } > {code} > It throws InterruptedException instead as declared. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9721) AsyncInvocationTask.get() throws CancellationException

by David Lloyd (JIRA)

[ https://issues.jboss.org/browse/WFLY-9721?page=com.atlassian.jira.plugin.... ] David Lloyd updated WFLY-9721: ------------------------------ Description: AsyncInvocationTask.get() on cancelled task in Wildfly 11 throws CancellationException via EjbLogger, but the behavior is not declared in method signature: {code:java} public synchronized Object get() throws InterruptedException, ExecutionException { for (;;) switch (status) { case ST_RUNNING: wait(); break; *case ST_CANCELLED: throw EjbLogger.ROOT_LOGGER.taskWasCancelled();* case ST_FAILED: throw new ExecutionException(failed); case ST_DONE: return result; default: throw Assert.impossibleSwitchCase(status); } } {code} Wildfly 10.01.0 code is different: {code:java} public synchronized Object get() throws InterruptedException, ExecutionException { while (!isDone()) { wait(); } if (failed != null) { throw new ExecutionException(failed); } return result; } {code} It throws InterruptedException instead as declared. was: AsyncInvocationTask.get() on cancelled task in Wildfly 11 throws CancellationException via EjbLogger, but the behavior is not declared in method signature: {{ public synchronized Object get() throws InterruptedException, ExecutionException { for (;;) switch (status) { case ST_RUNNING: wait(); break; *case ST_CANCELLED: throw EjbLogger.ROOT_LOGGER.taskWasCancelled();* case ST_FAILED: throw new ExecutionException(failed); case ST_DONE: return result; default: throw Assert.impossibleSwitchCase(status); } } }} Wildfly 10.01.0 code is different: {{ public synchronized Object get() throws InterruptedException, ExecutionException { while (!isDone()) { wait(); } if (failed != null) { throw new ExecutionException(failed); } return result; } }} It throws InterruptedException instead as declared. > AsyncInvocationTask.get() throws CancellationException > ------------------------------------------------------ > > Key: WFLY-9721 > URL: https://issues.jboss.org/browse/WFLY-9721 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.Final > Reporter: Denis Shklyaev > Priority: Optional > > AsyncInvocationTask.get() on cancelled task in Wildfly 11 throws CancellationException via EjbLogger, but the behavior is not declared in method signature: > {code:java} > public synchronized Object get() throws InterruptedException, ExecutionException { > for (;;) switch (status) { > case ST_RUNNING: wait(); break; > *case ST_CANCELLED: throw EjbLogger.ROOT_LOGGER.taskWasCancelled();* > case ST_FAILED: throw new ExecutionException(failed); > case ST_DONE: return result; > default: throw Assert.impossibleSwitchCase(status); > } > } > {code} > Wildfly 10.01.0 code is different: > {code:java} > public synchronized Object get() throws InterruptedException, ExecutionException { > while (!isDone()) { > wait(); > } > if (failed != null) { > throw new ExecutionException(failed); > } > return result; > } > {code} > It throws InterruptedException instead as declared. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3546) Update MoreTestCase to hide failures caused by WFCORE-3545

by Erich Duda (JIRA)

Erich Duda created WFCORE-3546: ---------------------------------- Summary: Update MoreTestCase to hide failures caused by WFCORE-3545 Key: WFCORE-3546 URL: https://issues.jboss.org/browse/WFCORE-3546 Project: WildFly Core Issue Type: Task Components: CLI Affects Versions: 4.0.0.Alpha6 Reporter: Erich Duda Assignee: Erich Duda The MoreTestCase fails on Solaris and HPUX because of the WFCORE-3545. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3545) Composed keys don't have to be recognized by CLI

by Erich Duda (JIRA)

Erich Duda created WFCORE-3545: ---------------------------------- Summary: Composed keys don't have to be recognized by CLI Key: WFCORE-3545 URL: https://issues.jboss.org/browse/WFCORE-3545 Project: WildFly Core Issue Type: Bug Components: CLI Affects Versions: 4.0.0.Alpha6 Reporter: Erich Duda Assignee: Jean-Francois Denise Some keys like key down are composed from multiple characters. Normally when the key down is pushed, 3 characters are written into stdin. These 3 characters are read by InputStream::read operation at once and then decoded to the Key.DOWN constant. However there is no guarantee that InputStream::read operation returns all the 3 characters at once. It can return only first character and then remaining two. This actually happens in one test on Solaris and HPUX, where stdin is emulated by PipedInputStream. If the aforementioned situation happens, pushing of key down is decoded as pushing of two maybe three keys - ESC and some other key(s). The issue has low priority, because this behavior wasn't observed in real terminal with real input. It affects only testing. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9731) The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS

by Petr Jurak (JIRA)

[ https://issues.jboss.org/browse/WFLY-9731?page=com.atlassian.jira.plugin.... ] Petr Jurak reassigned WFLY-9731: -------------------------------- Assignee: Petr Jurak (was: Pedro Igor) > The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9731 > URL: https://issues.jboss.org/browse/WFLY-9731 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Petr Jurak > Assignee: Petr Jurak > > Web service with STS (Picketlink) returns wrong subject with PolicyContext("javax.security.auth.subject.container"). > It seems that configured login modules are not called since SecurityContext was created by SAML2Handler for the same security domain and are skipped because of WFLY-4625. > Reproducer is attached in BZ-1352418. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9731) The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS

by Peter Skopek (JIRA)

[ https://issues.jboss.org/browse/WFLY-9731?page=com.atlassian.jira.plugin.... ] Peter Skopek moved PLINK-772 to WFLY-9731: ------------------------------------------ Project: WildFly (was: PicketLink) Key: WFLY-9731 (was: PLINK-772) Workflow: GIT Pull Request workflow (was: classic default workflow) Component/s: Security (was: BASE) > The fix for WFLY-4625 breaks PolicyContext("javax.security.auth.subject.container") in CXF web service with STS > --------------------------------------------------------------------------------------------------------------- > > Key: WFLY-9731 > URL: https://issues.jboss.org/browse/WFLY-9731 > Project: WildFly > Issue Type: Bug > Components: Security > Reporter: Petr Jurak > Assignee: Pedro Igor > > Web service with STS (Picketlink) returns wrong subject with PolicyContext("javax.security.auth.subject.container"). > It seems that configured login modules are not called since SecurityContext was created by SAML2Handler for the same security domain and are skipped because of WFLY-4625. > Reproducer is attached in BZ-1352418. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3541) Missing password types in set-password operation of modifiable realms

by Jan Kalina (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3541?page=com.atlassian.jira.plugi... ] Jan Kalina commented on WFCORE-3541: ------------------------------------ By discussion, reworking of password management API is in plan, so adding all passwords types into current one would not be much useful. But scram will be added, as we want SCRAM to be preferred authentication mechanism. > Missing password types in set-password operation of modifiable realms > --------------------------------------------------------------------- > > Key: WFCORE-3541 > URL: https://issues.jboss.org/browse/WFCORE-3541 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 4.0.0.Alpha6 > Reporter: Jan Kalina > Assignee: Jan Kalina > Priority: Critical > Labels: elytron > > Not all password types are covered by *set-password* operation in ModifiableRealmDecorator. > At least *ScramDigestPassword* is not available. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2274) "?" special variable support

by Fedor Gavrilov (JIRA)

Fedor Gavrilov created DROOLS-2274: -------------------------------------- Summary: "?" special variable support Key: DROOLS-2274 URL: https://issues.jboss.org/browse/DROOLS-2274 Project: Drools Issue Type: Enhancement Reporter: Fedor Gavrilov Assignee: Fedor Gavrilov Priority: Minor -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1767) FEEL: add compile-time cycle detection

by Fedor Gavrilov (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1767?page=com.atlassian.jira.plugi... ] Fedor Gavrilov resolved DROOLS-1767. ------------------------------------ Resolution: Done > FEEL: add compile-time cycle detection > --------------------------------------- > > Key: DROOLS-1767 > URL: https://issues.jboss.org/browse/DROOLS-1767 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Affects Versions: 7.4.1.Final > Reporter: Fedor Gavrilov > Assignee: Fedor Gavrilov > Priority: Minor > > Similar to what's done in https://issues.jboss.org/browse/DROOLS-1730 but during validation stage -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ELY-1405) The password attribute of resource owner credentials should support a credential store reference

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1405?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1405: ---------------------------------- Fix Version/s: 1.2.0.Beta13 (was: 1.2.0.Beta12) > The password attribute of resource owner credentials should support a credential store reference > ------------------------------------------------------------------------------------------------ > > Key: ELY-1405 > URL: https://issues.jboss.org/browse/ELY-1405 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Martin Mazanek > Fix For: 1.2.0.Beta13 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018