December 2007 - jboss-jira - Jboss List Archives

[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

16 years, 1 month

3
9
0 / 0

[JBoss JIRA] Created: (JBCACHE-1015) Notify user (via callback) if application of (async or sync) replication fails

by Bela Ban (JIRA)

Notify user (via callback) if application of (async or sync) replication fails ------------------------------------------------------------------------------ Key: JBCACHE-1015 URL: http://jira.jboss.com/jira/browse/JBCACHE-1015 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Bela Ban Assigned To: Manik Surtani If a replication cannot be applied (no transactions), then invoke a callback notifying the application, so that some corrective action can be taken -- 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

16 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-877) TreeCache usage should not depend on trove.jar

by Galder Zamarreno (JIRA)

TreeCache usage should not depend on trove.jar ---------------------------------------------- Key: JBCACHE-877 URL: http://jira.jboss.com/jira/browse/JBCACHE-877 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 1.4.0.SP1 Reporter: Galder Zamarreno Assigned To: Manik Surtani Priority: Minor A customer is upgrading from JBC 1.1 to 1.4.0.SP1 and even though it only uses plain TreeCache, it gets a NoClassDefFoundError for trove classes. 2006-11-23 13:19:03,781 ERROR RpcDispatcher exception=java.lang.NoClassDefFoundError: gnu/trove/TObjectHashingStrategy This is a TreeCacheAop/PojoCache dependency and therefore, should be isolated and attempted to be loaded only when PojoCache used. -- 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

16 years, 1 month

7
28
0 / 0

[JBoss JIRA] Created: (JBCACHE-797) Cache to provide a Node implementation that can hide the internal metadata

by Ben Wang (JIRA)

Cache to provide a Node implementation that can hide the internal metadata -------------------------------------------------------------------------- Key: JBCACHE-797 URL: http://jira.jboss.com/jira/browse/JBCACHE-797 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Reporter: Ben Wang Assigned To: Manik Surtani Fix For: 2.1.0 This came up from a Forum thread. Can we offer a second node implementation such that we can deposit the metadata into that node that is hiding away from the user? -- 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

16 years, 1 month

4
4
0 / 0

[JBoss JIRA] Created: (JBCACHE-772) State transfer not handled properly in case of reconnect

by Brian Stansberry (JIRA)

State transfer not handled properly in case of reconnect -------------------------------------------------------- Key: JBCACHE-772 URL: http://jira.jboss.com/jira/browse/JBCACHE-772 Project: JBoss Cache Issue Type: Bug Security Level: Public (Everyone can see) Components: Clustering Affects Versions: 1.4.0.SP1, 1.4.0, 1.3.0.SP3, 1.3.0.SP2, 1.3.0.SP1, 1.3.0, 1.2.4SP2, 1.2.4SP1, 1.2.4 Reporter: Brian Stansberry Assigned To: Manik Surtani Fix For: 2.1.0 In createService(), TreeCache set Channel.AUTO_GET_STATE to true. This should only be done if the cache is configured to do an initial state transfer. That's easy to fix. What's harder to fix is what to do when region-based marshalling is in effect. Probably, something like the following: 1) In viewAccepted, monitor for the case where a view is issue that doesn't include the current node. Set a flag and ??? (throw exceptions when attempts are made to use the cache???) 2) When another view is accepted that once again includes the current node, iterate through the various marshalling regions, inactivating and then reactivating them (reactivation will cause a partial state transfer). -- 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

16 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBCACHE-1214) Can the cache be backed by LinkedHashSet instead of HashSet

by Carl Shelbourne (JIRA)

Can the cache be backed by LinkedHashSet instead of HashSet ----------------------------------------------------------- Key: JBCACHE-1214 URL: http://jira.jboss.com/jira/browse/JBCACHE-1214 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Environment: RFC Reporter: Carl Shelbourne Assigned To: Manik Surtani Priority: Optional Looking at the code it is noted that the cache is backed by a HashSet. Would it be possible to change this so that it is backed by a LinkedHashSet. There may or may not be performance benefits to this dependant on the usage. The primary reason for wanting it to be backed by a LinkedHashSet is the guaranteed ordering of the elements when iterated over. Having this guarantee would facilitate implementations of say a TableModel, but would make other iterations more predictable too. -- 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

