[JBoss JIRA] Created: (JBAS-5414) Application class loaders leak to JGroups thread pools
by Brian Stansberry (JIRA)
Application class loaders leak to JGroups thread pools
------------------------------------------------------
Key: JBAS-5414
URL: http://jira.jboss.com/jira/browse/JBAS-5414
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Fix For: JBossAS-5.0.0.CR1
Application threads carrying messages down can end up creating pool threads in the various JGroups thread pools, and will leak their TCCL to the pool thread.
Immediate solution is to have the AS channel factory inject specialized thread pools into the channels it creates. Specialized thread pool will ensure TCCL leaks don't occur, using the same basic approach as was used for JBCOMMON-41.
We'll see whether JGroups can add the ability to handle this itself.
Also need to ensure that the default domain classloader is the TCCLwhenever the AS (including EJB3 and Hibernate) connects a channel. This will prevent leakage of user deployment classloaders to the many JGroups threads created during Channel.connect(). Currently this isn't an issue as all channels are created as part of deployment of core services where the TCCL is the default domain loader. But, this will become an issue as we switch to lazy-initializing JBoss Cache instances as part of deploying user apps.
--
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, 2 months
[JBoss JIRA] Created: (JBAS-5735) Session not reliably bound to SessionReplicationContext if SecurityAssocationValve not present
by Brian Stansberry (JIRA)
Session not reliably bound to SessionReplicationContext if SecurityAssocationValve not present
----------------------------------------------------------------------------------------------
Key: JBAS-5735
URL: http://jira.jboss.com/jira/browse/JBAS-5735
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: Clustering, Web (Tomcat) service
Affects Versions: JBossAS-5.0.0.CR1, JBossAS-4.2.2.GA
Reporter: Brian Stansberry
Assigned To: Brian Stansberry
Priority: Minor
Fix For: JBossAS-4.2.3.GA, JBossAS-5.0.0.CR2
The call in JBossCacheManager.findSession(String id) to SessionReplicationContext.bindSession(...) only binds the session if ClusteredSessionValve has first called SessionReplicationContext.enterWebapp() to establish the context. The problem is, if any code calls Request.getSession(...) before ClusteredSessionValve is invoked, the session will be cached in the request, not bound to the context, and subsequent calls to Request.getSession(...) will use the cached session and never call JBossCacheManager.findSession(...). Result is the session will never be bound to the context and won't be replicated.
BatchReplicationClusteredSessionValve calls Request.getSession(...) before ClusteredSessionValve is invoked. SecurityAssocationValve happens to save us, by providentially calling Manager.findSession(...) after the request has passed through ClusteredSessionValve. But that's just good luck; we need to make sure the session is properly bound to the context.
--
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, 2 months
[JBoss JIRA] Created: (JBAS-5585) Fix tomcat federation tests
by Anil Saldhana (JIRA)
Fix tomcat federation tests
---------------------------
Key: JBAS-5585
URL: http://jira.jboss.com/jira/browse/JBAS-5585
Project: JBoss Application Server
Issue Type: Sub-task
Security Level: Public (Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.0.0.Beta4
Reporter: Anil Saldhana
Assigned To: Stefan Guilhen
Fix For: JBossAS-5.0.0.CR1
Tests such as:
org.jboss.test.web.security.AuthenticatorsExternalizationTestCase(tomcat-federation).testHeaderBasedAuthentication 1.109 12
org.jboss.test.web.security.CustomHeaderAuthTestCase(tomcat-federation).unknown 0.0030 12
org.jboss.test.web.test.FormAuthUnitTestCase(tomcat-federation).testPostDataFormAuth 0.097 12
org.jboss.test.web.test.FormAuthUnitTestCase(tomcat-federation).testFlushOnSessionInvalidation 0.086 12
--
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, 2 months