[
https://issues.apache.org/jira/browse/DIRSERVER-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex Karasulu closed DIRSERVER-1166.
------------------------------------
Resolution: Won't Fix
I've investigated and don't think this is the case and anyways we're rewriting
all this code with the bigbang refactoring with the new event mechanism so we
can keep a close eye on PS efficiency to make sure it's not claiming a thread
indefinitely.
> a lot of Persistent searches may exhaust the available threads
> --------------------------------------------------------------
>
> Key: DIRSERVER-1166
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1166
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.2
> Reporter: Emmanuel Lecharny
> Assignee: Alex Karasulu
> Priority: Blocker
> Fix For: 1.5.3
>
>
> While just trying to understand how the network layer works, I was wondering
> if PersistentSearch might be a problem.
> It seems that each persistent search is consuming a thread, in order to keep
> the communication with the client open. As we are using a limited size pool
> of thread, I'm afraid that the server may simply stop responding if we have
> as many PS as nuber of threads in the pool.
> It may be a false alarm...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
