October 2019 - jboss-jira - Jboss List Archives

[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)

5 years, 11 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)

5 years, 11 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)

5 years, 11 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)

5 years, 11 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)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12741) Eliminate redundant buffer allocation/copying when marshalling session attributes and EJB instances

by Paul Ferraro (Jira)

Paul Ferraro created WFLY-12741: ----------------------------------- Summary: Eliminate redundant buffer allocation/copying when marshalling session attributes and EJB instances Key: WFLY-12741 URL: https://issues.jboss.org/browse/WFLY-12741 Project: WildFly Issue Type: Bug Components: Clustering Affects Versions: 18.0.0.Final Reporter: Paul Ferraro Assignee: Paul Ferraro A performance optimization for SimpleMarshalledValue inspired by https://github.com/infinispan/infinispan/blob/master/commons/src/main/jav... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12740) Test WildFly s390

by Ken Wills (Jira)

[ https://issues.jboss.org/browse/WFLY-12740?page=com.atlassian.jira.plugin... ] Ken Wills updated WFLY-12740: ----------------------------- Fix Version/s: 19.0.0.Beta1 > Test WildFly s390 > ----------------- > > Key: WFLY-12740 > URL: https://issues.jboss.org/browse/WFLY-12740 > Project: WildFly > Issue Type: Feature Request > Reporter: Ken Wills > Assignee: Ken Wills > Priority: Major > Fix For: 19.0.0.Beta1 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12740) Test WildFly s390

by Ken Wills (Jira)

Ken Wills created WFLY-12740: -------------------------------- Summary: Test WildFly s390 Key: WFLY-12740 URL: https://issues.jboss.org/browse/WFLY-12740 Project: WildFly Issue Type: Feature Request Reporter: Ken Wills Assignee: Ken Wills -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12739) Flash Scope is not cleared when JSF1095 is occurred

by Bartosz Spyrko (Jira)

[ https://issues.jboss.org/browse/WFLY-12739?page=com.atlassian.jira.plugin... ] Bartosz Spyrko updated WFLY-12739: ---------------------------------- Labels: downstream_dependency (was: ) > Flash Scope is not cleared when JSF1095 is occurred > --------------------------------------------------- > > Key: WFLY-12739 > URL: https://issues.jboss.org/browse/WFLY-12739 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > Labels: downstream_dependency > > If committing the response for file download processing and using Flash Scope in the action method are combined as the following code, the Flash Scope will not be cleared in subsequent requests. > {code:java} > try { > // The response is committed by following code. > // Therefore, mojarra can not set csfcfc Cookie to identify FlashScope. > externalContext.responseFlushBuffer(); > facesContext.responseComplete(); > } catch (Exception e) { > e.printStackTrace(); > } > Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash(); > flash.put("business", businessMap); > {code} > In other words, if the below log shows in server.log, the Flash Scope will not be cleared in subsequent requests. > {noformat} > 2019-10-28 10:38:09,180 WARNING [javax.enterprise.resource.webcontainer.jsf.flash] (default task-1) JSF1095: The response was already committed by the time we tried to set the outgoing cookie for the flash. Any values stored to the flash will not be available on the next request. > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12739) Flash Scope is not cleared when JSF1095 is occurred

by Bartosz Spyrko (Jira)

[ https://issues.jboss.org/browse/WFLY-12739?page=com.atlassian.jira.plugin... ] Bartosz Spyrko moved JBEAP-17909 to WFLY-12739: ----------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-12739 (was: JBEAP-17909) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: JSF (was: JSF) Affects Version/s: (was: 7.2.5.CR1) Fix Version/s: (was: 7.3.0.GA) > Flash Scope is not cleared when JSF1095 is occurred > --------------------------------------------------- > > Key: WFLY-12739 > URL: https://issues.jboss.org/browse/WFLY-12739 > Project: WildFly > Issue Type: Bug > Components: JSF > Reporter: Bartosz Spyrko > Assignee: Bartosz Spyrko > Priority: Major > > If committing the response for file download processing and using Flash Scope in the action method are combined as the following code, the Flash Scope will not be cleared in subsequent requests. > {code:java} > try { > // The response is committed by following code. > // Therefore, mojarra can not set csfcfc Cookie to identify FlashScope. > externalContext.responseFlushBuffer(); > facesContext.responseComplete(); > } catch (Exception e) { > e.printStackTrace(); > } > Flash flash = FacesContext.getCurrentInstance().getExternalContext().getFlash(); > flash.put("business", businessMap); > {code} > In other words, if the below log shows in server.log, the Flash Scope will not be cleared in subsequent requests. > {noformat} > 2019-10-28 10:38:09,180 WARNING [javax.enterprise.resource.webcontainer.jsf.flash] (default task-1) JSF1095: The response was already committed by the time we tried to set the outgoing cookie for the flash. Any values stored to the flash will not be available on the next request. > {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 11 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 October 2019