November 2014 - jboss-jira - Jboss List Archives

[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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-656) The blessed repo's should not accept a git force push

by Geoffrey De Smet (JIRA)

[ https://issues.jboss.org/browse/DROOLS-656?page=com.atlassian.jira.plugin... ] Geoffrey De Smet commented on DROOLS-656: ----------------------------------------- Might not be possible on GitHub yet: http://stackoverflow.com/questions/13016119/how-to-set-the-receive-denyno... > The blessed repo's should not accept a git force push > ----------------------------------------------------- > > Key: DROOLS-656 > URL: https://issues.jboss.org/browse/DROOLS-656 > Project: Drools > Issue Type: Task > Reporter: Geoffrey De Smet > Assignee: Michael Biarnes Kiefer > Priority: Critical > > If someone ever git forces pushes to a blessed repo all hell will break loose. > We can prevent git forces pushes, as explained here: > http://stackoverflow.com/questions/1754491/is-there-a-way-to-configure-gi... > Force pushing on blessed repo's is very bad, but force pushing on forks is very common. > Requirements: > - Enable this on 1 new dummy blessed repository > - Prove you cannot force push to > - Prove you can fork it and force push to your fork. > - Delete the dummy blessed repository > - If that works well, enable it on the real blessed repositories -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-260) Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-260?page=com.atlassian.jira.plugin... ] RH Bugzilla Integration commented on WFCORE-260: ------------------------------------------------ Darran Lofthouse <darran.lofthouse(a)redhat.com> changed the Status of [bug 1161589|https://bugzilla.redhat.com/show_bug.cgi?id=1161589] from ASSIGNED to POST > Incorrect LoginModule name used for Kerberos with IBM JDK and incorrect case for useKeytab > ------------------------------------------------------------------------------------------ > > Key: WFCORE-260 > URL: https://issues.jboss.org/browse/WFCORE-260 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.0.0.Alpha14 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-4013) The value of the bound attribute in socket-binding-group messaging is always false

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-4013?page=com.atlassian.jira.plugin.... ] Jeff Mesnil updated WFLY-4013: ------------------------------ Fix Version/s: 9.0.0.Beta1 > The value of the bound attribute in socket-binding-group messaging is always false > ---------------------------------------------------------------------------------- > > Key: WFLY-4013 > URL: https://issues.jboss.org/browse/WFLY-4013 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: JBoss AS7 7.2.0.Final > Environment: JBoss EAP 6.3.1. > Reporter: Tom Ross > Assignee: Jeff Mesnil > Fix For: 9.0.0.Beta1 > > > The value of bound attribute in messaging socket group is always false. > {noformat} > /socket-binding-group=standard-sockets/socket-binding=messaging:read-resource(include-runtime=true, recursive=true) > { > "outcome" => "success", > "result" => { > "bound" => false, > "bound-address" => undefined, > "bound-port" => undefined, > "client-mappings" => undefined, > "fixed-port" => false, > "interface" => undefined, > "multicast-address" => undefined, > "multicast-port" => undefined, > "name" => "messaging", > "port" => 5445 > } > {noformat} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2014