April 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-738) Add clear cache operation on cache container and cache (accessible via admin console)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-738?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-738: ---------------------------------- Assignee: Paul Ferraro (was: Brian Stansberry) > Add clear cache operation on cache container and cache (accessible via admin console) > ------------------------------------------------------------------------------------- > > Key: WFLY-738 > URL: https://issues.jboss.org/browse/WFLY-738 > Project: WildFly > Issue Type: Feature Request > Components: Clustering, Domain Management > Reporter: Guillaume Grossetie > Assignee: Paul Ferraro > Fix For: Awaiting Volunteers > > > Add operation on infinispan subsystem to clear cache at cache container level (ie. clear all caches for the container) and at cache level. > The implementation of the clear operation just calls the method #clear() on the org.infinispan.Cache interface. If needed we can clear the associated CacheStore (make it optional ?) and handle more complex cases. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1051) Indicate failed deployment within the web console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-1051?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-1051: ----------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Indicate failed deployment within the web console > ------------------------------------------------- > > Key: WFLY-1051 > URL: https://issues.jboss.org/browse/WFLY-1051 > Project: WildFly > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-734) Deadlock detection for Entity beans

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-734?page=com.atlassian.jira.plugin.s... ] Brian Stansberry resolved WFLY-734. ----------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: Awaiting Volunteers) Resolution: Won't Fix Support for CMP has been dropped for WildFly 8. > Deadlock detection for Entity beans > ----------------------------------- > > Key: WFLY-734 > URL: https://issues.jboss.org/browse/WFLY-734 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Environment: Windows 7 64 bit, Java 1.7.0 64 bit > Reporter: Christian Inzko > Fix For: 8.0.0.Alpha1 > > > Deadlock detection with EJB 2.1 entity beans and pessimistic locking does not work. > We are migrating our application from Jboss 4.05 where we used entity beans. This jboss version was able to detect deadlock situations and throw a org.jboss.util.deadlock.ApplicationDeadlockException. This mechanism does no longer work - instead of that both transactions just hang until a transaction timeout is reached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-731) Store config file comments in the model

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-731?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-731: ---------------------------------- Assignee: (was: Brian Stansberry) > Store config file comments in the model > --------------------------------------- > > Key: WFLY-731 > URL: https://issues.jboss.org/browse/WFLY-731 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Fix For: Awaiting Volunteers > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-733) Expose tatletale management operations

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-733?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-733: ---------------------------------- Assignee: (was: Brian Stansberry) > Expose tatletale management operations > -------------------------------------- > > Key: WFLY-733 > URL: https://issues.jboss.org/browse/WFLY-733 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Heiko Braun > Fix For: Awaiting Volunteers > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-724) Provide the ability to invoke datasource operations on a server level (domain mode)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-724?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-724: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Provide the ability to invoke datasource operations on a server level (domain mode) > ----------------------------------------------------------------------------------- > > Key: WFLY-724 > URL: https://issues.jboss.org/browse/WFLY-724 > Project: WildFly > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: No Release > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-734) Deadlock detection for Entity beans

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-734?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-734: ---------------------------------- Assignee: (was: Brian Stansberry) > Deadlock detection for Entity beans > ----------------------------------- > > Key: WFLY-734 > URL: https://issues.jboss.org/browse/WFLY-734 > Project: WildFly > Issue Type: Feature Request > Components: EJB > Environment: Windows 7 64 bit, Java 1.7.0 64 bit > Reporter: Christian Inzko > Fix For: Awaiting Volunteers > > > Deadlock detection with EJB 2.1 entity beans and pessimistic locking does not work. > We are migrating our application from Jboss 4.05 where we used entity beans. This jboss version was able to detect deadlock situations and throw a org.jboss.util.deadlock.ApplicationDeadlockException. This mechanism does no longer work - instead of that both transactions just hang until a transaction timeout is reached. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-723) Wildcard operations that span multiple processes

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-723?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-723: ---------------------------------- Assignee: Emanuel Muckenhuber (was: Brian Stansberry) > Wildcard operations that span multiple processes > ------------------------------------------------ > > Key: WFLY-723 > URL: https://issues.jboss.org/browse/WFLY-723 > Project: WildFly > Issue Type: Feature Request > Components: Domain Management > Reporter: Brian Stansberry > Assignee: Emanuel Muckenhuber > Labels: as7-ignored > Fix For: Awaiting Volunteers > > > Handle host=* and host=y,server=* type operations. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-701) Complete interface management from the console

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-701?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-701: ---------------------------------- Assignee: Heiko Braun (was: Brian Stansberry) > Complete interface management from the console > ---------------------------------------------- > > Key: WFLY-701 > URL: https://issues.jboss.org/browse/WFLY-701 > Project: WildFly > Issue Type: Feature Request > Reporter: Heiko Braun > Assignee: Heiko Braun > Fix For: No Release > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-713) Ability to specify a delay between URL round-robin attempts in HA datasource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-713?page=com.atlassian.jira.plugin.s... ] Brian Stansberry updated WFLY-713: ---------------------------------- Assignee: (was: Brian Stansberry) > Ability to specify a delay between URL round-robin attempts in HA datasource > ---------------------------------------------------------------------------- > > Key: WFLY-713 > URL: https://issues.jboss.org/browse/WFLY-713 > Project: WildFly > Issue Type: Feature Request > Components: JCA > Reporter: Daniel Marchese > Fix For: Awaiting Volunteers > > > We have a configuration with Oracle RAC One Node (1 active database, 1 standby database) and we are testing HA possibilities. > In one test, if we try to obtain a connection during the starting of the standby database after the active database crash, we get an ORA-12514 error because the standby instance is not ready to respond. > Besides the fact that Oracle should not return an error but wait for the standby database to be ready to respond, it would be interesting if it was possible to specify a delay between URL round-roubin attempts in the HA datasource (ex: url-retry-wait-millis). > This way, it would be possible to ask JBoss to wait before it tries the next URL in the list, giving the standby database the time to start. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 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 2013