You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2011/09/08 13:05:12 UTC
[jira] [Created] (DIRSERVER-1656) We need a separate thread to
process the consumer log
We need a separate thread to process the consumer log
-----------------------------------------------------
Key: DIRSERVER-1656
URL: https://issues.apache.org/jira/browse/DIRSERVER-1656
Project: Directory ApacheDS
Issue Type: Bug
Affects Versions: 2.0.0-M2
Reporter: Emmanuel Lecharny
Priority: Critical
Fix For: 2.0.0-M4
We don't use a séparate thread to process the consumer logs, which make it possible that in some cases, when the consumer has been shut down and reconnect, it does not receive all the modifications.
We should use a thread to process the consumer logs, which will be activated when the consumer reconnect.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (DIRSERVER-1656) We need a separate thread to
process the consumer log
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny resolved DIRSERVER-1656.
------------------------------------------
Resolution: Won't Fix
Not a problem in trunk
> We need a separate thread to process the consumer log
> -----------------------------------------------------
>
> Key: DIRSERVER-1656
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1656
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M2
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-M7
>
>
> We don't use a séparate thread to process the consumer logs, which make it possible that in some cases, when the consumer has been shut down and reconnect, it does not receive all the modifications.
> We should use a thread to process the consumer logs, which will be activated when the consumer reconnect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (DIRSERVER-1656) We need a separate thread to
process the consumer log
Posted by "Pierre-Arnaud Marcelot (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot updated DIRSERVER-1656:
----------------------------------------------
Fix Version/s: (was: 2.0.0-M4)
2.0.0-M5
> We need a separate thread to process the consumer log
> -----------------------------------------------------
>
> Key: DIRSERVER-1656
> URL: https://issues.apache.org/jira/browse/DIRSERVER-1656
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 2.0.0-M2
> Reporter: Emmanuel Lecharny
> Priority: Critical
> Fix For: 2.0.0-M5
>
>
> We don't use a séparate thread to process the consumer logs, which make it possible that in some cases, when the consumer has been shut down and reconnect, it does not receive all the modifications.
> We should use a thread to process the consumer logs, which will be activated when the consumer reconnect.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira