August 2008 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBCLUSTER-209) Move pojoized version of HASingleton support classes out of AS cluster module

by Brian Stansberry (JIRA)

Move pojoized version of HASingleton support classes out of AS cluster module ----------------------------------------------------------------------------- Key: JBCLUSTER-209 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-209 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Components: HA-Server-API Reporter: Brian Stansberry Assignee: Paul Ferraro Fix For: 1.1.0.CR3 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBCACHE-941) org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces

by Elias Ross (JIRA)

org.jboss.cache.Caches, which allows for users to access a Cache using various collection interfaces ---------------------------------------------------------------------------------------------------- Key: JBCACHE-941 URL: http://jira.jboss.com/jira/browse/JBCACHE-941 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Elias Ross Assigned To: Manik Surtani The java.util.Collections utility class supplies useful methods for dealing with legacy interfaces and wrapping collection classes for concurrency, type safety, read-only, etc. In a simiilar vein, I wrote a "Caches" class that returns java.util.Map instances for a Node, which allow data to be modified through the standard Map interface. This I expect to be extremely useful for allowing uses to integrate their existing application with JBoss Cache, and will eliminate some of the confusion of using a new API and they can use the API they know best. Users also often demand an API which is "generic" so that their code is not tied to a particular vendor. There are basically two methods in Caches, one looks like this: Cache cache = DefaultCacheFactory.getInstance().createCache(); Map m = Caches.asMap(cache); m.put("foo", "bar"); The API and examples explain themselves. "Caches" could also include other useful methods for printing or reporting. Note that this functionality could be considered duplicated from PojoCache...) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

3
13
0 / 0

[JBoss JIRA] Created: (JBAS-5836) Upgrade jbossws to 3.0.3

by Dimitris Andreadis (JIRA)

Upgrade jbossws to 3.0.3 ------------------------ Key: JBAS-5836 URL: https://jira.jboss.org/jira/browse/JBAS-5836 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Web Services Reporter: Dimitris Andreadis Assignee: Thomas Diesler Fix For: JBossAS-5.0.0.CR2 Track the upgrade of jbossws -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1250) Add a Node.clearChildren() functionality

by Brian Stansberry (JIRA)

Add a Node.clearChildren() functionality ---------------------------------------- Key: JBCACHE-1250 URL: http://jira.jboss.com/jira/browse/JBCACHE-1250 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani For next major API change. Equivalent to Node.clearData(), but removes the children. Use case is trying to atomically remove everything under some structural node, while leaving the structural node in place. The best that can be done now is either: 1) Remove the node and re-add it, but this doesn't work for remote caches with INVALIDATION, since both the removal and the addition propagate as invalidation messages. Remote caches are left w/o the structural node. Plus it's not atomic. 2) Query for the children and remove them one by one. Also not atomic, plus if lockParentForChildInsertRemove is false you have to deal with other threads possibly adding new children while you are removing. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
9
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1449) Add PortComponent parsing to the EJBDescriptorHandler

by Alessio Soldano (JIRA)

Add PortComponent parsing to the EJBDescriptorHandler ----------------------------------------------------- Key: EJBTHREE-1449 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1449 Project: EJB 3.0 Issue Type: Task Affects Versions: AS 5.0.0.CR1 Reporter: Alessio Soldano Assignee: Alessio Soldano Fix For: AS 5.0.0.CR2 Add PortComponentSpec annotation to the container in Ejb3DescriptorHandler. See linked issue comments for more info. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBOSGI-23) Update the manifest structure deployer to use the StructureContext

by Adrian Brock (JIRA)

Update the manifest structure deployer to use the StructureContext ------------------------------------------------------------------ Key: JBOSGI-23 URL: https://jira.jboss.org/jira/browse/JBOSGI-23 Project: JBoss OSGi Issue Type: Task Security Level: Public (Everyone can see) Reporter: Adrian Brock The OSGi manifest structure deployer needs updating to use the StructureContext before osgi is updated with the deployers version that removes the old api JBDEPLOY-70 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBDEPLOY-66) Simplify the StructureDeployer api

by Adrian Brock (JIRA)

Simplify the StructureDeployer api ---------------------------------- Key: JBDEPLOY-66 URL: https://jira.jboss.org/jira/browse/JBDEPLOY-66 Project: JBoss Deployers Issue Type: Task Components: structure Reporter: Adrian Brock Fix For: JBDEPLOY-2.0.0.CR1 Currently the StructureDeployer api has a horrible method signature: boolean determineStructure(VirtualFile root, VirtualFile parent, VirtualFile file, StructureMetaData metaData, VFSStructuralDeployers deployers) throws DeploymentException; These are fairly ad hoc and difficult to change when we need to pass new context. We should introduce a new class "StructureContext" which encapsulates these parameters and any future parameters. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-5409) Redesign Remoting Aspect

by Andrew Lee Rubinger (JIRA)

Redesign Remoting Aspect ------------------------ Key: JBAS-5409 URL: http://jira.jboss.com/jira/browse/JBAS-5409 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Reporter: Andrew Lee Rubinger Assigned To: Dimitris Andreadis Remoting aspect has a dependency on Tx and Security Aspects -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

2
4
0 / 0

[JBoss JIRA] Updated: (JBAS-5824) Allow flushing of connection pool on fatal connection events

by Jesper Pedersen (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-5824?page=com.atlassian.jira.plug... ] Jesper Pedersen updated JBAS-5824: ---------------------------------- Fix Version/s: JBossAS-5.1.0.CR1 > Allow flushing of connection pool on fatal connection events > ------------------------------------------------------------ > > Key: JBAS-5824 > URL: https://jira.jboss.org/jira/browse/JBAS-5824 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JCA service > Reporter: Chris Bredesen > Assignee: Jesper Pedersen > Priority: Minor > Fix For: JBossAS-5.1.0.CR1 > > > As an alternative to validating connections (either on borrow or in the background), we could implement a feature similar to WebSphere's purge policy. The idea is that we can assume in certain cases that a single fatal exception means every connection in the pool will subsequently throw fatal exceptions. Such is the case in situations where the connected database has been restarted. Rather than implementing a purge policy per se, we would implement an "on fatal behavior". The behavior could define one of three actions to be taken when a fatal exception is encountered: > 1. Destroy single connection (equivalent to WAS policy of "single connection") > 2. Initiate validation run > 3. Flush entire pool (equivalent to WAS policy of "whole pool") > Note that all of the above (indeed this entire feature) requires the use of an ExceptionSorter. > In terms of implementation, I see two possibilities: > 1. Implement this feature as an MBean, which means we'd need some way of registering connection event listeners outside JCA. > 2. Implement this feature as part of the JCA adapter which I think makes more sense, but is more impactful. > Regarding #1, if it's possible to simply add a way to register connection event listeners from outside the adapter, that could become its own feature request and this feature simply turns into an MBean that can be implemented separately. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-789) DelegatingCacheLoader that can use a load balanced proxy

by Brian Stansberry (JIRA)

DelegatingCacheLoader that can use a load balanced proxy -------------------------------------------------------- Key: JBCACHE-789 URL: http://jira.jboss.com/jira/browse/JBCACHE-789 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Cache loaders Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.2.0 Using cache mode LOCAL and a DelegatingCacheLoader (aka a far-cache) has the potential to be a very performant cluster topology. But, the far cache is a single point of failure. Idea here is to develop an HA proxy to a cluster of far-caches; proxy pins to one far-cache, but can fail over to another if the primary target fails. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

17 years, 11 months

3
9
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira August 2008