March 2010 - jboss-jira - Jboss List Archives

[JBoss JIRA] Closed: (JBCLUSTER-14) http session failover using single shared DB with cache loader

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBCLUSTER-14?page=com.atlassian.jira.p... ] Brian Stansberry closed JBCLUSTER-14. ------------------------------------- Fix Version/s: (was: Backlog) Resolution: Out of Date This was done for EAP 5.0 and AS 6.0.0.M1. > http session failover using single shared DB with cache loader > -------------------------------------------------------------- > > Key: JBCLUSTER-14 > URL: https://jira.jboss.org/jira/browse/JBCLUSTER-14 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web Tier > Reporter: Ben Wang > Assignee: Brian Stansberry > Priority: Minor > Original Estimate: 8 weeks > Remaining Estimate: 8 weeks > > To achieve http session failover, alternatively we can use a single shared DB with CacheLoader for multiple cache instances. All the session states will be persisted to the shared DB. When failing over, it will simply retrieve from the DB if it is not there yet. > This approach can scale very well. But it will be slower since every session setAttribute operation involves trip to DB. JBossCache already supports this semantics now. All we need is someone to verify it and benchmark it. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBCLUSTER-115) Major Clustering Features in JBoss 5.0

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBCLUSTER-115?page=com.atlassian.jira.... ] Brian Stansberry closed JBCLUSTER-115. -------------------------------------- Fix Version/s: (was: Q2Y8) Resolution: Out of Date > Major Clustering Features in JBoss 5.0 > -------------------------------------- > > Key: JBCLUSTER-115 > URL: https://jira.jboss.org/jira/browse/JBCLUSTER-115 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Blocker > > Overall tracking issue for *major* clustering features/fixes to be included in JBoss AS 5.0.0. > There will of course be numerous minor issues; please track those with a filter on the issues in the JBAS project. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (EJBTHREE-2053) Infinispan replication configuration via @CacheConfig

by Brian Stansberry (JIRA)

Infinispan replication configuration via @CacheConfig ----------------------------------------------------- Key: EJBTHREE-2053 URL: https://jira.jboss.org/jira/browse/EJBTHREE-2053 Project: EJB 3.0 Issue Type: Feature Request Components: cache, Clustering Reporter: Brian Stansberry Make the typical distributed cache configurations configurable via @CacheConfig or jboss.xml; don't force users to go to a separate Infinispan configuration file. The typical configurations are: 1) synchronous or async (perhaps a better term? async == fire and forget) 2) total replication or not? 3) if "not", number of backup copies. Potentially 2 and 3 could be combined into a numbackups param: -1 == total replication (i.e. unlimited) 0 == cache is in local mode > 0 = DIST w/ numbackups + 1 copies. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-43) Release JACC 1.4 API version 1.0.0.Beta1

by Stefan Guilhen (JIRA)

Release JACC 1.4 API version 1.0.0.Beta1 ---------------------------------------- Key: JBEE-43 URL: https://jira.jboss.org/jira/browse/JBEE-43 Project: JBoss JavaEE APIs Issue Type: Task Components: JACC API Reporter: Stefan Guilhen Assignee: Stefan Guilhen The JACC 1.4 API classes have been added to the specs repository. We need to release a Beta1 version of this API in order to update the javaee 6 aggregated module. -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Closed: (JBAS-4792) Implement HA Pooled Invoker

by Brian Stansberry (JIRA)

[ https://jira.jboss.org/jira/browse/JBAS-4792?page=com.atlassian.jira.plug... ] Brian Stansberry closed JBAS-4792. ---------------------------------- Resolution: Out of Date The pooled invoker is gone. > Implement HA Pooled Invoker > --------------------------- > > Key: JBAS-4792 > URL: https://jira.jboss.org/jira/browse/JBAS-4792 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Docs/Security Guide > Affects Versions: Backlog > Reporter: Andrew Oliver > > Presently there is a pooled invoker and an HA jrmp invoker. We should have a pooled JRMPHA invoker. -- 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

16 years, 4 months

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-7798) Naming deployers should get module name from NamedModule attached to DeploymentUnit

