March 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (AS7-6655) binding subcontexts with <lookup> does not work

by James Livingston (JIRA)

James Livingston created AS7-6655: ------------------------------------- Summary: binding subcontexts with <lookup> does not work Key: AS7-6655 URL: https://issues.jboss.org/browse/AS7-6655 Project: Application Server 7 Issue Type: Bug Components: Naming Affects Versions: 7.1.3.Final (EAP) Reporter: James Livingston Assignee: Eduardo Martins If you attempt to bind a subcontext via <lookup> in the naming subsystem it will fail when anything is looked up under it. To reproduce, add <lookup name="java:jboss/ds" lookup="java:jboss/datasources"/>, and then look up something under java:jboss/ds/ In ServiceBasedNamingStore.lookup() it needs to return a ResolveResult, but the (!(obj instanceof NamingContext)) check skips it. As a work-around, you can write an object factory which looks up the sub-context and then returns a wrapper around it, a Context implementation which simply delegates all methods to the original context. Since that wrapper is not a NamingContext instance, it works. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-6357) ejb timer service creates empty directories for all ejbs including those without timers

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6357?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-6357. --------------------------------- Fix Version/s: 8.0.0.Alpha1 Resolution: Done > ejb timer service creates empty directories for all ejbs including those without timers > --------------------------------------------------------------------------------------- > > Key: AS7-6357 > URL: https://issues.jboss.org/browse/AS7-6357 > Project: Application Server 7 > Issue Type: Bug > Components: EJB > Affects Versions: 7.1.3.Final (EAP) > Reporter: Brad Maxwell > Assignee: Stuart Douglas > Priority: Minor > Labels: directory, ejb, timer > Fix For: 8.0.0.Alpha1 > > > ejb timer service creates empty directories for all ejbs include those without timers > Empty directories are being created for all ejbs, even those that do not use timers. > $JBOSS_HOME/.../data/timer-service-data/ -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-6653) Add clustered database based timers

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-6653?page=com.atlassian.jira.plugin.s... ] Stuart Douglas reassigned AS7-6653: ----------------------------------- Assignee: Stuart Douglas (was: jaikiran pai) > Add clustered database based timers > ----------------------------------- > > Key: AS7-6653 > URL: https://issues.jboss.org/browse/AS7-6653 > Project: Application Server 7 > Issue Type: Feature Request > Components: EJB > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > Clustering should be supported for database timers. > The general ideal will be that a single database is shared by all nodes in the cluster. When a timer is created it will be inserted into the database. Periodically at a configured interval nodes will refresh their list of active timers from the database. > When a timer expires a node will attempt to grab ownership of the timer in the database by updating the row. Due to the use of either optimisitic locking or traditional DB locks only 1 node will be successful, and that node will run the task. > We will also support write only nodes, nodes that can create timer tasks, but do not attempt to run them, to allow timer tasks to be run by a subset of the nodes. > So that you don't have hundreds of existing partition name feature will allow clustered timers to be grouped into smaller partitions, so you can limit the number of nodes that are contending for a timer. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-6654) Add ability to migrate timers between data stores

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-6654: ----------------------------------- Summary: Add ability to migrate timers between data stores Key: AS7-6654 URL: https://issues.jboss.org/browse/AS7-6654 Project: Application Server 7 Issue Type: Feature Request Components: EJB Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 8.0.0.Alpha1 It should be possible to move timers between data stores, so that timers can be migrated from the legacy file store. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-6653) Add clustered database based timers

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-6653: ----------------------------------- Summary: Add clustered database based timers Key: AS7-6653 URL: https://issues.jboss.org/browse/AS7-6653 Project: Application Server 7 Issue Type: Feature Request Components: EJB Reporter: Stuart Douglas Assignee: jaikiran pai Fix For: 8.0.0.Alpha1 Clustering should be supported for database timers. The general ideal will be that a single database is shared by all nodes in the cluster. When a timer is created it will be inserted into the database. Periodically at a configured interval nodes will refresh their list of active timers from the database. When a timer expires a node will attempt to grab ownership of the timer in the database by updating the row. Due to the use of either optimisitic locking or traditional DB locks only 1 node will be successful, and that node will run the task. We will also support write only nodes, nodes that can create timer tasks, but do not attempt to run them, to allow timer tasks to be run by a subset of the nodes. So that you don't have hundreds of existing partition name feature will allow clustered timers to be grouped into smaller partitions, so you can limit the number of nodes that are contending for a timer. -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-6652) Add ability to customise timer SQL based on database type

by Stuart Douglas (JIRA)

Stuart Douglas created AS7-6652: ----------------------------------- Summary: Add ability to customise timer SQL based on database type Key: AS7-6652 URL: https://issues.jboss.org/browse/AS7-6652 Project: Application Server 7 Issue Type: Feature Request Components: EJB Reporter: Stuart Douglas Assignee: Stuart Douglas Fix For: 8.0.0.Alpha1 -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-1534) Ability to use alternate persistent stores for EJB timers

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/AS7-1534?page=com.atlassian.jira.plugin.s... ] Stuart Douglas resolved AS7-1534. --------------------------------- Fix Version/s: 8.0.0.Alpha1 (was: 7.2.0.Alpha1) Resolution: Done > Ability to use alternate persistent stores for EJB timers > --------------------------------------------------------- > > Key: AS7-1534 > URL: https://issues.jboss.org/browse/AS7-1534 > Project: Application Server 7 > Issue Type: Feature Request > Components: EJB > Affects Versions: 7.0.1.Final > Reporter: Stuart Douglas > Assignee: Stuart Douglas > Fix For: 8.0.0.Alpha1 > > > We need the ability to store persistent timers in a JDBC database -- 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, 10 months

1
0
0 / 0

[JBoss JIRA] (AS7-3199) RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present

by Bill Burke (JIRA)

[ https://issues.jboss.org/browse/AS7-3199?page=com.atlassian.jira.plugin.s... ] Bill Burke commented on AS7-3199: --------------------------------- I have a pull request for trunk that only barfs if there are multiple Application classes annotated with @ApplicationPath and ignore any other non-annotated Application class. Allowing multiple deployed Application classes is going to have to wait though until Resteasy 3. I'd backmerge it to AS 7.x, but I don't see a 7.2 branch to fork/merge to. > RESTEasy: Can't deploy WebApp if more than one subclass of javax.ws.rs.Application is present > --------------------------------------------------------------------------------------------- > > Key: AS7-3199 > URL: https://issues.jboss.org/browse/AS7-3199 > Project: Application Server 7 > Issue Type: Bug > Components: REST > Affects Versions: 7.1.0.CR1b > Reporter: Pavel Janousek > Attachments: ExampleJAXRS.war > > > If I packed WAR WebApp with more that one subclass of javax.ws.rs.Application, deployment fails with "JBAS011232: Only one JAX-RS Application Class allowed." > This is not correct because it is against JAX-RS 1.1. specs where invalid situation (in section 2.3.2) is only when "It is a n error for > more than one application to be deployed +at the same effective servlet mapping+". > If you have any objections, please compare to reference JEE6 and JAX-RS implementation represented by the GlassFish Prelude 3.1.1 application server with already +fully JEE6 platform support+. -- 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, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira March 2013