October 2006 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBTM-142) Change JBoss logo

by Mark Little (JIRA)

Change JBoss logo ----------------- Key: JBTM-142 URL: http://jira.jboss.com/jira/browse/JBTM-142 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.2.2 The documentation uses the old JBoss logo. Needs to be updated to use the new Redhat/JBoss logo. -- 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, 11 months

1
1
0 / 0

[JBoss JIRA] Created: (JBTM-141) The fix for JBTM-139 requires updates to the documentation.

by Kevin Conner (JIRA)

The fix for JBTM-139 requires updates to the documentation. ----------------------------------------------------------- Key: JBTM-141 URL: http://jira.jboss.com/jira/browse/JBTM-141 Project: JBoss Transaction Manager Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.2.1 Reporter: Kevin Conner Assigned To: Mark Little Fix For: 4.2.2 Documentation update for JBTM-139 -- 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, 11 months

2
1
0 / 0

[JBoss JIRA] Created: (JBTM-143) IllegalStateException/INVALID_TRANSACTION termination status

by Mark Little (JIRA)

IllegalStateException/INVALID_TRANSACTION termination status ------------------------------------------------------------ Key: JBTM-143 URL: http://jira.jboss.com/jira/browse/JBTM-143 Project: JBoss Transaction Manager Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Documentation, JTA Implementation, JTS Implementation Affects Versions: 4.2.1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.6 Multi-threaded environments may allow non-creating thread to terminate transaction. In JTA we throw IllegalStateException, in OTS we throw INVALID_TRANSACTION. OTS assumed termination status of transaction would be obtained via previously held reference to Control. However, we could also indicate via the exception detail. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBSEAM-375) <method name="...." event="..."/> in components.xml

by Gavin King (JIRA)

<method name="...." event="..."/> in components.xml --------------------------------------------------- Key: JBSEAM-375 URL: http://jira.jboss.com/jira/browse/JBSEAM-375 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Gavin King Assigned To: Gavin King I think it would be really cool to be able to do the @RaiseEvent thing in components.xml -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBAS-3096) Add a maxInactiveInterval concept to ClusteredSingleSignOn

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3096?page=all ] Brian Stansberry closed JBAS-3096. ---------------------------------- Fix Version/s: JBossAS-4.0.5.GA (was: JBossAS-5.0.0.Beta) (was: JBossAS-4.0.6.CR1) Resolution: Done Fixed in Branch_4_0. Ended up using the Tomcat background thread, as it's the simplest solution for now. > Add a maxInactiveInterval concept to ClusteredSingleSignOn > ---------------------------------------------------------- > > Key: JBAS-3096 > URL: http://jira.jboss.com/jira/browse/JBAS-3096 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Security, Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-4.0.5.GA > > Original Estimate: 3 days > Remaining Estimate: 3 days > > SSOs are currently invalidated when all sessions associated with the SSO are expired. The problem is webapp undeploy or server shutdown can result in all sessions being expired, even though the sessions are distributed and can thus be accessed on other cluster nodes. If the user then fails over to another server, the SSO is gone. > Not invalidating SSOs when all sessions expire can lead to memory leaks -- SSOs that never can removed from the local and distributed caches. > Idea here is to timestamp the sso when all its sessions are expired, and then some configurable time later invalidate the sso if no new sessions have been added. > Issues: > 1) The TC background thread doesn't call into Valves, so there is no natural thread to check for "expired" SSOs. I'm considering hijacking the regular TC bg thread, since it ends up calling into the valve whenever it expires a session. That's ugly though. > 2) Have to make sure that the other cluster nodes know the sso is "semi-expired" so they can do the expiration check, since often the node where the sso originally lived has been shut down. This should be simple; just another TreeCache event to monitor. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBAS-3096) Add a maxInactiveInterval concept to ClusteredSingleSignOn

by Brian Stansberry (JIRA)

[ http://jira.jboss.com/jira/browse/JBAS-3096?page=all ] Brian Stansberry updated JBAS-3096: ----------------------------------- Comment: was deleted > Add a maxInactiveInterval concept to ClusteredSingleSignOn > ---------------------------------------------------------- > > Key: JBAS-3096 > URL: http://jira.jboss.com/jira/browse/JBAS-3096 > Project: JBoss Application Server > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: Web (Tomcat) service, Security, Clustering > Reporter: Brian Stansberry > Assigned To: Brian Stansberry > Fix For: JBossAS-4.0.5.GA > > Original Estimate: 3 days > Remaining Estimate: 3 days > > SSOs are currently invalidated when all sessions associated with the SSO are expired. The problem is webapp undeploy or server shutdown can result in all sessions being expired, even though the sessions are distributed and can thus be accessed on other cluster nodes. If the user then fails over to another server, the SSO is gone. > Not invalidating SSOs when all sessions expire can lead to memory leaks -- SSOs that never can removed from the local and distributed caches. > Idea here is to timestamp the sso when all its sessions are expired, and then some configurable time later invalidate the sso if no new sessions have been added. > Issues: > 1) The TC background thread doesn't call into Valves, so there is no natural thread to check for "expired" SSOs. I'm considering hijacking the regular TC bg thread, since it ends up calling into the valve whenever it expires a session. That's ugly though. > 2) Have to make sure that the other cluster nodes know the sso is "semi-expired" so they can do the expiration check, since often the node where the sso originally lived has been shut down. This should be simple; just another TreeCache event to monitor. -- 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, 11 months

1
0
0 / 0

[JBoss JIRA] Created: (JBESB-116) Parameter checking

by Mark Little (JIRA)

Parameter checking ------------------ Key: JBESB-116 URL: http://jira.jboss.com/jira/browse/JBESB-116 Project: JBoss ESB Issue Type: Feature Request Security Level: Public (Everyone can see) Components: ESB Core Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Priority: Minor Look at a convention like -paramname <param> for passing in parameters on the command line, rather than assuming element N in a list is param. -- 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, 11 months

1
3
0 / 0

[JBoss JIRA] Created: (JBESB-126) Remove references to LDAP and Processors from diagrams in programmers guide.

by Mark Little (JIRA)

Remove references to LDAP and Processors from diagrams in programmers guide. ---------------------------------------------------------------------------- Key: JBESB-126 URL: http://jira.jboss.com/jira/browse/JBESB-126 Project: JBoss ESB Issue Type: Task Security Level: Public (Everyone can see) Components: Documentation Affects Versions: 4.0 Beta 1 Reporter: Mark Little Assigned To: Mark Little Fix For: 4.0 -- 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, 11 months

1
3
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