February 2018 - jboss-jira - Jboss List Archives

[JBoss JIRA] (ELY-1530) Introduce a security provider selector mechanism

by Farah Juma (JIRA)

Farah Juma created ELY-1530: ------------------------------- Summary: Introduce a security provider selector mechanism Key: ELY-1530 URL: https://issues.jboss.org/browse/ELY-1530 Project: WildFly Elytron Issue Type: Enhancement Components: Authentication Client Reporter: Farah Juma ELY-1526 updated the default provider supplier to be an aggregate of: # {{WildFlyElytronProvider}} # The security providers loaded using the service loader mechanism ensuring that any provider that is already an installed provider is skipped # The installed providers This was done to fix a difference in behaviour on JDK 8 vs. JDK 9. In particular, on JDK 9, the security providers were being loaded in a different order, resulting in the WildFlyElytronProvider no longer being loaded first. Some security providers were also being loaded twice - once from the service loader mechanism and once from the installed list of providers. This task follows up on ELY-1526 to introduce a security provider selector mechanism that allows security providers to be selected and ordered based on certain criteria. David Lloyd mentioned the following idea for this in WFLY-9899: {quote} Introduce a security provider selector mechanism that works similarly to the SASL and TLS cipher suite selector mechanisms, which allows providers to be selected and ordered by whatever criteria we can (name, name+version, class name, package name, source module all spring to mind, but there may be more as well including filtering (i.e. allowing only certain service entries of a given provider to "peek through")) {quote} See WFLY-9899 for the full discussion. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9294) Add security configuration for infinispan remote cache store

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9294?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9294: --------------------------------- Summary: Add security configuration for infinispan remote cache store (was: Add encryption/authentication configuration for infinispan remote cache store) > Add security configuration for infinispan remote cache store > ------------------------------------------------------------ > > Key: WFLY-9294 > URL: https://issues.jboss.org/browse/WFLY-9294 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 12.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-9294) Add security configuration for Infinispan remote cache store

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-9294?page=com.atlassian.jira.plugin.... ] Radoslav Husar updated WFLY-9294: --------------------------------- Summary: Add security configuration for Infinispan remote cache store (was: Add security configuration for infinispan remote cache store) > Add security configuration for Infinispan remote cache store > ------------------------------------------------------------ > > Key: WFLY-9294 > URL: https://issues.jboss.org/browse/WFLY-9294 > Project: WildFly > Issue Type: Feature Request > Components: Clustering > Affects Versions: 12.0.0.Beta1 > Reporter: Paul Ferraro > Assignee: Radoslav Husar > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1368) JDBC XAManagedConnection.end could loop endlessly when broadcasting error

