April 2009 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBAS-6038) Examine use of SessionReplicationContext start/finishCacheActivity

by Brian Stansberry (JIRA)

Examine use of SessionReplicationContext start/finishCacheActivity ------------------------------------------------------------------ Key: JBAS-6038 URL: https://jira.jboss.org/jira/browse/JBAS-6038 Project: JBoss Application Server Issue Type: Task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.0.1.CR1 I don't believe the calls to SessionReplicationContext.startCacheActivity and finishCacheActivity are necessary any longer; confirm this and remove if so. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
3
0 / 0

[JBoss JIRA] Created: (JBAS-6733) Avoid re-reading expired sessions from distributed cache

by Brian Stansberry (JIRA)

Avoid re-reading expired sessions from distributed cache -------------------------------------------------------- Key: JBAS-6733 URL: https://jira.jboss.org/jira/browse/JBAS-6733 Project: JBoss Application Server Issue Type: Sub-task Security Level: Public (Everyone can see) Components: Clustering, Web (Tomcat) service Reporter: Brian Stansberry Assignee: Brian Stansberry Priority: Minor Fix For: JBossAS-5.1.0.CR1 Add logic such that if we don't find a session locally, only check the distributed cache if we haven't previously handled this session id on this request. If we handled it previously but it's no longer local, that means it's been invalidated. If we request an invalidated session from the distributed cache, it will be missing from the local cache but may still exist on other nodes (i.e. if the invalidation hasn't replicated yet because we are running in a tx or with async repl). With buddy replication, asking the local cache for the session will cause the out-of-date session from the other nodes to be gravitated, thus resuscitating the session. Previously releases had logic to deal with this, but only covered requests for the session that come before the code returns from ClusteredSessionValve. Such calls can happen after that, in particular StandardHostValve makes such a call. Fix is to store info on invalidated sessions in a thread local, as was done previously, but to defer clearing the thread local until the Session.recycle method rather than doing it in the ClusteredSessionValve. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1797) remove bandwidth monitoring in SF config for EJB3

by Radoslav Husar (JIRA)

remove bandwidth monitoring in SF config for EJB3 ------------------------------------------------- Key: EJBTHREE-1797 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1797 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (EJBTHREE-1564) add other configurations to hudson+create hudson tasks

by Radoslav Husar (JIRA)

add other configurations to hudson+create hudson tasks ------------------------------------------------------ Key: EJBTHREE-1564 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1564 Project: EJB 3.0 Issue Type: Sub-task Reporter: Radoslav Husar Assignee: Radoslav Husar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBTEST-8) add a stop task option to silently ignore shutdown errors

by Aleksandar Kostadinov (JIRA)

add a stop task option to silently ignore shutdown errors --------------------------------------------------------- Key: JBTEST-8 URL: https://jira.jboss.org/jira/browse/JBTEST-8 Project: JBoss Test Issue Type: Feature Request Affects Versions: 1.1.2.GA Reporter: Aleksandar Kostadinov Assignee: Shelly McGowan Fix For: 1.1.3.GA It could be useful to have a stop task option to silently ignore shutdown errors. For example when we know we screwed up a server config with some test and want server manager to kill its process and not complain anyhow. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 1 month

1
4
0 / 0

[JBoss JIRA] Created: (JBMESSAGING-1230) Client failover support if one node of a cluster is cleanly shut down.

by Phillip Thurmond (JIRA)

Client failover support if one node of a cluster is cleanly shut down. ---------------------------------------------------------------------- Key: JBMESSAGING-1230 URL: http://jira.jboss.com/jira/browse/JBMESSAGING-1230 Project: JBoss Messaging Issue Type: Feature Request Reporter: Phillip Thurmond Assigned To: Tim Fox Fix For: 1.4.0.SP3.CP01 If one node of a cluster fails in someway, the client will attempt to failover transparently. However, if one node is shutdown cleanly, the client will not automatically failover to another node in the cluster. This functionality would be very useful for "rolling upgrades" where a portion of the cluster is left up while the other nodes are being updated. -- 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

15 years, 2 months

3
11
0 / 0

[JBoss JIRA] Created: (JBAS-6734) Hot changes not updated in VFS server/tmp directory

by Jeff Wexler (JIRA)

Hot changes not updated in VFS server/tmp directory --------------------------------------------------- Key: JBAS-6734 URL: https://jira.jboss.org/jira/browse/JBAS-6734 Project: JBoss Application Server Issue Type: Bug Security Level: Public (Everyone can see) Components: VFS Affects Versions: JBossAS-5.0.1.GA Environment: JBossAS 5.0.1.GA, Windows Server 2003, localhost:8080, seam 2.1.2.GA, Eclipse 3.4.2 with JbossTools 3.0.0.GA, PostgreSQL 8.3 Reporter: Jeff Wexler Assignee: Ales Justin Priority: Critical Create a new seam project as an ear (or war) with Dynamic Seam 2.1. deployed to the default server of JBossAS. Verify Welcome to Seam! message. Change home.xhtml such that message is now Welcome to Seam_Modified1! and save. Wait a number of seconds. Verify that change updated in home.xhtml in the default server of JBossAS. Refresh project/home.seam and you still get Welcome to Seam! rather than Welcome to Seam_Modified1! Check again after an hour and still the old message. Does not seem to update the tmp directory with the changed version unless you touch application.xml or redeploy the whole project. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
2
0 / 0

[JBoss JIRA] Created: (JBCLUSTER-213) check and warn if system time on joining node if off

by Radoslav Husar (JIRA)

check and warn if system time on joining node if off ---------------------------------------------------- Key: JBCLUSTER-213 URL: https://jira.jboss.org/jira/browse/JBCLUSTER-213 Project: JBoss Clustering Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Radoslav Husar Assignee: Brian Stansberry Priority: Minor When new node joins the cluster, It can simply exchange time with other nodes. If the time is off by significant number of seconds, it would warn the administrator to synchronize the time on cluster machines. Since some services depend on having time synchronized, this could help users to find this problem quickly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
8
0 / 0

[JBoss JIRA] Created: (JBAS-6729) Update to JBoss LogBridge 1.0.0CR4

by David Lloyd (JIRA)

Update to JBoss LogBridge 1.0.0CR4 ---------------------------------- Key: JBAS-6729 URL: https://jira.jboss.org/jira/browse/JBAS-6729 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Logging Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-5.1.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBAS-6730) Update to JBoss LogManager 1.0.0.CR3

by David Lloyd (JIRA)

Update to JBoss LogManager 1.0.0.CR3 ------------------------------------ Key: JBAS-6730 URL: https://jira.jboss.org/jira/browse/JBAS-6730 Project: JBoss Application Server Issue Type: Component Upgrade Security Level: Public (Everyone can see) Components: Logging Reporter: David Lloyd Assignee: David Lloyd Fix For: JBossAS-5.1.0.CR1 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2009