October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Commented: (JBAS-2921) Use JBossSerialization for serializing sessions and attributes before putting them in the cache

by Hany Mesha (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-2921?page=comments#action_12344492 ] Hany Mesha commented on JBAS-2921: ---------------------------------- Brian, It's checked in and tested. The only thing is outstanding is adding documentation to the AS Guide that's why I left it open. > Use JBossSerialization for serializing sessions and attributes before putting them in the cache > ----------------------------------------------------------------------------------------------- > > Key: JBAS-2921 > URL: http://jira.jboss.com/jira/browse/JBAS-2921 > Project: JBoss Application Server > Issue Type: Task > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Clustering > Reporter: Brian Stansberry > Assigned To: Hany Mesha > Fix For: JBossAS-5.0.0.Beta > > > Use JBossSerialization in JBossCacheService externalizeSession(), loadSession(), getMarshalledValue() and getUnmarshalledValue(). -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Created: (JBPORTAL-986) Test session handling more completely in both Producer and Consumer

by Chris Laprun (JIRA)

Test session handling more completely in both Producer and Consumer ------------------------------------------------------------------- Key: JBPORTAL-986 URL: http://jira.jboss.com/jira/browse/JBPORTAL-986 Project: JBoss Portal Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Portal WSRP Affects Versions: 2.4 Final, 2.4.1 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.4.1 Final In particular, test behavior when: - a session has expired, - the Producer sent InvalidSessionFault, - etc -- 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, 7 months

1
1
0 / 0

[JBoss JIRA] Created: (JBPORTAL-982) Cookies handling in WSRP

by Chris Laprun (JIRA)

Cookies handling in WSRP ------------------------ Key: JBPORTAL-982 URL: http://jira.jboss.com/jira/browse/JBPORTAL-982 Project: JBoss Portal Issue Type: Task Security Level: Public (Everyone can see) Affects Versions: 2.4 Final Reporter: Chris Laprun Assigned To: Chris Laprun Fix For: 2.6 Final Cf. forums. -- 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, 7 months

1
2
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-68) enhance farm deployment to handle cluster partitioning and merging

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-68?page=all ] Brian Stansberry updated JBCLUSTER-68: -------------------------------------- Fix Version/s: Q1Y7 (was: Q3Y6) Move to Q1 '07 as we may get a chance to make farming improvements in 4.0.x next year. > enhance farm deployment to handle cluster partitioning and merging > ------------------------------------------------------------------ > > Key: JBCLUSTER-68 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-68 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Scott Marlow > Assigned To: Scott Marlow > Priority: Optional > Fix For: Q1Y7 > > > Handle partitions and merges. Here's a use case: > * Group is {A,B,C,D,E} > * Partition occurs > * Groups are now {A,B,C} and {D,E} > * User drops WAR into E > * D and E will have WAR > * Partition heals, merge occurs > o Group is now {A,B,C,D,E} > * A,B,C don't have the WAR, D and E have it > We could possibly use the same algorithm we use to reconcile this when D > and E were offline and a user dropped the WAR into E's ./farm dir. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-1) Clustering work book update

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-1?page=all ] Brian Stansberry updated JBCLUSTER-1: ------------------------------------- Fix Version/s: Q4Y6 (was: Q3Y6) > Clustering work book update > --------------------------- > > Key: JBCLUSTER-1 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-1 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Michael Yuan > Fix For: Q4Y6 > > Original Estimate: 2 weeks > Remaining Estimate: 2 weeks > > Update the Oreiley work book written by Sacha and Bill. Currently, http session replication uses the new JBossCache implementation. So configuration and architecture is changed. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-25) HA JMS

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-25?page=all ] Brian Stansberry updated JBCLUSTER-25: -------------------------------------- Fix Version/s: Q4Y6 (was: Q3Y6) > HA JMS > ------ > > Key: JBCLUSTER-25 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-25 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q4Y6 > > > Currently JBossMQ is using HA-Singleton for limited high availbility. There is no fail over for state, per se. > We don't have plan to enhance any HA in JBossMQ (4.0x release). > Ovidiu's new messaging system has a built-in high-availbility capability in there through the servless nature of the system. So when his new system is ready for JMS, this piece should be built in. > Remaining issues are to integrate with the current clustering framework. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-54) JGroups and JBoss Cache config best practice

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-54?page=all ] Brian Stansberry updated JBCLUSTER-54: -------------------------------------- Fix Version/s: Q1Y7 (was: Q3Y6) > JGroups and JBoss Cache config best practice > -------------------------------------------- > > Key: JBCLUSTER-54 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-54 > Project: JBoss Clustering > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Affects Versions: Q2Y5 > Reporter: Michael Yuan > Assigned To: Ben Wang > Fix For: Q1Y7 > > > We need a set of "Best Practices" on how to set various parameters on the JGroups and JBoss Cache MBean attributes. I think the "Best Practice" guide can take the format of a FAQ: > Q: Describe a common clustering error message or low performance scenario > A: Discuss possible reasons and MBean configuration parameters to adjust to solve this problem. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-17) http session replication benchmark and performance tuning

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-17?page=all ] Brian Stansberry updated JBCLUSTER-17: -------------------------------------- Fix Version/s: Q4Y6 (was: Q3Y6) > http session replication benchmark and performance tuning > --------------------------------------------------------- > > Key: JBCLUSTER-17 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-17 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q4Y6 > > > Need to benchmark http session replication using different configurations, e.g., sync mode, granularity, etc. > Also requires JBossCache to do the same first. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBCLUSTER-10) Unified client side failover/load-balancing on top of Remoting

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBCLUSTER-10?page=all ] Brian Stansberry updated JBCLUSTER-10: -------------------------------------- Fix Version/s: Q4Y6 (was: Q3Y6) > Unified client side failover/load-balancing on top of Remoting > -------------------------------------------------------------- > > Key: JBCLUSTER-10 > URL: http://jira.jboss.com/jira/browse/JBCLUSTER-10 > Project: JBoss Clustering > Issue Type: Task > Security Level: Public(Everyone can see) > Reporter: Ben Wang > Assigned To: Brian Stansberry > Fix For: Q4Y6 > > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Bill has a version that does this using the Remoting transport framework implemented in ejb3. Need further documentation and testing. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBMESSAGING-289) Make service container configurable wrt datasource and persistence manager config

by Ovidiu Feodorov (JIRA)

[ http://jira.jboss.com/jira/browse/JBMESSAGING-289?page=all ] Ovidiu Feodorov updated JBMESSAGING-289: ---------------------------------------- Priority: Critical (was: Major) > Make service container configurable wrt datasource and persistence manager config > --------------------------------------------------------------------------------- > > Key: JBMESSAGING-289 > URL: http://jira.jboss.com/jira/browse/JBMESSAGING-289 > Project: JBoss Messaging > Issue Type: Task > Reporter: Tim Fox > Assigned To: Ovidiu Feodorov > Priority: Critical > Fix For: 1.2.0.Alpha2 > > > Must be made configurable so test suite can be run against different databases with different pm configs -- 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, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2006