March 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Updated: (JGRP-203) Primary Partiton approach for handling of partitions

by Bela Ban (JIRA)

[ http://jira.jboss.com/jira/browse/JGRP-203?page=all ] Bela Ban updated JGRP-203: -------------------------- Fix Version/s: 2.6 (was: 2.x) > Primary Partiton approach for handling of partitions > ---------------------------------------------------- > > Key: JGRP-203 > URL: http://jira.jboss.com/jira/browse/JGRP-203 > Project: JGroups > Issue Type: Feature Request > Reporter: Bela Ban > Assigned To: Bela Ban > Fix For: 2.6 > > Attachments: PRIMARY_PARTITION.java > > > Add this approach to JGroups. Members in a non-primary partition will shut down, become read-only etc. > Google for "primary partition AND group communication" for the relevant literature on this -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (JBCACHE-823) Refactor eviction configuration away from EvictionConfiguration interface

by Brian Stansberry (JIRA)

Refactor eviction configuration away from EvictionConfiguration interface ------------------------------------------------------------------------- Key: JBCACHE-823 URL: http://jira.jboss.com/jira/browse/JBCACHE-823 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Brian Stansberry Fix For: 2.0.0.GA The EvictionConfiguration interface presumes that objects that represent a policy configuration should be able to parse their XML config themselves. We don't want that; parsing of the legacy XML configs should be handled by XmlConfigurationParser and policy config objects should be configurable by the MC without their having any internal expectation of being passed a DOM element. To do this: 1) Create interface EvictionPolicyConfig. This is used internally (e.g. in the RegionManager and Region classes) in place of EvictionConfiguration. 2) All of the config classes for the standard eviction policies now implement EvictionPolicyConfig instead of EvictionConfiguration. To support old custom policies: 1) EvictionConfiguration still exists but is deprecated. 2) EvictionConfiguration now extends EvictionPolicyConfig. So, custom impls *will* need to be modified to implement EvictionPolicyConfig's 2 methods. 3) XmlConfigurationParser when trying to configure a policy config object will check if it implements EvictionConfiguration. If it does, the legacy parseXmlConfig(Element) method will be called. Otherwise it will be configured via reflection. Need to decided exactly how to handle the old public EvictionConfiguration Region.getEvictionConfiguration() method. -- 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 month

2
3
0 / 0

[JBoss JIRA] Created: (JBCACHE-822) Reconsider validation of EvictionPolicyConfig objects

by Brian Stansberry (JIRA)

Reconsider validation of EvictionPolicyConfig objects ----------------------------------------------------- Key: JBCACHE-822 URL: http://jira.jboss.com/jira/browse/JBCACHE-822 Project: JBoss Cache Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Brian Stansberry Assigned To: Manik Surtani In the legacy code, various impls of EvictionConfiguration would validate input during calls to parseXmlConfig. Problem is that if a config was instantiated and configured programatically, no validation occurred. Further the old parseXmlConfig validations basically just tested whether a configuration element was present, not whether it had a reasonable value. The new validate() methods really should just test for reasonable values; whether the value was configured externally or was there by default is irrelevant. Main task here is to remove some old unit tests that checked whether a value was set or not during xml parsing and replace with tests that check whether the reasonable value requirement is enforced. Probably will do this after alpha. -- 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 month

2
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-1006) Removal of parent node before removal of child node causes parent not to be found in optimistic tx workspace

by Manik Surtani (JIRA)

Removal of parent node before removal of child node causes parent not to be found in optimistic tx workspace ------------------------------------------------------------------------------------------------------------ Key: JBCACHE-1006 URL: http://jira.jboss.com/jira/browse/JBCACHE-1006 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.1.SP2 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 1.4.1.SP3 -- 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 month

1
2
0 / 0

[JBoss JIRA] Created: (JBREM-723) BisocketClientInvoker.transport() needs to distinguish between push and pull callback connections

by Ron Sigal (JIRA)

BisocketClientInvoker.transport() needs to distinguish between push and pull callback connections ------------------------------------------------------------------------------------------------- Key: JBREM-723 URL: http://jira.jboss.com/jira/browse/JBREM-723 Project: JBoss Remoting Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.2.0.Beta1 (Bluto) Reporter: Ron Sigal Assigned To: Ron Sigal Fix For: 2.2.0.Beta1 (Bluto) When BisocketClientInvoker.transport() detects an ADDLISTENER internal invocation, it asks the related callback BisocketServerInvoker to create a control connection. But for a pull callback connection, there is no callback BisocketServerInvoker. -- 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 month

