April 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-2611) Upgrade WildFly Client Config to 1.0.0.Beta3

by David Lloyd (JIRA)

David Lloyd created WFCORE-2611: ----------------------------------- Summary: Upgrade WildFly Client Config to 1.0.0.Beta3 Key: WFCORE-2611 URL: https://issues.jboss.org/browse/WFCORE-2611 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta13 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2610) Upgrade XNIO to 3.5.0.Beta4

by David Lloyd (JIRA)

David Lloyd created WFCORE-2610: ----------------------------------- Summary: Upgrade XNIO to 3.5.0.Beta4 Key: WFCORE-2610 URL: https://issues.jboss.org/browse/WFCORE-2610 Project: WildFly Core Issue Type: Component Upgrade Reporter: David Lloyd Assignee: David Lloyd Fix For: 3.0.0.Beta13 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-2609) CLIRolloutPlanTestCase hang

by Brian Stansberry (JIRA)

Brian Stansberry created WFCORE-2609: ---------------------------------------- Summary: CLIRolloutPlanTestCase hang Key: WFCORE-2609 URL: https://issues.jboss.org/browse/WFCORE-2609 Project: WildFly Core Issue Type: Bug Components: Domain Management, Test Suite Reporter: Brian Stansberry Priority: Critical Fix For: 3.0.0.Beta13 Hang: https://ci.wildfly.org/viewLog.html?buildId=53176&buildTypeId=WF_MasterWi... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

by Radoslav Husar (JIRA)

[ https://issues.jboss.org/browse/WFLY-8488?page=com.atlassian.jira.plugin.... ] Radoslav Husar commented on WFLY-8488: -------------------------------------- [~meetoblivion] Can you reproduce on master? Did you set the datasource reference on JDBC_PING protocol resource? e.g. /subsystem=jgroups/stack=tcp/protocol=JDBC_PING:add(data-source=ExampleDS) If that still fails, can you post configuration and stack trace? > Usage of JGroups JDBC_PING attempts to delete row too late > ---------------------------------------------------------- > > Key: WFLY-8488 > URL: https://issues.jboss.org/browse/WFLY-8488 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: John Ament > Assignee: Paul Ferraro > > I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down. > In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8488) Usage of JGroups JDBC_PING attempts to delete row too late

by John Ament (JIRA)

John Ament created WFLY-8488: -------------------------------- Summary: Usage of JGroups JDBC_PING attempts to delete row too late Key: WFLY-8488 URL: https://issues.jboss.org/browse/WFLY-8488 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 10.1.0.Final Reporter: John Ament Assignee: Paul Ferraro I was recently working on spinning up a Keycloak cluster. We're deployed to AWS, can't leverage UDP and wanted to have a discovery mechanism that was easy to use, so tried out JDBC_PING. While I got the cluster running, when shutting down a node I would receive an exception on the console when attempting to remove the node from the cluster. It attempts to do a delete on the row in the database after the DataSource has been shut down. In my setup, I'm pointing JGroups at the same DataSource as Keycloak, I'm not using the properties approach. I can switch to the properties approach, but I would prefer a single pool rather than multiple connections. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8485) Upgrade Narayana to 5.5.6.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8485?page=com.atlassian.jira.plugin.... ] Kabir Khan reopened WFLY-8485: ------------------------------ > Upgrade Narayana to 5.5.6.Final > ------------------------------- > > Key: WFLY-8485 > URL: https://issues.jboss.org/browse/WFLY-8485 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 11.0.0.Beta1 > > > https://issues.jboss.org/projects/JBTM/versions/12334093 > https://github.com/jbosstm/narayana/compare/5.5.5.Final...5.5.6.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-8485) Upgrade Narayana to 5.5.6.Final

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-8485?page=com.atlassian.jira.plugin.... ] Kabir Khan commented on WFLY-8485: ---------------------------------- @psakar merged, leaving unresolved until we have the prod upgrade > Upgrade Narayana to 5.5.6.Final > ------------------------------- > > Key: WFLY-8485 > URL: https://issues.jboss.org/browse/WFLY-8485 > Project: WildFly > Issue Type: Component Upgrade > Components: Transactions > Reporter: Tom Jenkinson > Assignee: Tom Jenkinson > Fix For: 11.0.0.Beta1 > > > https://issues.jboss.org/projects/JBTM/versions/12334093 > https://github.com/jbosstm/narayana/compare/5.5.5.Final...5.5.6.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2017