by Brian Stansberry (JIRA)

Naming deployers should get module name from NamedModule attached to DeploymentUnit ----------------------------------------------------------------------------------- Key: JBAS-7798 URL: https://jira.jboss.org/jira/browse/JBAS-7798 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Deployers Reporter: Brian Stansberry Assignee: Carlo de Wolf Fix For: JBossAS-6.0.0.M3 See discussion thread linked from parent issue. The ModuleNameDeployer created for the JBAS-7644 work attaches the metadata object that implements the NamedModule interface to the DU under key NamedModule.class. The naming deployers should get this attachment to find the module name, rather than using NamingJavaEEModuleInformer.getModulePath(). Note that my JBAS-7644 work actually hacked NamingJavaEEModuleInformer.getModulePath() to have it get the NamedModule attachment rather than returning a path. That was to allow the deployer to get integrated and tested in hudson pending completion of this subtask. -- 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

16 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (JBMETA-271) PersistenceContext annotation processor creates incorrect targetname in ResourceInjectionTargetMetaData

by jaikiran pai (JIRA)

PersistenceContext annotation processor creates incorrect targetname in ResourceInjectionTargetMetaData ------------------------------------------------------------------------------------------------------- Key: JBMETA-271 URL: https://jira.jboss.org/jira/browse/JBMETA-271 Project: JBoss Metadata Issue Type: Bug Security Level: Public (Everyone can see) Components: common Affects Versions: jboss-metadata-common-2.0.0-alpha-14 Reporter: jaikiran pai Assignee: jaikiran pai Fix For: jboss-metadata-common-2.0.0-alpha-15 For the following bean: public class MyBean { @PersistenceContext (name = "emENCName") private EntityManager emFieldName; ... } The (Abstract)PersistenceContextProcessor creates a ResourceInjectionTargetMetaData with (correct) targetClass MyBean and (incorrect) targetName "emENCName". The targetName should actually be "emFieldName". -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (SECURITY-480) SecurityAssociation->getContextInfo and setContextInfo methods to take in Object key for backwards compatibility

by Anil Saldhana (JIRA)

SecurityAssociation->getContextInfo and setContextInfo methods to take in Object key for backwards compatibility ---------------------------------------------------------------------------------------------------------------- Key: SECURITY-480 URL: https://jira.jboss.org/jira/browse/SECURITY-480 Project: PicketBox (JBoss Security and Identity Management) Issue Type: Bug Security Level: Public (Everyone can see) Components: JBossSX Affects Versions: PicketBox_v3_0_beta3 Reporter: Anil Saldhana Assignee: Anil Saldhana Fix For: PicketBox_v3_0_beta4 Classes to change: SecurityAssociation.java and LegacySecurityAssociationUnitTestCase -- 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

16 years, 4 months

1
1
0 / 0

[JBoss JIRA] Created: (JBEE-41) Release jboss-ejb-api_3.1_spec 1.0.0.Beta2

by Shelly McGowan (JIRA)

Release jboss-ejb-api_3.1_spec 1.0.0.Beta2 ------------------------------------------- Key: JBEE-41 URL: https://jira.jboss.org/jira/browse/JBEE-41 Project: JBoss JavaEE APIs Issue Type: Release Reporter: Shelly McGowan Assignee: Shelly McGowan -- 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

16 years, 4 months

2
5
0 / 0

[JBoss JIRA] Created: (JBEE-38) Resolve issues with javax.annotation APIs

by Shelly McGowan (JIRA)

Resolve issues with javax.annotation APIs ----------------------------------------- Key: JBEE-38 URL: https://jira.jboss.org/jira/browse/JBEE-38 Project: JBoss JavaEE APIs Issue Type: Bug Reporter: Shelly McGowan Assignee: Shelly McGowan Fix For: 1.0.0.CR1 The signature tests are detecting failues in the 1.0.0.Beta1 release of jboss-annotations-api_1.1_spec.jar. See linked issue for more information. -- 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

16 years, 4 months

1
2
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 March 2010