[jboss-jira] [JBoss JIRA] Updated: (JBAS-6039) Change JGroups thread pool rejection policy to 'Discard'
Brian Stansberry (JIRA)
jira-events at lists.jboss.org
Fri Nov 14 13:10:36 EST 2008
[ https://jira.jboss.org/jira/browse/JBAS-6039?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Stansberry updated JBAS-6039:
-----------------------------------
Component/s: Clustering
Fix Version/s: JBossAS-5.0.0.GA
(was: JBossAS-5.0.1.CR1)
Assignee: Brian Stansberry
I forgot to add the 'Clustering' component so it didn't auto-assign to me. I actually did this several weeks ago, but the unassigned JIRA fell off my radar screen.
> Change JGroups thread pool rejection policy to 'Discard'
> --------------------------------------------------------
>
> Key: JBAS-6039
> URL: https://jira.jboss.org/jira/browse/JBAS-6039
> Project: JBoss Application Server
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Clustering
> Affects Versions: JBossAS-5.0.0.CR2
> Reporter: Brian Stansberry
> Assignee: Brian Stansberry
> Fix For: JBossAS-5.0.0.GA
>
>
> Change the standard stacks so thread_pool.rejection_policy="Discard" rather than 'Run'. Run allows the packet reader thread to pass messages up the stack and possibly block, leading to a disfunctional channel. The http session replication soak tests Radoslav Husar is doing were able to generate sufficient load to cause this.
> At the same time I'll look at the thread pool min sizes.
--
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
More information about the jboss-jira
mailing list