July 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JBCACHE-533) Remove synchronization in Passivation/Activation interceptor

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-533?page=all ] Manik Surtani updated JBCACHE-533: ---------------------------------- Summary: Remove synchronization in Passivation/Activation interceptor (was: Change synchronization to use locks in Passivation/Activation interceptor) Description: This is now handled in the cache loader implementation (was: Re synchronization in PassivationInterceptor and ActivationInterceptor The synchronization statement is needed to prevent multiple threads from trying to passivate or activate the node at the same time. However, we can switch to use BaseCacheLoaderInterceptor.obtainLoaderLock() to obtain locks. The same strategy used in CacheStoreInterceptor and CacheLoaderInterceptor. Please open a JIRA Issue for it and it'll be done. ) Assignee: Manik Surtani (was: Hany Mesha) Complexity: Low > Remove synchronization in Passivation/Activation interceptor > ------------------------------------------------------------ > > Key: JBCACHE-533 > URL: http://jira.jboss.com/jira/browse/JBCACHE-533 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Manik Surtani > Fix For: 2.0.0.GA > > > This is now handled in the cache loader implementation -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-533) Change synchronization to use locks in Passivation/Activation interceptor

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-533?page=comments#action_12368879 ] Manik Surtani commented on JBCACHE-533: --------------------------------------- Synchronization removed. This is now handled in the cache loader implementations. > Change synchronization to use locks in Passivation/Activation interceptor > ------------------------------------------------------------------------- > > Key: JBCACHE-533 > URL: http://jira.jboss.com/jira/browse/JBCACHE-533 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 1.3.0.GA > Reporter: Elias Ross > Assigned To: Hany Mesha > Fix For: 2.0.0.GA > > > Re synchronization in PassivationInterceptor and ActivationInterceptor > The synchronization statement is needed to prevent multiple threads from trying to passivate or activate the node at the same time. However, we can switch to use BaseCacheLoaderInterceptor.obtainLoaderLock() to obtain locks. The same strategy used in CacheStoreInterceptor and CacheLoaderInterceptor. Please open a JIRA Issue for it and it'll be done. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Updated: (JBCACHE-371) Create Spring clustering pagakage using JBossCache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-371?page=all ] Manik Surtani updated JBCACHE-371: ---------------------------------- Fix Version/s: 2.1.0.GA (was: 2.0.0.GA) > Create Spring clustering pagakage using JBossCache > -------------------------------------------------- > > Key: JBCACHE-371 > URL: http://jira.jboss.com/jira/browse/JBCACHE-371 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.1.0.GA > > > I don't have detailed of Spring framework, but when JBossCache 1.3 is released (with support of JDK5.0 annotation for POJO Cache), it should be able to support annotation based POJO clustering (or more accurately, state replicatiom) that can run inside Spring. If there is a contributor that is willing to take this task, please let me know. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Commented: (JBCACHE-371) Create Spring clustering pagakage using JBossCache

by Manik Surtani (JIRA)

[ http://jira.jboss.com/jira/browse/JBCACHE-371?page=comments#action_12368878 ] Manik Surtani commented on JBCACHE-371: --------------------------------------- See JBCLUSTER-154 > Create Spring clustering pagakage using JBossCache > -------------------------------------------------- > > Key: JBCACHE-371 > URL: http://jira.jboss.com/jira/browse/JBCACHE-371 > Project: JBoss Cache > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Manik Surtani > Priority: Minor > Fix For: 2.0.0.GA > > > I don't have detailed of Spring framework, but when JBossCache 1.3 is released (with support of JDK5.0 annotation for POJO Cache), it should be able to support annotation based POJO clustering (or more accurately, state replicatiom) that can run inside Spring. If there is a contributor that is willing to take this task, please let me know. -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1137) setPurgeOnStartup(true) doesn't purge with bdbje cacheloader

by Steven Marcus (JIRA)

setPurgeOnStartup(true) doesn't purge with bdbje cacheloader ------------------------------------------------------------ Key: JBCACHE-1137 URL: http://jira.jboss.com/jira/browse/JBCACHE-1137 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Cache loaders Affects Versions: 2.0.0.CR3 Reporter: Steven Marcus Assigned To: Manik Surtani in contrast, the jdbm cache loader does purge on startup when requested -- 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

19 years

2
4
0 / 0

[JBoss JIRA] Updated: (JBAOP-193) Improve RunSecurityInterceptor

by Kabir Khan (JIRA)

[ http://jira.jboss.com/jira/browse/JBAOP-193?page=all ] Kabir Khan updated JBAOP-193: ----------------------------- Fix Version/s: (was: 2.0.0.beta) This is really tied to app server version and not to aop release > Improve RunSecurityInterceptor > ------------------------------ > > Key: JBAOP-193 > URL: http://jira.jboss.com/jira/browse/JBAOP-193 > Project: JBoss AOP > Issue Type: Bug > Affects Versions: 1.3.4 > Reporter: Kabir Khan > Assigned To: Kabir Khan > > In addition to what is mentioned on the forum, we also need to check the class for the @RunAs annotation -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-1120) Do not load data from loader for calls to Cache.get(Fqn fqn)

by Elias Ross (JIRA)

Do not load data from loader for calls to Cache.get(Fqn fqn) ------------------------------------------------------------ Key: JBCACHE-1120 URL: http://jira.jboss.com/jira/browse/JBCACHE-1120 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.0.0.CR2 Reporter: Elias Ross Assigned To: Manik Surtani Refer to the forum... The following code causes the old data to be loaded from the cache loader, though it's really not necessary: Cache c; Map m; c.get("/a/b").replaceAll(m); // or c.get("/a/b").clearData(); Changing CacheLoaderInterceptor to not load on "getNodeMethodLocal_id" might work, but not sure if that would be the correct fix. -- 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

19 years

3
6
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1012) Make IOR security configurable

by Dimitris Andreadis (JIRA)

Make IOR security configurable ------------------------------ Key: EJBTHREE-1012 URL: http://jira.jboss.com/jira/browse/EJBTHREE-1012 Project: EJB 3.0 Issue Type: Feature Request Components: Security Affects Versions: AS 4.2.1.GA, AS 4.2.0 GA, EJB 3.0 RC9 - Patch 1 Reporter: Dimitris Andreadis See the linked issues starting from EJBTHREE-667. org.jboss.ejb3.iiop.IORFactory.java: ... IorSecurityConfigMetaData iorSecurityConfigMetaData = new IorSecurityConfigMetaData(); // TODO: make ior security configurable The IorSecurityConfigMetaData is practically immutable and configured currently only from XML. This needs to be changed so that it can be configured programmatically, as well (e.g. driven by annotations?). -- 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

19 years

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4541) Authentication Service (AS) Context stored in CSIv2 encoded IORs shouldn't indicate EstablishTrustInClient supported when AUTH_METHOD_NONE

by Dimitris Andreadis (JIRA)

Authentication Service (AS) Context stored in CSIv2 encoded IORs shouldn't indicate EstablishTrustInClient supported when AUTH_METHOD_NONE ------------------------------------------------------------------------------------------------------------------------------------------ Key: JBAS-4541 URL: http://jira.jboss.com/jira/browse/JBAS-4541 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: IIOP service Affects Versions: JBossAS-4.2.1.GA, JBossAS-4.2.0.GA Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.2.GA In a recent ejb3 refactoring the AS context stored in CSIv2 encoded IOR indicated that EstablishTrustInClient is always supported. The CTS testsuite expects the AS context to indicate that EstablishTrustInClient is not supported when the context in the IOR is configured through xml indicating AUTH_METHOD_NONE. -- 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

19 years

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1547) Speak like yoda, you do

by Andrew Oliver (JIRA)

Speak like yoda, you do ----------------------- Key: JBPORTAL-1547 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1547 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Components: Portal Reference Guide Affects Versions: 2.6 Final Reporter: Andrew Oliver Assigned To: Julien Viet 4.1.1 g/"If you stay with old theme files you may find JBP 2.6 unusable by not even be able to log in."/s//"If you stay with old theme files you may find JBP 2.6 unusable to the point that you may not even be able to log in."/g -- 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

19 years

3
4
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 July 2007