October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-12744) Elytron as MPs config source

by Tobias Stadler (Jira)

Tobias Stadler created WFLY-12744: ------------------------------------- Summary: Elytron as MPs config source Key: WFLY-12744 URL: https://issues.jboss.org/browse/WFLY-12744 Project: WildFly Issue Type: Feature Request Components: MP Config Reporter: Tobias Stadler Assignee: Jeff Mesnil I would like to be able to use credentials managed by the elytron subsytem in my application by using the microprofile config api. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ELY-1897) HashiCorp Vault as credential source

by Tobias Stadler (Jira)

Tobias Stadler created ELY-1897: ----------------------------------- Summary: HashiCorp Vault as credential source Key: ELY-1897 URL: https://issues.jboss.org/browse/ELY-1897 Project: WildFly Elytron Issue Type: Feature Request Reporter: Tobias Stadler Assignee: Darran Lofthouse I would like to be able to use HashiCorp Vault as source for my datasource credentials -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4719) DMN editor: Update DRG icon

by Elizabeth Clayton (Jira)

Elizabeth Clayton created DROOLS-4719: ----------------------------------------- Summary: DMN editor: Update DRG icon Key: DROOLS-4719 URL: https://issues.jboss.org/browse/DROOLS-4719 Project: Drools Issue Type: Enhancement Components: DMN Editor Reporter: Elizabeth Clayton Assignee: Guilherme Gomes Update the DRG icon in the Navigator tree from: https://fontawesome.com/icons/share-alt?style=solid - to - https://fontawesome.com/icons/sitemap?style=solid Consider replacing the "automatic layout" with a different icon, maybe: https://fontawesome.com/icons/layer-group?style=solid? -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12718) Clustering: replicated-cache sampling errors

by Paul Ferraro (Jira)

