December 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12882) Add user API to handle merging HttpSession attributes/metadata on partition merge

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12882: ----------------------------------- Summary: Add user API to handle merging HttpSession attributes/metadata on partition merge Key: WFLY-12882 URL: https://issues.redhat.com/browse/WFLY-12882 Project: WildFly Issue Type: Feature Request Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12881) Cannot customize split detection and merge policy for Infinispan partition handling

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12881: ----------------------------------- Summary: Cannot customize split detection and merge policy for Infinispan partition handling Key: WFLY-12881 URL: https://issues.redhat.com/browse/WFLY-12881 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.1.Final Reporter: Paul Ferraro Assignee: Paul Ferraro Currently, when partition handling is enabled on a cache, both reads and writes are denied on minority partitions (of a given segment) and upon partition merge, and critically, no data reconciliation occurs. This is effectively hard coded, and users do not have the ability to customize this. Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12881) Cannot customize split detection and merge policy for Infinispan partition handling

by Paul Ferraro (Jira)

[ https://issues.redhat.com/browse/WFLY-12881?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFLY-12881: -------------------------------- Priority: Critical (was: Major) > Cannot customize split detection and merge policy for Infinispan partition handling > ----------------------------------------------------------------------------------- > > Key: WFLY-12881 > URL: https://issues.redhat.com/browse/WFLY-12881 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > > Currently, when partition handling is enabled on a cache, both reads and writes are denied on minority partitions (of a given segment) and upon partition merge, and critically, no data reconciliation occurs. This is effectively hard coded, and users do not have the ability to customize this. Users need to be able to configure this, at least to support the built in read/write on split policy and the built-in merge policies. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1035) Wizard - TLS MUTUAL

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1035?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan commented on SWSQE-1035: --------------------------------------- https://github.com/Kiali-QE/kiali-qe-python/pull/227 > Wizard - TLS MUTUAL > ------------------- > > Key: SWSQE-1035 > URL: https://issues.redhat.com/browse/SWSQE-1035 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Client Certificate > Private Key -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (SWSQE-1035) Wizard - TLS MUTUAL

by Hayk Hovsepyan (Jira)

[ https://issues.redhat.com/browse/SWSQE-1035?page=com.atlassian.jira.plugi... ] Hayk Hovsepyan resolved SWSQE-1035. ----------------------------------- Resolution: Done > Wizard - TLS MUTUAL > ------------------- > > Key: SWSQE-1035 > URL: https://issues.redhat.com/browse/SWSQE-1035 > Project: Kiali QE > Issue Type: QE Task > Reporter: Hayk Hovsepyan > Assignee: Hayk Hovsepyan > Priority: Major > Labels: automation > > Client Certificate > Private Key -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1398) Connection leak when there is an exception during getConnection for NoTransaction resource adapter

by Stefano Maestri (Jira)

[ https://issues.redhat.com/browse/JBJCA-1398?page=com.atlassian.jira.plugi... ] Stefano Maestri resolved JBJCA-1398. ------------------------------------ Resolution: Done > Connection leak when there is an exception during getConnection for NoTransaction resource adapter > -------------------------------------------------------------------------------------------------- > > Key: JBJCA-1398 > URL: https://issues.redhat.com/browse/JBJCA-1398 > Project: IronJacamar > Issue Type: Bug > Components: Core > Affects Versions: 1.0.31.Final, 1.0.38.Final, 1.4.10 > Reporter: Stephen Fikes > Assignee: Stefano Maestri > Priority: Major > Labels: downstream_dependency > > When an exception occurs with a {{NoTransaction}} resource adapter during a {{getConnection}} attempt the pool leaks the connection. The exception (simulating a timeout of the underlying connect attempt) detail is below. > {code} > ... WARNING [support.jboss.ejb.session.SessionBean] (ServerService Thread Pool -- 51) Failed to get a connection: IJ000456: Unchecked throwable in ManagedConnection.getConnection() cl=org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@1a933f80[state=NORMAL managed connection=support.redhat.jboss.jca.ManagedConnectionImpl@7a294431 connection handles=0 lastUse=1575419355891 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@1d6a5362 pool internal context=SemaphoreArrayListManagedConnectionPool@2f47607f[pool=EisConnectionFactory]]: javax.resource.ResourceException: IJ000456: Unchecked throwable in ManagedConnection.getConnection() cl=org.jboss.jca.core.connectionmanager.listener.NoTxConnectionListener@1a933f80[state=NORMAL managed connection=support.redhat.jboss.jca.ManagedConnectionImpl@7a294431 connection handles=0 lastUse=1575419355891 trackByTx=false pool=org.jboss.jca.core.connectionmanager.pool.strategy.OnePool@1d6a5362 pool internal context=SemaphoreArrayListManagedConnectionPool@2f47607f[pool=EisConnectionFactory]] > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:521) > at support.redhat.jboss.jca.ConnectionFactoryImpl.getConnection(ConnectionFactoryImpl.java:61) > ... > Caused by: javax.resource.ResourceException: Simulate timeout > at support.redhat.jboss.jca.ManagedConnectionImpl.getConnection(ManagedConnectionImpl.java:61) > at org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:508) > ... > {code} > There seems to be a difference in a {{NoTransaction}} and an {{XATransaction}} adapter where {{returnConnection}} is triggered by the {{TxConnectionManagerImpl}}. > {code} > ... [BMAN] org.jboss.jca.core.connectionmanager.pool.mcp.SemaphoreArrayListManagedConnectionPool.returnConnection(SemaphoreArrayListManagedConnectionPool.java:-1) > ... org.jboss.jca.core.connectionmanager.pool.AbstractPool.returnConnection(AbstractPool.java:633) > ... org.jboss.jca.core.connectionmanager.AbstractConnectionManager.returnManagedConnection(AbstractConnectionManager.java:456) > ... org.jboss.jca.core.connectionmanager.tx.TxConnectionManagerImpl.managedConnectionDisconnected(TxConnectionManagerImpl.java:515) > ... org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:525) > {code} > For a {{NoTransaction}} adapter, however, the abstract implementation is used: > {code} > ... [BMAN] org.jboss.jca.core.connectionmanager.AbstractConnectionManager.managedConnectionDisconnected(AbstractConnectionManager.java:697) > ... org.jboss.jca.core.connectionmanager.AbstractConnectionManager.allocateConnection(AbstractConnectionManager.java:525) > {code} > The empty implementation for [AbstractConnectionManager.managedConnectionDisconnected|https://github.co...] does nothing so the connection is not returned as it would be for a transactional implementation. > I also see the same issue with IronJacamar 1.4.18.Final so this issue remains in the latest release. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12867) Upgrade IronJacamar from 1.4.19.Final to 1.4.20.Final

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12867?page=com.atlassian.jira.plugi... ] Ilia Vassilev updated WFLY-12867: --------------------------------- Description: (was: Upgrade IronJacamar from 1.4.18.Final to 1.4.19.Final) > Upgrade IronJacamar from 1.4.19.Final to 1.4.20.Final > ----------------------------------------------------- > > Key: WFLY-12867 > URL: https://issues.redhat.com/browse/WFLY-12867 > Project: WildFly > Issue Type: Component Upgrade > Components: JCA > Reporter: Ilia Vassilev > Assignee: Stefano Maestri > Priority: Critical > Labels: downstream_dependency > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12880) Upgrade Jaeger client to 1.1.0

by Emmanuel Hugonnet (Jira)

Emmanuel Hugonnet created WFLY-12880: ---------------------------------------- Summary: Upgrade Jaeger client to 1.1.0 Key: WFLY-12880 URL: https://issues.redhat.com/browse/WFLY-12880 Project: WildFly Issue Type: Component Upgrade Components: MP OpenTracing Affects Versions: 18.0.1.Final Reporter: Emmanuel Hugonnet Assignee: Emmanuel Hugonnet Upgrade Jaeger client to 1.1.0 -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12879) Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12879?page=com.atlassian.jira.plugi... ] Ilia Vassilev moved JBEAP-18320 to WFLY-12879: ---------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12879 (was: JBEAP-18320) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Build System (was: Build System) Fix Version/s: (was: 7.3.1.GA) > Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final > ---------------------------------------------------------- > > Key: WFLY-12879 > URL: https://issues.redhat.com/browse/WFLY-12879 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Ilia Vassilev > Priority: Major > > https://github.com/wildfly/jboss-ejb-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 5 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12879) Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final

by Ilia Vassilev (Jira)

[ https://issues.redhat.com/browse/WFLY-12879?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFLY-12879: ------------------------------------ Assignee: Tomasz Adamski (was: Ilia Vassilev) > Upgrade jboss-ejb-client from 4.0.27.Final to 4.0.28.Final > ---------------------------------------------------------- > > Key: WFLY-12879 > URL: https://issues.redhat.com/browse/WFLY-12879 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System > Reporter: Ilia Vassilev > Assignee: Tomasz Adamski > Priority: Major > > https://github.com/wildfly/jboss-ejb-client -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 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 December 2019