by Flavia Rainone (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1368?page=com.atlassian.jira.plugin... ] Flavia Rainone resolved JBJCA-1368. ----------------------------------- Resolution: Done > JDBC XAManagedConnection.end could loop endlessly when broadcasting error > ------------------------------------------------------------------------- > > Key: JBJCA-1368 > URL: https://issues.jboss.org/browse/JBJCA-1368 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > If a connection.end operation broadcasts an error for a XA JDBC connection, it could loop endlessly: > 09/01/2018 14:43:16,805 WARN [com.arjuna.ats.jta] (http task-73) ARJUNA016056: TransactionImple.delistResource - caught exception during delist : XAException.XAER_RMFAIL: oracle.jdbc.xa.OracleXAException > at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1110) > at oracle.jdbc.xa.client.OracleXAResource.end(OracleXAResource.java:436) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:295) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.end(XAResourceWrapperImpl.java:118) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperStatImpl.end(XAResourceWrapperStatImpl.java:96) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:914) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.haltCatchFire(TxConnectionListener.java:768) > at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:468) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:673) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:301) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.end(XAResourceWrapperImpl.java:118) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperStatImpl.end(XAResourceWrapperStatImpl.java:96) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:914) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.haltCatchFire(TxConnectionListener.java:768) > at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:468) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:673) > .... > REPEAT ENDLESSLY > .... > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:301) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.end(XAResourceWrapperImpl.java:118) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperStatImpl.end(XAResourceWrapperStatImpl.java:96) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:914) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.haltCatchFire(TxConnectionListener.java:768) > at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:468) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:673) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:301) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.end(XAResourceWrapperImpl.java:118) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperStatImpl.end(XAResourceWrapperStatImpl.java:96) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:914) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.haltCatchFire(TxConnectionListener.java:768) > at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:468) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:673) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:301) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.end(XAResourceWrapperImpl.java:118) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperStatImpl.end(XAResourceWrapperStatImpl.java:96) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:914) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.haltCatchFire(TxConnectionListener.java:768) > at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:468) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:673) > at org.jboss.jca.adapters.jdbc.xa.XAManagedConnection.end(XAManagedConnection.java:301) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperImpl.end(XAResourceWrapperImpl.java:118) > at org.jboss.jca.core.tx.jbossts.XAResourceWrapperStatImpl.end(XAResourceWrapperStatImpl.java:96) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.delistResource(TransactionImple.java:914) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener.haltCatchFire(TxConnectionListener.java:768) > at org.jboss.jca.core.connectionmanager.listener.AbstractConnectionListener.connectionErrorOccurred(AbstractConnectionListener.java:468) > at org.jboss.jca.adapters.jdbc.BaseWrapperManagedConnection.broadcastConnectionError(BaseWrapperManagedConnection.java:673) > As a result, the reentrant lock/unlock system gets out of hand the lock in the connection is not entirely unlocked. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1356) BaseWrapperManagedConnection.unlock fails to unlock

by Flavia Rainone (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1356?page=com.atlassian.jira.plugin... ] Flavia Rainone resolved JBJCA-1356. ----------------------------------- Fix Version/s: (was: WildFly/IronJacamar 1.4.3.Final) Resolution: Done > BaseWrapperManagedConnection.unlock fails to unlock > --------------------------------------------------- > > Key: JBJCA-1356 > URL: https://issues.jboss.org/browse/JBJCA-1356 > Project: IronJacamar > Issue Type: Bug > Affects Versions: WildFly/IronJacamar 1.4.2.Final > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > There is a possibility of unlock missing the call to reentrantLock.unlock: > {noformat} > protected void unlock() > { > if (tryLock < 0) > return; > if (getLog().isTraceEnabled()) > dumpLockInformation(false); > if (lock.isHeldByCurrentThread()) > lock.unlock(); > } > {noformat} > This bug is random. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBJCA-1369) SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnConnection throws NPE

