July 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9153) Upgrade Artemis 1.5.5.jbossorg-006

by Jeff Mesnil (JIRA)

[ https://issues.jboss.org/browse/WFLY-9153?page=com.atlassian.jira.plugin.... ] Jeff Mesnil moved JBEAP-12425 to WFLY-9153: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-9153 (was: JBEAP-12425) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JMS (was: ActiveMQ) (was: JMS) > Upgrade Artemis 1.5.5.jbossorg-006 > ---------------------------------- > > Key: WFLY-9153 > URL: https://issues.jboss.org/browse/WFLY-9153 > Project: WildFly > Issue Type: Component Upgrade > Components: JMS > Reporter: Jeff Mesnil > Assignee: Jeff Mesnil > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1312) Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1312?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse commented on ELY-1312: --------------------------------------- We could even take this slightly further and allow these options to apply to other mechanisms - e.g. FORM authentication could use an alternative SCOPE, e.g. specify SSL Scope and without an SSLSession FORM authentication is not possible. This could mean if your connection is clear mechanisms such as Digest or SCRAM are possible but until an SSLSession is established FORM authentication is not possible. It could potentially become a simple form of SSO where a common SSLSession is used across multiple applications. > Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism > ----------------------------------------------------------------------------- > > Key: ELY-1312 > URL: https://issues.jboss.org/browse/ELY-1312 > Project: WildFly Elytron > Issue Type: Enhancement > Components: HTTP > Environment: # > Reporter: Darran Lofthouse > Fix For: 1.2.0.Beta1 > > > Currently the SpnegoAuthenticationMechanism caches against the connection scope and uses the cached GssContext to recreate the identity. > We should consider the following: - > # Using the same cached identity mechanism as is used by FORM authentication. > # Adding configuration to specify which scope to cache against. > # Add an option to disable caching entirely, this would need to take into account cases where continuation is required as that would become unsupported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-151) Avoid Trigger collisions - Sprint-65

by Matt Mahoney (JIRA)

[ https://issues.jboss.org/browse/HAWKULARQE-151?page=com.atlassian.jira.pl... ] Matt Mahoney updated HAWKULARQE-151: ------------------------------------ Description: Avoid Trigger collisions when MIQ is linked to multiple MIQ's Ref Sprint Review: https://www.youtube.com/watch?v=nXLLLv_QyP0&feature=em-subs_digest was: Avoid Trigger collisions when MIQ is linked to multiple MIQ's > Avoid Trigger collisions - Sprint-65 > ------------------------------------ > > Key: HAWKULARQE-151 > URL: https://issues.jboss.org/browse/HAWKULARQE-151 > Project: Hawkular QE > Issue Type: Task > Reporter: Matt Mahoney > Assignee: Michael Foley > > Avoid Trigger collisions when MIQ is linked to multiple MIQ's > Ref Sprint Review: https://www.youtube.com/watch?v=nXLLLv_QyP0&feature=em-subs_digest -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (HAWKULARQE-151) Avoid Trigger collisions - Sprint-65

by Matt Mahoney (JIRA)

Matt Mahoney created HAWKULARQE-151: --------------------------------------- Summary: Avoid Trigger collisions - Sprint-65 Key: HAWKULARQE-151 URL: https://issues.jboss.org/browse/HAWKULARQE-151 Project: Hawkular QE Issue Type: Task Reporter: Matt Mahoney Assignee: Michael Foley Avoid Trigger collisions when MIQ is linked to multiple MIQ's -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ELY-1312) Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism

by Darran Lofthouse (JIRA)

Darran Lofthouse created ELY-1312: ------------------------------------- Summary: Further Scoping and Caching Enhancements to the SpnegoAuthenticationMechanism Key: ELY-1312 URL: https://issues.jboss.org/browse/ELY-1312 Project: WildFly Elytron Issue Type: Enhancement Components: HTTP Environment: # Reporter: Darran Lofthouse Fix For: 1.2.0.Beta1 Currently the SpnegoAuthenticationMechanism caches against the connection scope and uses the cached GssContext to recreate the identity. We should consider the following: - # Using the same cached identity mechanism as is used by FORM authentication. # Adding configuration to specify which scope to cache against. # Add an option to disable caching entirely, this would need to take into account cases where continuation is required as that would become unsupported. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2141) RingBuffer should implement BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2141?page=com.atlassian.jira.plugin.... ] Bela Ban reopened JGRP-2141: ---------------------------- > RingBuffer should implement BlockingQueue > ----------------------------------------- > > Key: JGRP-2141 > URL: https://issues.jboss.org/browse/JGRP-2141 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.5 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2141) RingBuffer should implement BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2141?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2141: --------------------------- Fix Version/s: 4.0.5 (was: 4.1) > RingBuffer should implement BlockingQueue > ----------------------------------------- > > Key: JGRP-2141 > URL: https://issues.jboss.org/browse/JGRP-2141 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.5 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2141) RingBuffer should implement BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2141?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-2141. -------------------------- Resolution: Won't Fix See prev comment > RingBuffer should implement BlockingQueue > ----------------------------------------- > > Key: JGRP-2141 > URL: https://issues.jboss.org/browse/JGRP-2141 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.0.5 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2141) RingBuffer should implement BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2141?page=com.atlassian.jira.plugin.... ] Bela Ban closed JGRP-2141. -------------------------- Resolution: Won't Fix ThreadPoolExecutors in {{TP}} use {{SynchronousQueue}}, so this is not needed and as such closed as moot. > RingBuffer should implement BlockingQueue > ----------------------------------------- > > Key: JGRP-2141 > URL: https://issues.jboss.org/browse/JGRP-2141 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JGRP-2141) RingBuffer should implement BlockingQueue

by Bela Ban (JIRA)

[ https://issues.jboss.org/browse/JGRP-2141?page=com.atlassian.jira.plugin.... ] Bela Ban updated JGRP-2141: --------------------------- Description: Then we could use RingBuffer as queue in ThreadPoolExecutor (was: Then we could use RingBuffer and queue in ThreadPoolExecutor) > RingBuffer should implement BlockingQueue > ----------------------------------------- > > Key: JGRP-2141 > URL: https://issues.jboss.org/browse/JGRP-2141 > Project: JGroups > Issue Type: Enhancement > Reporter: Bela Ban > Assignee: Bela Ban > Priority: Minor > Fix For: 4.1 > > > Then we could use RingBuffer as queue in ThreadPoolExecutor -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 July 2017