November 2007 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-4838) TECH REVIEW: Clustering - Chapter1 - Section3 - Clustered Entity EJBs

by samson kittoli (JIRA)

TECH REVIEW: Clustering - Chapter1 - Section3 - Clustered Entity EJBs ---------------------------------------------------------------------- Key: JBAS-4838 URL: http://jira.jboss.com/jira/browse/JBAS-4838 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: samson kittoli Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/ -- 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, 12 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4839) TECH REVIEW: Chapter1 - Section4 - Clustering HTTP Services

by samson kittoli (JIRA)

TECH REVIEW: Chapter1 - Section4 - Clustering HTTP Services ------------------------------------------------------------ Key: JBAS-4839 URL: http://jira.jboss.com/jira/browse/JBAS-4839 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli Assigned To: Norman Richards Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/ -- 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, 12 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-4836) TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services

by samson kittoli (JIRA)

TECH REVIEW: Clustering - Chapter1 - Section1 - Clustered-JNDI-Services ----------------------------------------------------------------------- Key: JBAS-4836 URL: http://jira.jboss.com/jira/browse/JBAS-4836 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: samson kittoli Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/ -- 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, 12 months

3
6
0 / 0

[JBoss JIRA] Created: (JBAS-4841) TECH REVIEW: Chapter2 - JBossCache and JGroups Services

by samson kittoli (JIRA)

TECH REVIEW: Chapter2 - JBossCache and JGroups Services ------------------------------------------------------- Key: JBAS-4841 URL: http://jira.jboss.com/jira/browse/JBAS-4841 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli Assigned To: Norman Richards Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/ -- 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, 12 months

5
11
0 / 0

[JBoss JIRA] Created: (JBAS-4834) TECH REVIEW: Clustering Guide - TRACKER

by samson kittoli (JIRA)

TECH REVIEW: Clustering Guide - TRACKER --------------------------------------- Key: JBAS-4834 URL: http://jira.jboss.com/jira/browse/JBAS-4834 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering Guide Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli Issue tracker for the Clustering Guide -- 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, 12 months

4
5
0 / 0

[JBoss JIRA] Created: (JBAS-4840) TECH REVIEW: Chapter1 - Section5 - Clustered JMS Services

by samson kittoli (JIRA)

TECH REVIEW: Chapter1 - Section5 - Clustered JMS Services ---------------------------------------------------------- Key: JBAS-4840 URL: http://jira.jboss.com/jira/browse/JBAS-4840 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: JBossAS-4.2.2.GA Reporter: samson kittoli Assigned To: Norman Richards Attached is an Open Office 2.0 Document containing a chapter of the Clustering Guide 1. Open document in Open Office 2. Edit -> Changes -> Record 3. Edit the document 4. Save changes and reattach to this Jira It is important for track changes to be enabled so the re-write can be easily performed. http://labs.jboss.com/jbossas/docs/Clustering_Guide/beta422/html/ -- 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, 12 months

4
8
0 / 0

[JBoss JIRA] Created: (JBAS-4648) Upgrade jboss transactions to 4.4 (from 4.3)

by Dimitris Andreadis (JIRA)

Upgrade jboss transactions to 4.4 (from 4.3) -------------------------------------------- Key: JBAS-4648 URL: http://jira.jboss.com/jira/browse/JBAS-4648 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Reporter: Dimitris Andreadis Fix For: JBossAS-5.0.0.CR1 -- 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, 12 months

1
3
0 / 0

[JBoss JIRA] Created: (JBPORTAL-1831) New user properties (locale) set by the user is not immediately used by the portal (improve existing solution)

by Thomas Heute (JIRA)

New user properties (locale) set by the user is not immediately used by the portal (improve existing solution) -------------------------------------------------------------------------------------------------------------- Key: JBPORTAL-1831 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1831 Project: JBoss Portal Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 2.6.2 Final Reporter: Thomas Heute Assigned To: Thomas Heute Fix For: 2.6.3 Final Because of some user properties caching, when a user modifies his profile, the new data is not immediately accessible, only after a re-login -- 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

1
2
0 / 0

[JBoss JIRA] Created: (JBCACHE-718) PojoCache TxLockInterceptor needs to release the lock node as well

by Ben Wang (JIRA)

PojoCache TxLockInterceptor needs to release the lock node as well ------------------------------------------------------------------ Key: JBCACHE-718 URL: http://jira.jboss.com/jira/browse/JBCACHE-718 Project: JBoss Cache Issue Type: Task Security Level: Public (Everyone can see) Components: PojoCache Reporter: Ben Wang Assigned To: Ben Wang Priority: Minor Fix For: 2.0.0 Currently, in TxLockInterceptor, I achieve the node lock by applying explicitly a cache.put(). It has two drawbacks: 1) It explicit going to insert a value to that node 2) Needs to do a remove when it is done. Not much can be done re: 1 now, but we should do 2, alhtough it will degrade the performance further. -- 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

3
5
0 / 0

[JBoss JIRA] Created: (JBCACHE-754) RPC return values to use a marshaller as well

by Manik Surtani (JIRA)

RPC return values to use a marshaller as well --------------------------------------------- Key: JBCACHE-754 URL: http://jira.jboss.com/jira/browse/JBCACHE-754 Project: JBoss Cache Issue Type: Feature Request Security Level: Public (Everyone can see) Affects Versions: 1.4.0, 2.0.0 Reporter: Manik Surtani Assigned To: Manik Surtani Fix For: 2.1.0 Currently, all RPC calls go through the VersionAwareMarshaller which is responsible for efficiently marshalling JBC internal objects as well as user objects using JBoss Serialization. Return values and exceptions, on the other hand, are marshalled/unmarshalled using JGroups' Util.{to|from}ByteBuffer() which uses standard object serialization. The problems here are twofold: 1) Relatively inefficient (in speed as well as byte array size) marshalling/unmarshalling for return values 2) Potential class loader problems Most RPC calls in JBoss Cache do not have return values so this is not a problem that comes up often, but certain features (clustered cache loader, data gravitation in buddy replication) rely on return values. The solution to this problem is to be able to register a marshaller with the JGroups RPCDispatcher for return values (and exceptions) as well as for the RPC calls themselves. -- 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

2
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira November 2007