Stefan, Answers below.
Regards, Dave. > On Jul 4, 2021, at 8:59 AM, Stefan Seelmann <m...@stefan-seelmann.de> wrote: > > Hi Dave, > > On 7/4/21 2:00 AM, David Filip wrote: >> Greetings, >> >> I have noticed that when deleting entries too fast using Apache Directory >> Studio Version: 2.0.0.v20210213-M16 (ApacheDS 2.0.0.AM26), I receive the >> following error: >> >> ERR_04169_RESPONSE_QUEUE_EMPTIED The response queue has been emptied, no >> response was found >> >> >> >> I am not sure if this is a Studio (frontend) or ApacheDS (backend) issue? > > Can you please give detailed information about your environment? > > Studio: Which operating system and which Java version do you use? > Running Apache Directory Studio (Version: 2.0.0.v20210213-M16) on macOS Catalina (10.15.7). Connecting from Apache Directory Studio on macOS connected to Apache Directory Server (apacheds-2.0.0.AM26) running on Linux (Raspbian GNU/Linux 10 (Debian Buster). Yes, I wait for the prior batch deletion to complete to 100% before attempting to delete another batch. I usually try to wait about 1 second for every entry deleted, which is frequently insufficien (e.g., if I delete 30 entries, I wait 30 seconds before attempting to delete the next batch, AFTER the prior batch reaches 100%). > Server: Do you use the ApacheDS embedded in Studio? Otherwise which type > of directory server do you use? > >> To Reproduce: >> >> Load a large number (200) of entire into the directory via JNDI API. >> >> After the load completes, select 8 - 10 entries at a time in Studio, hit the >> [Delete] key, and confirm deleting those entries. >> >> If done successively, without waiting a sufficient amount of time, will >> generate the above error, and not all of the selected entries will have been >> deleted (but usually one or a few have been deleted). Hit F5 to refresh to >> determine which entires still remain. >> >> Expected Result: >> >> All entires should be successfully deleted without any error or warning >> message. >> >> Work Around: >> >> Wait 30 - 60 scones between each batch (8 - 10 entires) of deletions. Or >> select a smaller set of entries (5 - 6) and wait 15 - 20 seconds between >> each batch. >> >> Has anyone else experienced this? Is this a known limitation? > > I the previous batch completed before you run the next batch? If a batch > is still running it should show up in the "Progress" view [1], and after > it finished the "LDAP Browser" view usually is refreshed. In you run a > 2nd delete batch while the first one is still running it may be related > to the fact that the LDAP API is not really thread safe [2], so if the > same connection is used for multiple operations unexpected things may > happen. > > Kind Regards, > Stefan > > > [1] > https://nightlies.apache.org/directory/studio/2.0.0.v20210213-M16/userguide/ldap_browser/tools_progress_view.html > > <https://nightlies.apache.org/directory/studio/2.0.0.v20210213-M16/userguide/ldap_browser/tools_progress_view.html> > [2] https://issues.apache.org/jira/browse/DIRAPI-237 > <https://issues.apache.org/jira/browse/DIRAPI-237> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@directory.apache.org > <mailto:users-unsubscr...@directory.apache.org> > For additional commands, e-mail: users-h...@directory.apache.org > <mailto:users-h...@directory.apache.org>
