November 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4109) Remove outdated policy files from testsuite/integration/src/test/config

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4109?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4109: ----------------------------------------------- Petr Kremensky <pkremens(a)redhat.com> changed the Status of [bug 1166130|https://bugzilla.redhat.com/show_bug.cgi?id=1166130] from ON_QA to VERIFIED > Remove outdated policy files from testsuite/integration/src/test/config > ----------------------------------------------------------------------- > > Key: WFLY-4109 > URL: https://issues.jboss.org/browse/WFLY-4109 > Project: WildFly > Issue Type: Enhancement > Components: Test Suite > Reporter: Josef Cacek > Assignee: Josef Cacek > Priority: Minor > Fix For: 9.0.0.Beta1 > > > Policy files no-op.policy and permit_all_testsuite.policy are outdated. They should be removed. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-650: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1168746|https://bugzilla.redhat.com/show_bug.cgi?id=1168746] from ASSIGNED to MODIFIED > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on DROOLS-650: ------------------------------------------------ Mario Fusco <mfusco(a)redhat.com> changed the Status of [bug 1168746|https://bugzilla.redhat.com/show_bug.cgi?id=1168746] from NEW to ASSIGNED > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-650: ------------------------------------------- Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168746, https://bugzilla.redhat.com/show_bug.cgi?id=1168747 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1168746) > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-650) Sequential Phreak is broken

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/DROOLS-650?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration updated DROOLS-650: ------------------------------------------- Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1168746 > Sequential Phreak is broken > ---------------------------- > > Key: DROOLS-650 > URL: https://issues.jboss.org/browse/DROOLS-650 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.0.1.Final, 6.1.0.Final, 6.2.0.CR2 > Reporter: Mark Proctor > Assignee: Mario Fusco > Fix For: 6.2.0.CR3 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4135) EE Concurrency 1.0 Quickstarts

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-4135: ------------------------------------- Summary: EE Concurrency 1.0 Quickstarts Key: WFLY-4135 URL: https://issues.jboss.org/browse/WFLY-4135 Project: WildFly Issue Type: Sub-task Reporter: Eduardo Martins Assignee: Eduardo Martins Update WildFly Quickstarts to demo usage of EE Concurrency 1.0, new technology introduced by Java EE 7. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4134) Java EE 7 Quickstarts

by Eduardo Martins (JIRA)

Eduardo Martins created WFLY-4134: ------------------------------------- Summary: Java EE 7 Quickstarts Key: WFLY-4134 URL: https://issues.jboss.org/browse/WFLY-4134 Project: WildFly Issue Type: Task Reporter: Eduardo Martins Assignee: Eduardo Martins WildFly Quickstarts should demo the technologies introduced/updated by Java EE 7. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4133) Hanging EJB threads because of a persistent timer and failed deployment

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4133?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated WFLY-4133: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1147948 > Hanging EJB threads because of a persistent timer and failed deployment > ------------------------------------------------------------------------ > > Key: WFLY-4133 > URL: https://issues.jboss.org/browse/WFLY-4133 > Project: WildFly > Issue Type: Bug > Affects Versions: 9.0.0.Alpha1 > Reporter: Enrique González Martínez > Assignee: Enrique González Martínez > > When there is a time service with pending timeouts a bad redeploy can hang worker threads in the server. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4133) Hanging EJB threads because of a persistent timer and failed deployment

by Enrique González Martínez (JIRA)

Enrique González Martínez created WFLY-4133: ----------------------------------------------- Summary: Hanging EJB threads because of a persistent timer and failed deployment Key: WFLY-4133 URL: https://issues.jboss.org/browse/WFLY-4133 Project: WildFly Issue Type: Bug Affects Versions: 9.0.0.Alpha1 Reporter: Enrique González Martínez Assignee: Enrique González Martínez When there is a time service with pending timeouts a bad redeploy can hang worker threads in the server. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

[JBoss JIRA] (WFLY-4129) The RemotingLoginModule should first check if there is already a RealmUser

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4129?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4129: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1168585|https://bugzilla.redhat.com/show_bug.cgi?id=1168585] from POST to MODIFIED > The RemotingLoginModule should first check if there is already a RealmUser > -------------------------------------------------------------------------- > > Key: WFLY-4129 > URL: https://issues.jboss.org/browse/WFLY-4129 > Project: WildFly > Issue Type: Bug > Components: Security > Affects Versions: 9.0.0.Alpha1 > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 9.0.0.Beta1 > > > The reason is because the realm may have actually already substituted in a different name for the user. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2014