by Flavia Rainone (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1369?page=com.atlassian.jira.plugin... ] Flavia Rainone resolved JBJCA-1369. ----------------------------------- Resolution: Done > SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnConnection throws NPE > ------------------------------------------------------------------------------- > > Key: JBJCA-1369 > URL: https://issues.jboss.org/browse/JBJCA-1369 > Project: IronJacamar > Issue Type: Bug > Reporter: Flavia Rainone > Assignee: Flavia Rainone > > This happens whenever there is no corresponding connection listener wrapper in the cls map. > Example of the error: > 05/02/2018 12:45:31,558 ERROR [org.jboss.jca.core.connectionmanager.TxConnectionManager] (http task-74) IJ000406: Throwable in returning connection: org.jboss.jca.adapters.jdbc.xa.XAManagedConnection@75c05dd6: java.lang.NullPointerException > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:731) > at org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreConcurrentLinkedDequeManagedConnectionPool.returnConnection(SemaphoreConcurrentLinkedDequeManagedConnectionPool.java:611) > at org.jboss.jca.core.connectionmanager.pool.AbstractPool.returnConnection(AbstractPool.java:849) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.returnManagedConnection(AbstractConnectionManager.java:748) > at org.jboss.jca.core.connectionmanager.listener.TxConnectionListener$TransactionSynchronization.afterCompletion(TxConnectionListener.java:1155) > at org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.invokeAfter(TransactionSynchronizer.java:456) > at org.jboss.jca.core.connectionmanager.transaction.TransactionSynchronizer.afterCompletion(TransactionSynchronizer.java:392) > at org.jboss.as.txn.service.internal.tsr.JCAOrderedLastSynchronizationList.afterCompletion(JCAOrderedLastSynchronizationList.java:163) > at com.arjuna.ats.internal.jta.resources.arjunacore.SynchronizationImple.afterCompletion(SynchronizationImple.java:96) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.afterCompletion(TwoPhaseCoordinator.java:545) > at com.arjuna.ats.arjuna.coordinator.TwoPhaseCoordinator.end(TwoPhaseCoordinator.java:101) > at com.arjuna.ats.arjuna.AtomicAction.commit(AtomicAction.java:162) > at com.arjuna.ats.internal.jta.transaction.arjunacore.TransactionImple.commitAndDisassociate(TransactionImple.java:1200) > at com.arjuna.ats.internal.jta.transaction.arjunacore.BaseTransaction.commit(BaseTransaction.java:126) > at com.arjuna.ats.jbossatx.BaseTransactionManagerDelegate.commit(BaseTransactionManagerDelegate.java:89) > at org.jboss.tm.usertx.client.ServerVMClientUserTransaction.commit(ServerVMClientUserTransaction.java:193) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2357) DMN expand test case for allowed values of simple type collections

by Matteo Mortari (JIRA)

[ https://issues.jboss.org/browse/DROOLS-2357?page=com.atlassian.jira.plugi... ] Matteo Mortari updated DROOLS-2357: ----------------------------------- Summary: DMN expand test case for allowed values of simple type collections (was: DMN expand test case for allowed values of simply type collections) > DMN expand test case for allowed values of simple type collections > ------------------------------------------------------------------ > > Key: DROOLS-2357 > URL: https://issues.jboss.org/browse/DROOLS-2357 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-2357) DMN expand test case for allowed values of simply type collections

by Matteo Mortari (JIRA)

Matteo Mortari created DROOLS-2357: -------------------------------------- Summary: DMN expand test case for allowed values of simply type collections Key: DROOLS-2357 URL: https://issues.jboss.org/browse/DROOLS-2357 Project: Drools Issue Type: Task Components: dmn engine Reporter: Matteo Mortari Assignee: Matteo Mortari -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-55) Support for XAResource in the transaction API and Narayana implementation

by Luis Barreiro (JIRA)

Luis Barreiro created AG-55: ------------------------------- Summary: Support for XAResource in the transaction API and Narayana implementation Key: AG-55 URL: https://issues.jboss.org/browse/AG-55 Project: Agroal Issue Type: Bug Components: api, narayana Affects Versions: 0.4 Reporter: Luis Barreiro Assignee: Luis Barreiro Fix For: 0.5 Building on AG-54 add support for XAResource in the transaction integration. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

1
0
0 / 0

[JBoss JIRA] (AG-54) Support for XAConnection in the pool

by Luis Barreiro (JIRA)

[ https://issues.jboss.org/browse/AG-54?page=com.atlassian.jira.plugin.syst... ] Luis Barreiro resolved AG-54. ----------------------------- Resolution: Done > Support for XAConnection in the pool > ------------------------------------ > > Key: AG-54 > URL: https://issues.jboss.org/browse/AG-54 > Project: Agroal > Issue Type: Bug > Components: pool > Affects Versions: 0.4 > Reporter: Luis Barreiro > Assignee: Luis Barreiro > Fix For: 0.5 > > > The connection pool should be able to support creating and pooling of XAConnection. The major change required is that the ConnectionFactory should be able to create both. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 1 month

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 February 2018