April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-8032) CheckValidConnectionSQL can open a transaction, preventing application from changing transaction isolation level (PostgreSQL)

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8032?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-8032: ----------------------------- Fix Version/s: 11.0.0.Beta1 > CheckValidConnectionSQL can open a transaction, preventing application from changing transaction isolation level (PostgreSQL) > ----------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-8032 > URL: https://issues.jboss.org/browse/WFLY-8032 > Project: WildFly > Issue Type: Bug > Components: JCA > Affects Versions: 10.1.0.Final > Reporter: Tomas Hofman > Assignee: Tomas Hofman > Fix For: 11.0.0.Beta1 > > > PostgreSQL driver only allows changing the transaction isolation level when transaction is not opened. Under certain circumstances, an application can receive a connection with already opened transaction and an attempt to change transaction isolation level will lead to exception. > This happens with the PostgreSQL driver and with CheckValidConnectionSQL checker configured to run a select statement to verify connections retrieved from the pool. > The scenario is as follows: > # A connection is retrieved from the pool for the 1st app and CheckValidConnectionSQL verifies it by running a select statement (autocommit is set to true by default). This statement is run directly via the jdbc connection, not the wrapper. > # 1st app receives the connection, sets autocommit=false, perform some work and commits a transaction. > # The connection is returned to the pool, {{cleanup()}} method is called on LocalManagedConnection wrapper, which sets autocommit=true. This however doesn't reset autocommit on the wrapped jdbc connection yet, which would only happen just before executing another SQL statement f.i. > # The same connection is retrieved from the pool for the 2nd app and CheckValidConnectionSQL runs the query. Because the jdbc connection has still autocommit=false, new transaction is opened. > # 2nd app receives the connection and calls {{setTransactionIsolation()}}, which throws an exception because the transaction is open. > Possible solution could be that the {{cleanup()}} method propagates the autocommit=true to the wrapped jdbc connection immediately. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8616) Distributed workmanager does not execute work on other nodes than where the work was scheduled

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8616?page=com.atlassian.jira.plugin.... ] Kabir Khan resolved WFLY-8616. ------------------------------ Fix Version/s: 11.0.0.Beta1 Resolution: Done > Distributed workmanager does not execute work on other nodes than where the work was scheduled > ---------------------------------------------------------------------------------------------- > > Key: WFLY-8616 > URL: https://issues.jboss.org/browse/WFLY-8616 > Project: WildFly > Issue Type: Bug > Components: JCA > Reporter: Stefano Maestri > Assignee: Stefano Maestri > Priority: Blocker > Labels: KK-DR17, eap7.1-rfe-blocker, eap71_beta > Fix For: 11.0.0.Beta1 > > > Scenario: we have two EAP servers, both of them have a distributed workmanager set up. We try to schedule some work on one of the servers (via {{scheduleWork()}} and since we have a policy of ALWAYS, the work should be executed on a node different from the one where it was scheduled. However, it is always executed on the same node. > This might be related to or even caused by JBEAP-9418. > I think this is severe enough to warrant a beta blocker label - the DWM can be configured and you can pass work instances to it, but they will never be executed on remote nodes. In effect, policy options other than NEVER do not work. I'm raising the priority to blocker accordingly. > This also blocks EAP7-495. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8628) SwitchIdentityTestCase cannot authenticate

by David Lloyd (JIRA)

David Lloyd created WFLY-8628: --------------------------------- Summary: SwitchIdentityTestCase cannot authenticate Key: WFLY-8628 URL: https://issues.jboss.org/browse/WFLY-8628 Project: WildFly Issue Type: Bug Components: Security Reporter: David Lloyd Fix For: 11.0.0.Beta1 The two SwitchIdentityTestCase classes both attempt a DIGEST-MD5 authentication. For some reason the authentication is rejected. A debug session shows the user name, password, host name, and protocol all seem to match between client and server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8629) SwitchIdentityTestCase cannot authenticate

by David Lloyd (JIRA)

David Lloyd created WFLY-8629: --------------------------------- Summary: SwitchIdentityTestCase cannot authenticate Key: WFLY-8629 URL: https://issues.jboss.org/browse/WFLY-8629 Project: WildFly Issue Type: Bug Components: Security Reporter: David Lloyd Fix For: 11.0.0.Beta1 The two SwitchIdentityTestCase classes both attempt a DIGEST-MD5 authentication. For some reason the authentication is rejected. A debug session shows the user name, password, host name, and protocol all seem to match between client and server. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8627) Legacy FileTimerPersistence is slightly incompatible