1
2
0 / 0

[JBoss JIRA] Commented: (JBAS-3019) Add support for CRL validation to the certificate based login modules

by Anil Saldhana (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3019?page=comments#action_12355841 ] Anil Saldhana commented on JBAS-3019: ------------------------------------- At the tomcat layer, CRL file validation can happen with the JSSE socket factories. Attribute "crlFile" specified at the connector level in server.xml will do the trick. This is for information purposes only. > Add support for CRL validation to the certificate based login modules > --------------------------------------------------------------------- > > Key: JBAS-3019 > URL: http://jira.jboss.com/jira/browse/JBAS-3019 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Security > Reporter: Scott M Stark > Assigned To: Anil Saldhana > Fix For: JBossAS-4.2.1.CR1 > > > We need to add support for validating certificates against certificate revocation lists (CRLs). -- 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 month

1
0
0 / 0

[JBoss JIRA] Deleted: (JBAS-4196) Include a JSP Expression Language Interpreter (EL) implementation

by Dimitris Andreadis (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-4196?page=all ] Dimitris Andreadis deleted JBAS-4196: ------------------------------------- > Include a JSP Expression Language Interpreter (EL) implementation > ----------------------------------------------------------------- > > Key: JBAS-4196 > URL: http://jira.jboss.com/jira/browse/JBAS-4196 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Dimitris Andreadis > Assigned To: Dimitris Andreadis > > Include an EL implementation jar in deploy/jboss-web.deployer/jsf-libs, for Seam to use. -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (JBAS-4196) Include a JSP Expression Language Interpreter (EL) implementation

by Dimitris Andreadis (JIRA)

Include a JSP Expression Language Interpreter (EL) implementation ----------------------------------------------------------------- Key: JBAS-4196 URL: http://jira.jboss.com/jira/browse/JBAS-4196 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Web (Tomcat) service Reporter: Dimitris Andreadis Assigned To: Dimitris Andreadis Fix For: JBossAS-4.2.0.GA Include an EL implementation jar in deploy/jboss-web.deployer/jsf-libs, for Seam to use. -- 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 month

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1272) improve implementation of offset/limit in LDAP searches

by Boleslaw Dawidowicz (JIRA)

improve implementation of offset/limit in LDAP searches ------------------------------------------------------- Key: JBPORTAL-1272 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1272 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.6.Beta1 Reporter: Boleslaw Dawidowicz Assigned To: Boleslaw Dawidowicz Fix For: 2.6.CR1 instead of current dummy implementation which is unefficient use SearchControls and batch ldap operations -- 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 month

1
1
0 / 0

[JBoss JIRA] Created: (JGRP-416) MergeView processing fails for Multiplexer channel

by Jerry Gauthier (JIRA)

MergeView processing fails for Multiplexer channel -------------------------------------------------- Key: JGRP-416 URL: http://jira.jboss.com/jira/browse/JGRP-416 Project: JGroups Issue Type: Bug Affects Versions: 2.4.1 Reporter: Jerry Gauthier Assigned To: Bela Ban When I simulate a cluster failure and restart using a Multiplexer channel, the merge process fails in JGroups with an UnsupportedOperationException in Multiplexer.mergeServiceState(). The stack trace is as follows. ERROR [org.jgroups.mux.Multiplexer] problems handling merge view java.lang.UnsupportedOperationException at org.jgroups.util.UnmodifiableVector.retainAll(UnmodifiableVector.java:158) at org.jgroups.mux.Multiplexer.mergeServiceState(Multiplexer.java:867) at org.jgroups.mux.Multiplexer.handleMergeView(Multiplexer.java:812) at org.jgroups.mux.Multiplexer.access$200(Multiplexer.java:21) at org.jgroups.mux.Multiplexer$1.run(Multiplexer.java:287) I looked at the relevant JGroups code and it appears that JGroups uses a MergeView object that always returns an UnmodifiableVector when MergeView.getMembers() is invoked. The Multiplexer.mergeServiceState() method invokes MergeView.getMembers() followed by UnmodifiableVector(.retainAll(), causing the exception to occur. This problem can be replicated by executing DRMTestCase in JBossAS 5.0. The error occurs in DRMTestCase.isMasterReplica(). -- 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 month

3
6
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 2007