You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <ji...@apache.org> on 2007/08/16 08:37:30 UTC
[jira] Created: (DIRSERVER-1019) Using same thread pool for I/O
processing as request handling
Using same thread pool for I/O processing as request handling
--------------------------------------------------------------
Key: DIRSERVER-1019
URL: https://issues.apache.org/jira/browse/DIRSERVER-1019
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: pre-1.0, 1.0-RC1, 1.0-RC2, 1.0-RC3, 1.0-RC4, 1.0, 1.5.0, 1.0.1, 1.0.2
Reporter: Alex Karasulu
Assignee: Alex Karasulu
Priority: Blocker
Fix For: 1.5.1, 1.0.3
In the ServerContext factory the same thread pool is being used to process I/O
and request handling. This is depleting the thread pool rapidly causing the
server to hang under certain conditions. I caught this bug on a x86_64 machine
with multiple cores when the ReferralITest test was hanging. The right number
of connections and requests being processed could have caused this issue to
arrise. Regardless thankfully the issue appeared and Trustin found the cause
for it.
Trustin tracked the bug down to the way we misconfigured MINA's thread pools.
He is currently fixing the problem in trunk and I suspect the same issue exists
within the 1.0 branch.
I suspect this could have caused serious issues in performance if not causing
several load test clients to hang while others had requests processed. I
recommend reassessing performance metrics once again after this fix. There
should be a considerable boost. I think our impression that MINA was a
bottleneck may have been attributed to this misconfiguration issue.
Anyways once Trustin has the fix in trunk I will apply it to the 1.0 branch and
make sure all tests pass successfully. I am assigning this issue to myself
even though T is providing the fix so I can manage the application on the
1.0 branch and document the results.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-1019) Using same thread pool for I/O
processing and request handling causes clients to hang and MINA thread pool
depletion
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-1019:
-------------------------------------
Summary: Using same thread pool for I/O processing and request handling causes clients to hang and MINA thread pool depletion (was: Using same thread pool for I/O processing as request handling )
Improving title for clarity
> Using same thread pool for I/O processing and request handling causes clients to hang and MINA thread pool depletion
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1019
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1019
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0.2, 1.0.1, 1.5.0, 1.0, 1.0-RC4, 1.0-RC3, 1.0-RC2, 1.0-RC1, pre-1.0
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.1, 1.0.3
>
>
> In the ServerContext factory the same thread pool is being used to process I/O
> and request handling. This is depleting the thread pool rapidly causing the
> server to hang under certain conditions. I caught this bug on a x86_64 machine
> with multiple cores when the ReferralITest test was hanging. The right number
> of connections and requests being processed could have caused this issue to
> arrise. Regardless thankfully the issue appeared and Trustin found the cause
> for it.
> Trustin tracked the bug down to the way we misconfigured MINA's thread pools.
> He is currently fixing the problem in trunk and I suspect the same issue exists
> within the 1.0 branch.
> I suspect this could have caused serious issues in performance if not causing
> several load test clients to hang while others had requests processed. I
> recommend reassessing performance metrics once again after this fix. There
> should be a considerable boost. I think our impression that MINA was a
> bottleneck may have been attributed to this misconfiguration issue.
> Anyways once Trustin has the fix in trunk I will apply it to the 1.0 branch and
> make sure all tests pass successfully. I am assigning this issue to myself
> even though T is providing the fix so I can manage the application on the
> 1.0 branch and document the results.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (DIRSERVER-1019) Using same thread pool for I/O
processing and request handling causes clients to hang and MINA thread pool
depletion
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu closed DIRSERVER-1019.
------------------------------------
Resolution: Fixed
This has been fixed thanks to Trustin.
> Using same thread pool for I/O processing and request handling causes clients to hang and MINA thread pool depletion
> --------------------------------------------------------------------------------------------------------------------
>
> Key: DIRSERVER-1019
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1019
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.0.2, 1.0.1, 1.5.0, 1.0, 1.0-RC4, 1.0-RC3, 1.0-RC2, 1.0-RC1, pre-1.0
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.1, 1.0.3
>
>
> In the ServerContext factory the same thread pool is being used to process I/O
> and request handling. This is depleting the thread pool rapidly causing the
> server to hang under certain conditions. I caught this bug on a x86_64 machine
> with multiple cores when the ReferralITest test was hanging. The right number
> of connections and requests being processed could have caused this issue to
> arrise. Regardless thankfully the issue appeared and Trustin found the cause
> for it.
> Trustin tracked the bug down to the way we misconfigured MINA's thread pools.
> He is currently fixing the problem in trunk and I suspect the same issue exists
> within the 1.0 branch.
> I suspect this could have caused serious issues in performance if not causing
> several load test clients to hang while others had requests processed. I
> recommend reassessing performance metrics once again after this fix. There
> should be a considerable boost. I think our impression that MINA was a
> bottleneck may have been attributed to this misconfiguration issue.
> Anyways once Trustin has the fix in trunk I will apply it to the 1.0 branch and
> make sure all tests pass successfully. I am assigning this issue to myself
> even though T is providing the fix so I can manage the application on the
> 1.0 branch and document the results.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.