[JBoss JIRA] (ELY-849) Rename setMechanismProperties to setSaslMechanismProperties
by Darran Lofthouse (JIRA)
[ https://issues.jboss.org/browse/ELY-849?page=com.atlassian.jira.plugin.sy... ]
Darran Lofthouse updated ELY-849:
---------------------------------
Fix Version/s: 1.1.0.Beta19
(was: 1.1.0.Beta18)
> Rename setMechanismProperties to setSaslMechanismProperties
> -----------------------------------------------------------
>
> Key: ELY-849
> URL: https://issues.jboss.org/browse/ELY-849
> Project: WildFly Elytron
> Issue Type: Enhancement
> Components: Authentication Client
> Reporter: Darran Lofthouse
> Assignee: Darran Lofthouse
> Priority: Blocker
> Fix For: 1.1.0.Beta19
>
>
> If we later add HTTP mechanisms we have no way to differentiate between HTTP and SASL mechanism properties.
> We could probably share properties and rely on protocol matching in the MatchRule but as a single AuthenticationConfiguration will support both HTTP and SASL I think independent properties will be required.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (WFLY-6215) SessionSynchronization callbacks allow concurrent access to SFSB
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-6215?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-6215:
-----------------------------------------------
Brad Maxwell <bmaxwell(a)redhat.com> changed the Status of [bug 1308993|https://bugzilla.redhat.com/show_bug.cgi?id=1308993] from ASSIGNED to CLOSED
> SessionSynchronization callbacks allow concurrent access to SFSB
> ----------------------------------------------------------------
>
> Key: WFLY-6215
> URL: https://issues.jboss.org/browse/WFLY-6215
> Project: WildFly
> Issue Type: Bug
> Components: EJB
> Affects Versions: 10.0.0.Final
> Reporter: Ryan Emerson
> Assignee: Stuart Douglas
> Priority: Critical
> Labels: downstream_dependency
> Fix For: 10.1.0.CR1, 10.1.0.Final
>
> Attachments: wfly_reproducer.tar.gz
>
>
> Issue first encountered by customer in EAP5 (JBPAPP-11239).
> Assume a local SFSB, B1, with container managed transactions and a calling SFSB, B2, which has bean managed transactions. B1 implements the SessionSynchronization interface.
> When B2's bean managed transaction timesout whilst executing B1.exampleMethod(), B2's transaction aborts and the transaction reaper thread calls B1.afterCompletion(). However, the original worker thread that was executing B1.exampleMethod() continues to execute B1.exampleMethod() until it has completed. Hence it is possible for the B1 SFSB to be accessed concurrently. It is also possible for B1.afterCompletion() to finish executing before B1.exampleMethod().
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months