by David Lloyd (JIRA)

David Lloyd created WFLY-8627: --------------------------------- Summary: Legacy FileTimerPersistence is slightly incompatible Key: WFLY-8627 URL: https://issues.jboss.org/browse/WFLY-8627 Project: WildFly Issue Type: Bug Components: EJB Reporter: David Lloyd Assignee: David Lloyd Fix For: 11.0.0.Beta1 LegacyTimerFormatTestCase.createTimerService fails because a River v4 unmarshaller cannot read <= 3 data directly. Granted this use was never supported, but it did work. The fix is a one-liner to set the unmarshaller version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8626) Legacy FileTimerPersistence is slightly incompatible

by David Lloyd (JIRA)

David Lloyd created WFLY-8626: --------------------------------- Summary: Legacy FileTimerPersistence is slightly incompatible Key: WFLY-8626 URL: https://issues.jboss.org/browse/WFLY-8626 Project: WildFly Issue Type: Bug Components: EJB Reporter: David Lloyd Assignee: David Lloyd Fix For: 11.0.0.Beta1 LegacyTimerFormatTestCase.createTimerService fails because a River v4 unmarshaller cannot read <= 3 data directly. Granted this use was never supported, but it did work. The fix is a one-liner to set the unmarshaller version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFCORE-2712) Elytron - predefined-filter must have flag required in configurable-sasl-server-factory

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-2712?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFCORE-2712: ------------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Elytron - predefined-filter must have flag required in configurable-sasl-server-factory > --------------------------------------------------------------------------------------- > > Key: WFCORE-2712 > URL: https://issues.jboss.org/browse/WFCORE-2712 > Project: WildFly Core > Issue Type: Bug > Components: Security > Reporter: Josef Cacek > Assignee: Ilia Vassilev > > Change the required flag to true for {{predefined-filter}} attribute in Elytron subsystem. > Elytron resource type {{configurable-sasl-server-factory}} has {{filters}} object-list attribute. Its attribute {{predefined-filter}} is an alternative for {{pattern-filter}} attribute. The {{pattern-filter}} has required flag set to true, but {{predefined-filter}} has it false. It results in possibility to add empty filter: > {code} > /subsystem=elytron/configurable-sasl-server-factory=t1:add(sasl-server-factory=elytron, filters=[{}]) > {"outcome" => "success"} > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8625) Create test case for Elytron Audit Logging

by Jan Tymel (JIRA)

Jan Tymel created WFLY-8625: ------------------------------- Summary: Create test case for Elytron Audit Logging Key: WFLY-8625 URL: https://issues.jboss.org/browse/WFLY-8625 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Jan Tymel Assignee: Jan Tymel -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (ELY-1090) SASL mechanism selection strings with ordering and filtering

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/ELY-1090?page=com.atlassian.jira.plugin.s... ] Kabir Khan resolved ELY-1090. ----------------------------- Resolution: Done > SASL mechanism selection strings with ordering and filtering > ------------------------------------------------------------ > > Key: ELY-1090 > URL: https://issues.jboss.org/browse/ELY-1090 > Project: WildFly Elytron > Issue Type: Enhancement > Components: Authentication Client, Authentication Mechanisms, Authentication Server > Reporter: David Lloyd > Assignee: David Lloyd > Fix For: 1.1.0.Beta38 > > > ELY-129 went much of the way to exploring how authentication client configuration and server auth context should be able to configure mechanism selection automatically. However, there is still a need to do things like: specify mech preference/order, filter mechanisms, or provide a whitelist of allowed mechanisms. > Introduce a selector which allows more detailed criteria to be given for SASL mechanism selection. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8624) Create test case for http-interface authentication secured by Elytron http-authentication-factory

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFLY-8624: ---------------------------------- Summary: Create test case for http-interface authentication secured by Elytron http-authentication-factory Key: WFLY-8624 URL: https://issues.jboss.org/browse/WFLY-8624 Project: WildFly Issue Type: Bug Components: Test Suite Reporter: Ondrej Lukas Create test case for http-interface authentication secured by Elytron http-authentication-factory. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years

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 April 2017