February 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6672) EJB's async methods' Future#get should treat zero timeout as "don't wait"

by Daniel Čihák (JIRA)

[ https://issues.jboss.org/browse/WFLY-6672?page=com.atlassian.jira.plugin.... ] Daniel Čihák edited comment on WFLY-6672 at 2/8/17 9:06 AM: ------------------------------------------------------------ Pull request with test https://github.com/wildfly/wildfly/pull/9617. was (Author: dcihak): Pull request with test https://github.com/jbossas/jboss-eap7/pull/1282. > EJB's async methods' Future#get should treat zero timeout as "don't wait" > ------------------------------------------------------------------------- > > Key: WFLY-6672 > URL: https://issues.jboss.org/browse/WFLY-6672 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.2.0.Final > Reporter: Vsevolod Golovanov > Assignee: Stuart Douglas > Fix For: 10.1.0.CR1, 10.1.0.Final > > > Say there is an asynchronous EJB method: > {code} > @Asynchronous > public Future<Boolean> method() { > ... > } > {code} > Calling Future#get with a zero timeout: > {code} > if (bean.method().get(0, TimeUnit.MILLISECONDS)) > {code} > results in a block until the task is finished. > Instead I expected zero waiting, because {{java.util.concurrent.Future.get(long, TimeUnit)}} doesn't specify any special treatment for a zero timeout value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6672) EJB's async methods' Future#get should treat zero timeout as "don't wait"

by Daniel Čihák (JIRA)

[ https://issues.jboss.org/browse/WFLY-6672?page=com.atlassian.jira.plugin.... ] Daniel Čihák edited comment on WFLY-6672 at 2/8/17 9:05 AM: ------------------------------------------------------------ Pull request with test https://github.com/jbossas/jboss-eap7/pull/1282. was (Author: dcihak): Pull request with test https://github.com/wildfly/wildfly/pull/9617. > EJB's async methods' Future#get should treat zero timeout as "don't wait" > ------------------------------------------------------------------------- > > Key: WFLY-6672 > URL: https://issues.jboss.org/browse/WFLY-6672 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.2.0.Final > Reporter: Vsevolod Golovanov > Assignee: Stuart Douglas > Fix For: 10.1.0.CR1, 10.1.0.Final > > > Say there is an asynchronous EJB method: > {code} > @Asynchronous > public Future<Boolean> method() { > ... > } > {code} > Calling Future#get with a zero timeout: > {code} > if (bean.method().get(0, TimeUnit.MILLISECONDS)) > {code} > results in a block until the task is finished. > Instead I expected zero waiting, because {{java.util.concurrent.Future.get(long, TimeUnit)}} doesn't specify any special treatment for a zero timeout value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-933) There isn't possibility disable create CS file from scratch

by Peter Skopek (JIRA)

Peter Skopek created ELY-933: -------------------------------- Summary: There isn't possibility disable create CS file from scratch Key: ELY-933 URL: https://issues.jboss.org/browse/ELY-933 Project: WildFly Elytron Issue Type: Bug Components: Credential Store Affects Versions: 1.1.0.Beta20 Reporter: Peter Skopek Assignee: Peter Skopek Priority: Blocker There isn't possibility to disable create CS file from scratch. Earlier we were able to set create.storage to true/false. I can see problem in this scenario: * I want to create new CS with path to existing CS file * I fill wrong path * Everything pass But I want to use my CS file, not to create new one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6672) EJB's async methods' Future#get should treat zero timeout as "don't wait"

by Daniel Čihák (JIRA)

[ https://issues.jboss.org/browse/WFLY-6672?page=com.atlassian.jira.plugin.... ] Daniel Čihák commented on WFLY-6672: ------------------------------------ Pull request with test https://github.com/wildfly/wildfly/pull/9617. > EJB's async methods' Future#get should treat zero timeout as "don't wait" > ------------------------------------------------------------------------- > > Key: WFLY-6672 > URL: https://issues.jboss.org/browse/WFLY-6672 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.2.0.Final > Reporter: Vsevolod Golovanov > Assignee: Stuart Douglas > Fix For: 10.1.0.CR1, 10.1.0.Final > > > Say there is an asynchronous EJB method: > {code} > @Asynchronous > public Future<Boolean> method() { > ... > } > {code} > Calling Future#get with a zero timeout: > {code} > if (bean.method().get(0, TimeUnit.MILLISECONDS)) > {code} > results in a block until the task is finished. > Instead I expected zero waiting, because {{java.util.concurrent.Future.get(long, TimeUnit)}} doesn't specify any special treatment for a zero timeout value. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8056) Implement ServerSetupTask to simplify configuring Elytron security domains

by Josef Cacek (JIRA)

Josef Cacek created WFLY-8056: --------------------------------- Summary: Implement ServerSetupTask to simplify configuring Elytron security domains Key: WFLY-8056 URL: https://issues.jboss.org/browse/WFLY-8056 Project: WildFly Issue Type: Task Components: Test Suite, Security Reporter: Josef Cacek Assignee: Darran Lofthouse Implement logic similar to {{org.jboss.as.test.integration.security.common.AbstractSecurityDomainsServerSetupTask}} which could be used accross AS TS to create Elytron security domains. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8056) Implement ServerSetupTask to simplify configuring Elytron security domains

by Josef Cacek (JIRA)

[ https://issues.jboss.org/browse/WFLY-8056?page=com.atlassian.jira.plugin.... ] Josef Cacek reassigned WFLY-8056: --------------------------------- Assignee: Josef Cacek (was: Darran Lofthouse) > Implement ServerSetupTask to simplify configuring Elytron security domains > -------------------------------------------------------------------------- > > Key: WFLY-8056 > URL: https://issues.jboss.org/browse/WFLY-8056 > Project: WildFly > Issue Type: Task > Components: Security, Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > > Implement logic similar to > {{org.jboss.as.test.integration.security.common.AbstractSecurityDomainsServerSetupTask}} which could be used accross AS TS to create Elytron security domains. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2063) JDBC_PING: allow supplying dataSource object directly instead of String-based properties

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/JGRP-2063?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated JGRP-2063: --------------------------------- Fix Version/s: 4.0 (was: 4.1) > JDBC_PING: allow supplying dataSource object directly instead of String-based properties > ---------------------------------------------------------------------------------------- > > Key: JGRP-2063 > URL: https://issues.jboss.org/browse/JGRP-2063 > Project: JGroups > Issue Type: Feature Request > Affects Versions: 3.6.9 > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Fix For: 4.0 > > > See WFLY-6599. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8055) Upgrade h2 to 1.4.193 from 1.3.176

by Tomaz Cerar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8055?page=com.atlassian.jira.plugin.... ] Tomaz Cerar moved JBEAP-8724 to WFLY-8055: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8055 (was: JBEAP-8724) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) > Upgrade h2 to 1.4.193 from 1.3.176 > ---------------------------------- > > Key: WFLY-8055 > URL: https://issues.jboss.org/browse/WFLY-8055 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Tomaz Cerar > Assignee: Tomaz Cerar > > 1.3.176 requires JDK 6 to do the prod rebuild. It is not recommended for production use anyway. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ELY-749) String.toUpperCase() is used without Locale in AttributeMapping class (Elytron)

by Martin Choma (JIRA)

[ https://issues.jboss.org/browse/ELY-749?page=com.atlassian.jira.plugin.sy... ] Martin Choma commented on ELY-749: ---------------------------------- Just note, elytron and elytron-subsytem use: - Locale.ROOT - Locale.ENGLISH - Locale.US Is it worth unifying it? [~dmlloyd] ^ > String.toUpperCase() is used without Locale in AttributeMapping class (Elytron) > ------------------------------------------------------------------------------- > > Key: ELY-749 > URL: https://issues.jboss.org/browse/ELY-749 > Project: WildFly Elytron > Issue Type: Bug > Reporter: Josef Cacek > Assignee: Ilia Vassilev > Priority: Critical > Fix For: 1.1.0.Beta17 > > > The String.toUpperCase() call is used in constructor of {{AttributeMapping}} class without providing {{Locale.ENGLISH}} or {{Locale.US}} as parameter. > This can lead to problems on systems with non-English default locale (e.g. {{-Duser.language=tr}}). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8054) Remove messaging's required dependency to SecurityDomainService

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-8054?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-8721 to WFLY-8054: ------------------------------------------ Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-8054 (was: JBEAP-8721) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: JMS) > Remove messaging's required dependency to SecurityDomainService > --------------------------------------------------------------- > > Key: WFLY-8054 > URL: https://issues.jboss.org/browse/WFLY-8054 > Project: WildFly > Issue Type: Bug > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > > The messaging-activemq subsystem can use either a legacy security-domain or the new elytron-domain. > However, when only elytron-domain is defined (and any legacy security domain is removed), the subsystem fails to boot with the error: > {code} > 17:52:34,634 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ > ("subsystem" => "messaging-activemq"), > ("server" => "default") > ]) - failure description: { > "WFLYCTL0412: Required services that are not installed:" => ["jboss.security.security-domain.other"], > "WFLYCTL0180: Services with missing/unavailable dependencies" => ["jboss.messaging-activemq.default is missing [jboss.security.security-domain.other]"] > } > {code} > The dependency to jboss.security.security-domain.other must be optional and set only when elytron-domain is not defined. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017