16 years, 1 month

2
2
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1753) Align WSRP with WS 2.0

by Thomas Heute (JIRA)

Align WSRP with WS 2.0 ---------------------- Key: JBPORTAL-1753 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1753 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.6.2 Final Reporter: Thomas Heute Assigned To: Chris Laprun Fix For: 2.6.3 Final At least portal-wsrp.jse must be renamed portal-wsrp.war. There are also some WARN when you start WSRP on JBoss AS 4.2.2.GA 15:49:57,971 WARN [ServiceObjectFactory] Unable to narrow port selection for UnifiedPortComponentRef serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_ServiceDescription_PortType portQName=null enableMTOM=false portComponentLink=null callProperties=[] stubProperties=[] configName=null configFile=null 15:49:58,920 WARN [ServiceObjectFactory] Unable to narrow port selection for UnifiedPortComponentRef serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Markup_PortType portQName=null enableMTOM=false portComponentLink=null callProperties=[] stubProperties=[] configName=null configFile=null 15:49:59,827 WARN [ServiceObjectFactory] Unable to narrow port selection for UnifiedPortComponentRef serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_PortletManagement_PortType portQName=null enableMTOM=false portComponentLink=null callProperties=[] stubProperties=[] configName=null configFile=null 15:50:01,753 WARN [ServiceObjectFactory] Unable to narrow port selection for UnifiedPortComponentRef serviceEndpointInterface=org.jboss.portal.wsrp.core.WSRP_v1_Registration_PortType portQName=null enableMTOM=false portComponentLink=null callProperties=[] stubProperties=[] configName=null configFile=null -- 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

16 years, 1 month

2
5
0 / 0

[JBoss JIRA] Created: (JBAS-4592) NPE in ExtendedFormAuthenticator

by Anil Saldhana (JIRA)

NPE in ExtendedFormAuthenticator -------------------------------- Key: JBAS-4592 URL: http://jira.jboss.com/jira/browse/JBAS-4592 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: Security, Web (Tomcat) service Affects Versions: JBossAS-4.0.5.GA Reporter: Anil Saldhana Assigned To: Scott M Stark Fix For: JBossAS-4.2.2.GA Forum has details. -- 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

16 years, 1 month

2
3
0 / 0

[JBoss JIRA] Created: (EJBTHREE-696) Not active transaction in a slsb

by Denis Peyrusaubes (JIRA)

Not active transaction in a slsb -------------------------------- Key: EJBTHREE-696 URL: http://jira.jboss.com/jira/browse/EJBTHREE-696 Project: EJB 3.0 Issue Type: Bug Affects Versions: EJB 3.0 RC8 - FD Environment: jboss-4.0.4.GA Reporter: Denis Peyrusaubes Priority: Minor Calling the setRollBackOnly method in a method of SLSB marked with Required attribute throws a "org.jboss.util.NestedSQLException: Transaction is not active". -- 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

16 years, 1 month

2
1
0 / 0

[JBoss JIRA] Created: (SECURITY-33) White Paper on Kerberos

by Anil Saldhana (JIRA)

White Paper on Kerberos ------------------------ Key: SECURITY-33 URL: http://jira.jboss.com/jira/browse/SECURITY-33 Project: JBoss Security and Identity Management Issue Type: Task Security Level: Public (Everyone can see) Reporter: Anil Saldhana Assigned To: Anil Saldhana We have some kerberos/spnego interface available in JBoss as part of the initial work done by Chris DeLashmutt. http://wiki.jboss.org/wiki/Wiki.jsp?page=NegotiateKerberos Need to bring this contribution to some formality and get a white paper out. -- 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

16 years, 1 month

2
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira December 2007