[ https://issues.jboss.org/browse/WFLY-12718?page=com.atlassian.jira.plugin... ] Paul Ferraro commented on WFLY-12718: ------------------------------------- [~tommaso-borgato] If you bump the suspend timeout to 5 seconds, do the sampling errors go down to zero (or close to it)? > Clustering: replicated-cache sampling errors > -------------------------------------------- > > Key: WFLY-12718 > URL: https://issues.jboss.org/browse/WFLY-12718 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 18.0.0.Final > Reporter: Tommasso Borgato > Assignee: Paul Ferraro > Priority: Blocker > > The issue is about replicated-cache in fail-over tests. > WildFly is started in clustered mode using a replicated cache for replicating HTTP session data across cluster nodes; all 4 nodes in the cluster are initialized with the following cli script: > {noformat} > embed-server --server-config=standalone-ha.xml > /subsystem=jgroups/channel=ee:write-attribute(name=stack,value=tcp) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl:add() > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=locking:write-attribute(name=isolation, value=REPEATABLE_READ) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/component=transaction:write-attribute(name=mode, value=BATCH) > /subsystem=infinispan/cache-container=web/replicated-cache=testRepl/store=file:add() > /subsystem=infinispan/cache-container=web:write-attribute(name=default-cache, value=testRepl) > {noformat} > The test is run with wildfly-18.0.0.Final.zip; > The same tests run with version wildfly-17.0.1.Final.zip do not have any problem; > hence this looks like a regression; > As usual, we test that the serial value stored in the replicated cache is incremented at every call: when this is not true, we say we have a sampling error; > Here are the runs that exhibit this issue: > - **22.82% Fail Rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#23|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#24|https://eap-qe-jenkins.r...] > We also repeated the tests to make sure it can be reproduced: > - **22.75% Fail rate with WildFly-18 ** [eap-7.x-clustering-http-session-shutdown-repl#26|https://eap-qe-jenkins.r...] > - **0% Fail Rate with WildFly-17 ** [eap-7.x-clustering-http-session-shutdown-repl#25|https://eap-qe-jenkins.r...] -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12733: ----------------------------------------- Hi [~rhn-support-rhsilva]! I have the same question about that class/method. > EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment > -------------------------------------------------------------------------------------- > > Key: WFLY-12733 > URL: https://issues.jboss.org/browse/WFLY-12733 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Rhuan Rocha > Assignee: Cheng Fang > Priority: Major > > The EJB Timer has a way to persist timers in a database using datasources. It is described [here|https://docs.jboss.org/author/display/WFLY10/EJB3+Clustered+Database...]. The database-data-store has an attribute called refresh-interval that define a time in milliseconds to refresh the timers reading the timers from database. Look this sample of configuration. > > {code:java} > <data-stores> > <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/> > <database-data-store name="clustered-store" datasource-jndi-name="java:/jdbc/MyDataSource" partition="timer" refresh-interval="60000" allow-execution="true"/> > </data-stores> > {code} > The RFE is to Wildfly provide a way to force the refresh programmatically. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment

by Rhuan Rocha (Jira)

[ https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin... ] Rhuan Rocha commented on WFLY-12733: ------------------------------------ [~brian.stansberry] I sent a pull request. I have created a method in TimerServiceImpl to call refresh the DatabaseTimerPersistence > EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment > -------------------------------------------------------------------------------------- > > Key: WFLY-12733 > URL: https://issues.jboss.org/browse/WFLY-12733 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Rhuan Rocha > Assignee: Cheng Fang > Priority: Major > > The EJB Timer has a way to persist timers in a database using datasources. It is described [here|https://docs.jboss.org/author/display/WFLY10/EJB3+Clustered+Database...]. The database-data-store has an attribute called refresh-interval that define a time in milliseconds to refresh the timers reading the timers from database. Look this sample of configuration. > > {code:java} > <data-stores> > <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/> > <database-data-store name="clustered-store" datasource-jndi-name="java:/jdbc/MyDataSource" partition="timer" refresh-interval="60000" allow-execution="true"/> > </data-stores> > {code} > The RFE is to Wildfly provide a way to force the refresh programmatically. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin... ] Brian Stansberry commented on WFLY-12733: ----------------------------------------- DatabaseTimerPersistence is an internal class so adding API to it has no effect. Are you also looking for the addition of management operation to call this? [~cfang] This would need to go through the WildFly RFE process. > EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment > -------------------------------------------------------------------------------------- > > Key: WFLY-12733 > URL: https://issues.jboss.org/browse/WFLY-12733 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Rhuan Rocha > Assignee: Cheng Fang > Priority: Major > > The EJB Timer has a way to persist timers in a database using datasources. It is described [here|https://docs.jboss.org/author/display/WFLY10/EJB3+Clustered+Database...]. The database-data-store has an attribute called refresh-interval that define a time in milliseconds to refresh the timers reading the timers from database. Look this sample of configuration. > > {code:java} > <data-stores> > <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/> > <database-data-store name="clustered-store" datasource-jndi-name="java:/jdbc/MyDataSource" partition="timer" refresh-interval="60000" allow-execution="true"/> > </data-stores> > {code} > The RFE is to Wildfly provide a way to force the refresh programmatically. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12733) EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-12733?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-12733: --------------------------------------- Component/s: EJB Assignee: Cheng Fang (was: Brian Stansberry) > EJB Timers: Forcing refresh timers in a database-data-store in a clustered environment > -------------------------------------------------------------------------------------- > > Key: WFLY-12733 > URL: https://issues.jboss.org/browse/WFLY-12733 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Reporter: Rhuan Rocha > Assignee: Cheng Fang > Priority: Major > > The EJB Timer has a way to persist timers in a database using datasources. It is described [here|https://docs.jboss.org/author/display/WFLY10/EJB3+Clustered+Database...]. The database-data-store has an attribute called refresh-interval that define a time in milliseconds to refresh the timers reading the timers from database. Look this sample of configuration. > > {code:java} > <data-stores> > <file-data-store name="default-file-store" path="timer-service-data" relative-to="jboss.server.data.dir"/> > <database-data-store name="clustered-store" datasource-jndi-name="java:/jdbc/MyDataSource" partition="timer" refresh-interval="60000" allow-execution="true"/> > </data-stores> > {code} > The RFE is to Wildfly provide a way to force the refresh programmatically. -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12743) Upgrade IronJacamar from 1.4.18.Final to 1.4.19.Final

by James Perkins (Jira)

James Perkins created WFLY-12743: ------------------------------------ Summary: Upgrade IronJacamar from 1.4.18.Final to 1.4.19.Final Key: WFLY-12743 URL: https://issues.jboss.org/browse/WFLY-12743 Project: WildFly Issue Type: Component Upgrade Components: JCA Reporter: James Perkins Assignee: Stefano Maestri Fix For: 19.0.0.Beta1 Upgrade IronJacamar from 1.4.18.Final to 1.4.19.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12742) Upgrade IronJacamar from 1.4.18.Final to 1.4.19.Final

by James Perkins (Jira)

James Perkins created WFLY-12742: ------------------------------------ Summary: Upgrade IronJacamar from 1.4.18.Final to 1.4.19.Final Key: WFLY-12742 URL: https://issues.jboss.org/browse/WFLY-12742 Project: WildFly Issue Type: Component Upgrade Components: JCA Reporter: James Perkins Assignee: Stefano Maestri Fix For: 19.0.0.Beta1 Upgrade IronJacamar from 1.4.18.Final to 1.4.19.Final -- This message was sent by Atlassian Jira (v7.13.8#713008)

2 years, 6 months

1
0
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2019