Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: 0.8.0
    • Fix Version/s: 1.1.0
    • Component/s: studio-ldapbrowser
    • Labels:
      None
    • Environment:
      Client where software installed: Windows XP sp2
      LDAP host: Sun Directory 5.1 sp2

      Description

      When performing a query against the LDAP server (consumer) the number of returned entries returned from a search looks to be page limiting the results to approximately 500 entries. The requirement is for a filter to return over 100K entries ...that is not working. The directory instance is set to allow the return of 300K entries and a search time out of 3600 seconds.

      The initial search results may return < 500 users in a search time of <10 seconds.

      Have a look and let me know what you find. >> Matt

      1. My LS configuration.jpg
        86 kB
        Matt Green
      2. mgreen
        2.43 MB
        Matt Green
      3. screenshot-1.jpg
        65 kB
        Matt Green

        Activity

        Hide
        Matt Green added a comment -

        This is the result of my client configuration

            • Date: Mon May 07 16:00:26 CDT 2007
            • Platform Details:
            • System properties:
              awt.toolkit=sun.awt.windows.WToolkit
              eclipse.commands=-os
              win32
              -ws
              win32
              -arch
              x86
              -launcher
              C:\Program Files\LDAP Studio\LDAP Studio.exe
              -name
              LDAP Studio
              -showsplash
              600
              -exitdata
              a00_74
              -vm
              C:\WINDOWS\system32\javaw.exe
              eclipse.ee.install.verify=false
              eclipse.product=org.apache.directory.ldapstudio.product
              eclipse.startTime=1178571205699
              eclipse.vm=C:\WINDOWS\system32\javaw.exe
              eclipse.vmargs=-jar
              C:\Program Files\LDAP Studio\startup.jar
              file.encoding=Cp1252
              file.encoding.pkg=sun.io
              file.separator=\
              java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
              java.awt.printerjob=sun.awt.windows.WPrinterJob
              java.class.path=C:\Program Files\LDAP Studio\startup.jar
              java.class.version=49.0
              java.endorsed.dirs=C:\Program Files\Java\jre1.5.0_11\lib\endorsed
              java.ext.dirs=C:\Program Files\Java\jre1.5.0_11\lib\ext
              java.home=C:\Program Files\Java\jre1.5.0_11
              java.io.tmpdir=C:\DOCUME~1\957178\LOCALS~1\Temp\
              java.library.path=C:\WINDOWS\system32;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Compaq\Compaq Management Agents\Dmi\Win32\Bin;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH;D:\DSRK\bin\dsrk52;C:\j2sdk1.4.2_13\bin
              java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
              java.runtime.version=1.5.0_11-b03
              java.specification.name=Java Platform API Specification
              java.specification.vendor=Sun Microsystems Inc.
              java.specification.version=1.5
              java.vendor=Sun Microsystems Inc.
              java.vendor.url=http://java.sun.com/
              java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
              java.version=1.5.0_11
              java.vm.info=mixed mode, sharing
              java.vm.name=Java HotSpot(TM) Client VM
              java.vm.specification.name=Java Virtual Machine Specification
              java.vm.specification.vendor=Sun Microsystems Inc.
              java.vm.specification.version=1.0
              java.vm.vendor=Sun Microsystems Inc.
              java.vm.version=1.5.0_11-b03
              line.separator=

        org.osgi.framework.bootdelegation=*
        org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5
        org.osgi.framework.language=en
        org.osgi.framework.os.name=WindowsXP
        org.osgi.framework.os.version=5.1
        org.osgi.framework.processor=x86
        org.osgi.framework.system.packages=javax.accessibility,javax.activity,javax.crypto,javax.crypto.interfaces,javax.crypto.spec,javax.imageio,javax.imageio.event,javax.imageio.metadata,javax.imageio.plugins.bmp,javax.imageio.plugins.jpeg,javax.imageio.spi,javax.imageio.stream,javax.management,javax.management.loading,javax.management.modelmbean,javax.management.monitor,javax.management.openmbean,javax.management.relation,javax.management.remote,javax.management.remote.rmi,javax.management.timer,javax.naming,javax.naming.directory,javax.naming.event,javax.naming.ldap,javax.naming.spi,javax.net,javax.net.ssl,javax.print,javax.print.attribute,javax.print.attribute.standard,javax.print.event,javax.rmi,javax.rmi.CORBA,javax.rmi.ssl,javax.security.auth,javax.security.auth.callback,javax.security.auth.kerberos,javax.security.auth.login,javax.security.auth.spi,javax.security.auth.x500,javax.security.cert,javax.security.sasl,javax.sound.midi,javax.sound.midi.spi,javax.sound.sampled,javax.sound.sampled.spi,javax.sql,javax.sql.rowset,javax.sql.rowset.serial,javax.sql.rowset.spi,javax.swing,javax.swing.border,javax.swing.colorchooser,javax.swing.event,javax.swing.filechooser,javax.swing.plaf,javax.swing.plaf.basic,javax.swing.plaf.metal,javax.swing.plaf.multi,javax.swing.plaf.synth,javax.swing.table,javax.swing.text,javax.swing.text.html,javax.swing.text.html.parser,javax.swing.text.rtf,javax.swing.tree,javax.swing.undo,javax.transaction,javax.transaction.xa,javax.xml,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stream,javax.xml.validation,javax.xml.xpath,org.ietf.jgss,org.omg.CORBA,org.omg.CORBA_2_3,org.omg.CORBA_2_3.portable,org.omg.CORBA.DynAnyPackage,org.omg.CORBA.ORBPackage,org.omg.CORBA.portable,org.omg.CORBA.TypeCodePackage,org.omg.CosNaming,org.omg.CosNaming.NamingContextExtPackage,org.omg.CosNaming.NamingContextPackage,org.omg.Dynamic,org.omg.DynamicAny,org.omg.DynamicAny.DynAnyFactoryPackage,org.omg.DynamicAny.DynAnyPackage,org.omg.IOP,org.omg.IOP.CodecFactoryPackage,org.omg.IOP.CodecPackage,org.omg.Messaging,org.omg.PortableInterceptor,org.omg.PortableInterceptor.ORBInitInfoPackage,org.omg.PortableServer,org.omg.PortableServer.CurrentPackage,org.omg.PortableServer.POAManagerPackage,org.omg.PortableServer.POAPackage,org.omg.PortableServer.portable,org.omg.PortableServer.ServantLocatorPackage,org.omg.SendingContext,org.omg.stub.java.rmi,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.events,org.w3c.dom.ls,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers
        org.osgi.framework.vendor=Eclipse
        org.osgi.framework.version=1.3.0
        org.osgi.supports.framework.extension=true
        os.arch=x86
        os.name=Windows XP
        os.version=5.1
        osgi.arch=x86
        osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start
        osgi.bundles.defaultStartLevel=4
        osgi.bundlestore=C:\Program Files\LDAP Studio\configuration\org.eclipse.osgi\bundles
        osgi.configuration.area=file:/C:/Program Files/LDAP Studio/configuration/
        osgi.framework=file:/c:/Program Files/LDAP Studio/plugins/org.eclipse.osgi_3.2.1.R32x_v20060919.jar
        osgi.framework.beginningstartlevel=1
        osgi.framework.shape=jar
        osgi.framework.version=3.2.1.R32x_v20060919
        osgi.install.area=file:/C:/Program Files/LDAP Studio/
        osgi.instance.area=file:/C:/Documents and Settings/957178/.ldapstudio/
        osgi.instance.area.default=file:/C:/Documents and Settings/957178/.ldapstudio/
        osgi.logfile=C:\Documents and Settings\957178\.ldapstudio\.metadata\.log
        osgi.manifest.cache=C:\Program Files\LDAP Studio\configuration\org.eclipse.osgi\manifests
        osgi.nl=en_US
        osgi.os=win32
        osgi.splashLocation=c:\Program Files\LDAP Studio\configuration\org.eclipse.osgi\splash.bmp
        osgi.splashPath=platform:/base/plugins/org.apache.directory.ldapstudio
        osgi.syspath=c:\Program Files\LDAP Studio\plugins
        osgi.ws=win32
        path.separator=;
        sun.arch.data.model=32
        sun.boot.class.path=C:\Program Files\Java\jre1.5.0_11\lib\rt.jar;C:\Program Files\Java\jre1.5.0_11\lib\i18n.jar;C:\Program Files\Java\jre1.5.0_11\lib\sunrsasign.jar;C:\Program Files\Java\jre1.5.0_11\lib\jsse.jar;C:\Program Files\Java\jre1.5.0_11\lib\jce.jar;C:\Program Files\Java\jre1.5.0_11\lib\charsets.jar;C:\Program Files\Java\jre1.5.0_11\classes
        sun.boot.library.path=C:\Program Files\Java\jre1.5.0_11\bin
        sun.cpu.endian=little
        sun.cpu.isalist=
        sun.desktop=windows
        sun.io.unicode.encoding=UnicodeLittle
        sun.java.launcher=SUN_STANDARD
        sun.jnu.encoding=Cp1252
        sun.management.compiler=HotSpot Client Compiler
        sun.os.patch.level=Service Pack 2
        user.country=US
        user.dir=C:\Program Files\LDAP Studio
        user.home=C:\Documents and Settings\957178
        user.language=en
        user.name=957178
        user.timezone=America/Chicago
        user.variant=

            • Features:
            • Plug-in Registry:
              com.ibm.icu (3.4.5) "International Components for Unicode for Java (ICU4J)" [Active]
              org.apache.directory.ldapstudio (0.7.0) "LDAP Studio RCP Application" [Active]
              org.apache.directory.ldapstudio.aciitemeditor (0.8.0) "LDAP Studio ACI Item Editor Plug-in" [Active]
              org.apache.directory.ldapstudio.apacheds.configuration (0.8.0) "LDAP Studio Apache DS Configuration Plug-in" [Resolved]
              org.apache.directory.ldapstudio.apacheds.configuration.help (0.8.0) "LDAP Studio Apache DS Configuration Help Plugin" [Resolved]
              org.apache.directory.ldapstudio.browser.common (0.8.0) "LDAP Studio Browser Common Plug-in" [Active]
              org.apache.directory.ldapstudio.browser.core (0.8.0) "LDAP Studio Browser Core Plugin" [Active]
              org.apache.directory.ldapstudio.browser.help (0.6.0) "LDAP Studio Browser Help Plugin" [Resolved]
              org.apache.directory.ldapstudio.browser.ui (0.8.0) "LDAP Studio Browser UI Plugin" [Active]
              org.apache.directory.ldapstudio.help (0.6.0) "LDAP Studio Help Plugin" [Resolved]
              org.apache.directory.ldapstudio.jars (0.8.0) "LDAP Studio Jars Plugin" [Resolved]
              org.apache.directory.ldapstudio.ldifeditor (0.8.0) "LDAP Studio LDIF Editor Plug-in" [Active]
              org.apache.directory.ldapstudio.schemas (0.8.0) "LDAP Studio Schemas Editor Plug-in" [Resolved]
              org.apache.directory.ldapstudio.schemas.help (0.6.0) "LDAP Studio Schemas Editor Help Plugin" [Resolved]
              org.apache.directory.ldapstudio.valueeditors (0.8.0) "LDAP Studio Value Editors Plug-in" [Active]
              org.apache.lucene (1.4.103.v20060601) "Apache Lucene" [Resolved]
              org.eclipse.core.commands (3.2.0.I20060605-1400) "Commands" [Resolved]
              org.eclipse.core.contenttype (3.2.0.v20060603) "Eclipse Content Mechanism" [Active]
              org.eclipse.core.expressions (3.2.1.r321_v20060721) "Expression Language" [Active]
              org.eclipse.core.filebuffers (3.2.1.r321_v20060721) "File Buffers" [Active]
              org.eclipse.core.filesystem (1.0.0.v20060603) "Core File Systems" [Resolved]
              org.eclipse.core.jobs (3.2.0.v20060603) "Eclipse Jobs Mechanism" [Active]
              org.eclipse.core.resources (3.2.1.R32x_v20060914) "Core Resource Management" [Active]
              org.eclipse.core.runtime (3.2.0.v20060603) "Core Runtime" [Active]
              org.eclipse.core.runtime.compatibility (3.1.100.v20060603) "Core Runtime Plug-in Compatibility" [Active]
              org.eclipse.core.runtime.compatibility.auth (3.2.0.v20060511) "Authorization Compatibility Plug-in" [Active]
              org.eclipse.core.runtime.compatibility.registry (3.2.1.R32x_v20060907) "Eclipse Registry Compatibility Fragment" [Resolved]
              org.eclipse.equinox.common (3.2.0.v20060603) "Common Eclipse Runtime" [Active]
              org.eclipse.equinox.preferences (3.2.1.R32x_v20060717) "Eclipse Preferences Mechanism" [Active]
              org.eclipse.equinox.registry (3.2.1.R32x_v20060814) "Extension Registry Support" [Active]
              org.eclipse.help (3.2.1.R321_v20060920) "Help System Core" [Active]
              org.eclipse.help.appserver (3.1.100.v20060602) "Help Application Server" [Resolved]
              org.eclipse.help.base (3.2.1.R321_v20060822) "Help System Base" [Resolved]
              org.eclipse.help.ui (3.2.0.v20060602) "Help System UI" [Resolved]
              org.eclipse.help.webapp (3.2.1.R321_v20060803) "Help System Webapp" [Resolved]
              org.eclipse.jface (3.2.1.M20060908-1000) "JFace" [Resolved]
              org.eclipse.jface.databinding (1.0.0.I20060605-1400) "JFace Data Binding" [Resolved]
              org.eclipse.jface.text (3.2.1.r321_v20060810) "JFace Text" [Resolved]
              org.eclipse.rcp (3.2.0.v20060605) "Eclipse RCP" [Resolved]
              org.eclipse.sdk (3.2.1.r321_v20060705) "Eclipse Project SDK" [Installed]
              org.eclipse.search (3.2.1.r321_v20060726) "Search Support" [Active]
              org.eclipse.swt (3.2.1.v3235e) "Standard Widget Toolkit" [Resolved]
              org.eclipse.swt.win32.win32.x86 (3.2.1.v3235) "Standard Widget Toolkit for Windows" [Resolved]
              org.eclipse.text (3.2.0.v20060605-1400) "Text" [Resolved]
              org.eclipse.tomcat (4.1.130.v20060601) "Tomcat Wrapper" [Resolved]
              org.eclipse.ui (3.2.1.M20060913-0800) "Eclipse UI" [Active]
              org.eclipse.ui.editors (3.2.1.r321_v20060721) "Default Text Editor" [Active]
              org.eclipse.ui.forms (3.2.0.v20060602) "Eclipse Forms" [Active]
              org.eclipse.ui.ide (3.2.1.M20060915-1030) "Eclipse IDE UI" [Resolved]
              org.eclipse.ui.views (3.2.1.M20060906-0800) "Views" [Active]
              org.eclipse.ui.workbench (3.2.1.M20060906-0800) "Workbench" [Active]
              org.eclipse.ui.workbench.texteditor (3.2.0.v20060605-1400) "Text Editor Framework" [Active]
              org.eclipse.update.configurator (3.2.1.v20092006) "Install/Update Configurator" [Active]
              org.eclipse.update.core (3.2.1.v20092006) "Install/Update Core" [Resolved]
              org.eclipse.update.ui (3.2.1.v20092006) "Install/Update UI" [Resolved]
              system.bundle (3.2.1.R32x_v20060919) "OSGi System Bundle" [Active]
            • User Preferences:
              #Mon May 07 16:00:26 CDT 2007
              @org.eclipse.ui.editors=3.2.1.r321_v20060721
              @org.apache.directory.ldapstudio.browser.common=0.8.0
              /instance/org.eclipse.core.resources/version=1
              @org.eclipse.core.resources=3.2.1.R32x_v20060914
              /instance/org.eclipse.ui.editors/overviewRuler_migration=migrated_3.1
              /instance/org.apache.directory.ldapstudio.browser.ui/searchResultEditorShowDn=false
              /instance/org.apache.directory.ldapstudio.browser.common/browserEnableFolding=false
              !/=
              /instance/org.apache.directory.ldapstudio.browser.common/templates=<?xml version\="1.0" encoding\="UTF-8"?><templates/>
              /instance/org.apache.directory.ldapstudio.browser.ui/searchResultEditorShowLinks=false
              file_export_version=3.0
              /instance/org.apache.directory.ldapstudio.ldifeditor/templates=<?xml version\="1.0" encoding\="UTF-8"?><templates/>
              @org.apache.directory.ldapstudio.ldifeditor=0.8.0
              @org.apache.directory.ldapstudio.browser.ui=0.8.0
        Show
        Matt Green added a comment - This is the result of my client configuration Date: Mon May 07 16:00:26 CDT 2007 Platform Details: System properties: awt.toolkit=sun.awt.windows.WToolkit eclipse.commands=-os win32 -ws win32 -arch x86 -launcher C:\Program Files\LDAP Studio\LDAP Studio.exe -name LDAP Studio -showsplash 600 -exitdata a00_74 -vm C:\WINDOWS\system32\javaw.exe eclipse.ee.install.verify=false eclipse.product=org.apache.directory.ldapstudio.product eclipse.startTime=1178571205699 eclipse.vm=C:\WINDOWS\system32\javaw.exe eclipse.vmargs=-jar C:\Program Files\LDAP Studio\startup.jar file.encoding=Cp1252 file.encoding.pkg=sun.io file.separator=\ java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment java.awt.printerjob=sun.awt.windows.WPrinterJob java.class.path=C:\Program Files\LDAP Studio\startup.jar java.class.version=49.0 java.endorsed.dirs=C:\Program Files\Java\jre1.5.0_11\lib\endorsed java.ext.dirs=C:\Program Files\Java\jre1.5.0_11\lib\ext java.home=C:\Program Files\Java\jre1.5.0_11 java.io.tmpdir=C:\DOCUME~1\957178\LOCALS~1\Temp\ java.library.path=C:\WINDOWS\system32;.;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\Program Files\Compaq\Compaq Management Agents\Dmi\Win32\Bin;C:\WINDOWS\System32\Wbem;C:\WINDOWS\system32\nls;C:\WINDOWS\system32\nls\ENGLISH;D:\DSRK\bin\dsrk52;C:\j2sdk1.4.2_13\bin java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition java.runtime.version=1.5.0_11-b03 java.specification.name=Java Platform API Specification java.specification.vendor=Sun Microsystems Inc. java.specification.version=1.5 java.vendor=Sun Microsystems Inc. java.vendor.url= http://java.sun.com/ java.vendor.url.bug= http://java.sun.com/cgi-bin/bugreport.cgi java.version=1.5.0_11 java.vm.info=mixed mode, sharing java.vm.name=Java HotSpot(TM) Client VM java.vm.specification.name=Java Virtual Machine Specification java.vm.specification.vendor=Sun Microsystems Inc. java.vm.specification.version=1.0 java.vm.vendor=Sun Microsystems Inc. java.vm.version=1.5.0_11-b03 line.separator= org.osgi.framework.bootdelegation=* org.osgi.framework.executionenvironment=OSGi/Minimum-1.0,OSGi/Minimum-1.1,JRE-1.1,J2SE-1.2,J2SE-1.3,J2SE-1.4,J2SE-1.5 org.osgi.framework.language=en org.osgi.framework.os.name=WindowsXP org.osgi.framework.os.version=5.1 org.osgi.framework.processor=x86 org.osgi.framework.system.packages=javax.accessibility,javax.activity,javax.crypto,javax.crypto.interfaces,javax.crypto.spec,javax.imageio,javax.imageio.event,javax.imageio.metadata,javax.imageio.plugins.bmp,javax.imageio.plugins.jpeg,javax.imageio.spi,javax.imageio.stream,javax.management,javax.management.loading,javax.management.modelmbean,javax.management.monitor,javax.management.openmbean,javax.management.relation,javax.management.remote,javax.management.remote.rmi,javax.management.timer,javax.naming,javax.naming.directory,javax.naming.event,javax.naming.ldap,javax.naming.spi,javax.net,javax.net.ssl,javax.print,javax.print.attribute,javax.print.attribute.standard,javax.print.event,javax.rmi,javax.rmi.CORBA,javax.rmi.ssl,javax.security.auth,javax.security.auth.callback,javax.security.auth.kerberos,javax.security.auth.login,javax.security.auth.spi,javax.security.auth.x500,javax.security.cert,javax.security.sasl,javax.sound.midi,javax.sound.midi.spi,javax.sound.sampled,javax.sound.sampled.spi,javax.sql,javax.sql.rowset,javax.sql.rowset.serial,javax.sql.rowset.spi,javax.swing,javax.swing.border,javax.swing.colorchooser,javax.swing.event,javax.swing.filechooser,javax.swing.plaf,javax.swing.plaf.basic,javax.swing.plaf.metal,javax.swing.plaf.multi,javax.swing.plaf.synth,javax.swing.table,javax.swing.text,javax.swing.text.html,javax.swing.text.html.parser,javax.swing.text.rtf,javax.swing.tree,javax.swing.undo,javax.transaction,javax.transaction.xa,javax.xml,javax.xml.datatype,javax.xml.namespace,javax.xml.parsers,javax.xml.transform,javax.xml.transform.dom,javax.xml.transform.sax,javax.xml.transform.stream,javax.xml.validation,javax.xml.xpath,org.ietf.jgss,org.omg.CORBA,org.omg.CORBA_2_3,org.omg.CORBA_2_3.portable,org.omg.CORBA.DynAnyPackage,org.omg.CORBA.ORBPackage,org.omg.CORBA.portable,org.omg.CORBA.TypeCodePackage,org.omg.CosNaming,org.omg.CosNaming.NamingContextExtPackage,org.omg.CosNaming.NamingContextPackage,org.omg.Dynamic,org.omg.DynamicAny,org.omg.DynamicAny.DynAnyFactoryPackage,org.omg.DynamicAny.DynAnyPackage,org.omg.IOP,org.omg.IOP.CodecFactoryPackage,org.omg.IOP.CodecPackage,org.omg.Messaging,org.omg.PortableInterceptor,org.omg.PortableInterceptor.ORBInitInfoPackage,org.omg.PortableServer,org.omg.PortableServer.CurrentPackage,org.omg.PortableServer.POAManagerPackage,org.omg.PortableServer.POAPackage,org.omg.PortableServer.portable,org.omg.PortableServer.ServantLocatorPackage,org.omg.SendingContext,org.omg.stub.java.rmi,org.w3c.dom,org.w3c.dom.bootstrap,org.w3c.dom.events,org.w3c.dom.ls,org.xml.sax,org.xml.sax.ext,org.xml.sax.helpers org.osgi.framework.vendor=Eclipse org.osgi.framework.version=1.3.0 org.osgi.supports.framework.extension=true os.arch=x86 os.name=Windows XP os.version=5.1 osgi.arch=x86 osgi.bundles=org.eclipse.equinox.common@2:start,org.eclipse.update.configurator@3:start,org.eclipse.core.runtime@start osgi.bundles.defaultStartLevel=4 osgi.bundlestore=C:\Program Files\LDAP Studio\configuration\org.eclipse.osgi\bundles osgi.configuration.area= file:/C:/Program Files/LDAP Studio/configuration/ osgi.framework= file:/c:/Program Files/LDAP Studio/plugins/org.eclipse.osgi_3.2.1.R32x_v20060919.jar osgi.framework.beginningstartlevel=1 osgi.framework.shape=jar osgi.framework.version=3.2.1.R32x_v20060919 osgi.install.area= file:/C:/Program Files/LDAP Studio/ osgi.instance.area= file:/C:/Documents and Settings/957178/.ldapstudio/ osgi.instance.area.default= file:/C:/Documents and Settings/957178/.ldapstudio/ osgi.logfile=C:\Documents and Settings\957178\.ldapstudio\.metadata\.log osgi.manifest.cache=C:\Program Files\LDAP Studio\configuration\org.eclipse.osgi\manifests osgi.nl=en_US osgi.os=win32 osgi.splashLocation=c:\Program Files\LDAP Studio\configuration\org.eclipse.osgi\splash.bmp osgi.splashPath=platform:/base/plugins/org.apache.directory.ldapstudio osgi.syspath=c:\Program Files\LDAP Studio\plugins osgi.ws=win32 path.separator=; sun.arch.data.model=32 sun.boot.class.path=C:\Program Files\Java\jre1.5.0_11\lib\rt.jar;C:\Program Files\Java\jre1.5.0_11\lib\i18n.jar;C:\Program Files\Java\jre1.5.0_11\lib\sunrsasign.jar;C:\Program Files\Java\jre1.5.0_11\lib\jsse.jar;C:\Program Files\Java\jre1.5.0_11\lib\jce.jar;C:\Program Files\Java\jre1.5.0_11\lib\charsets.jar;C:\Program Files\Java\jre1.5.0_11\classes sun.boot.library.path=C:\Program Files\Java\jre1.5.0_11\bin sun.cpu.endian=little sun.cpu.isalist= sun.desktop=windows sun.io.unicode.encoding=UnicodeLittle sun.java.launcher=SUN_STANDARD sun.jnu.encoding=Cp1252 sun.management.compiler=HotSpot Client Compiler sun.os.patch.level=Service Pack 2 user.country=US user.dir=C:\Program Files\LDAP Studio user.home=C:\Documents and Settings\957178 user.language=en user.name=957178 user.timezone=America/Chicago user.variant= Features: Plug-in Registry: com.ibm.icu (3.4.5) "International Components for Unicode for Java (ICU4J)" [Active] org.apache.directory.ldapstudio (0.7.0) "LDAP Studio RCP Application" [Active] org.apache.directory.ldapstudio.aciitemeditor (0.8.0) "LDAP Studio ACI Item Editor Plug-in" [Active] org.apache.directory.ldapstudio.apacheds.configuration (0.8.0) "LDAP Studio Apache DS Configuration Plug-in" [Resolved] org.apache.directory.ldapstudio.apacheds.configuration.help (0.8.0) "LDAP Studio Apache DS Configuration Help Plugin" [Resolved] org.apache.directory.ldapstudio.browser.common (0.8.0) "LDAP Studio Browser Common Plug-in" [Active] org.apache.directory.ldapstudio.browser.core (0.8.0) "LDAP Studio Browser Core Plugin" [Active] org.apache.directory.ldapstudio.browser.help (0.6.0) "LDAP Studio Browser Help Plugin" [Resolved] org.apache.directory.ldapstudio.browser.ui (0.8.0) "LDAP Studio Browser UI Plugin" [Active] org.apache.directory.ldapstudio.help (0.6.0) "LDAP Studio Help Plugin" [Resolved] org.apache.directory.ldapstudio.jars (0.8.0) "LDAP Studio Jars Plugin" [Resolved] org.apache.directory.ldapstudio.ldifeditor (0.8.0) "LDAP Studio LDIF Editor Plug-in" [Active] org.apache.directory.ldapstudio.schemas (0.8.0) "LDAP Studio Schemas Editor Plug-in" [Resolved] org.apache.directory.ldapstudio.schemas.help (0.6.0) "LDAP Studio Schemas Editor Help Plugin" [Resolved] org.apache.directory.ldapstudio.valueeditors (0.8.0) "LDAP Studio Value Editors Plug-in" [Active] org.apache.lucene (1.4.103.v20060601) "Apache Lucene" [Resolved] org.eclipse.core.commands (3.2.0.I20060605-1400) "Commands" [Resolved] org.eclipse.core.contenttype (3.2.0.v20060603) "Eclipse Content Mechanism" [Active] org.eclipse.core.expressions (3.2.1.r321_v20060721) "Expression Language" [Active] org.eclipse.core.filebuffers (3.2.1.r321_v20060721) "File Buffers" [Active] org.eclipse.core.filesystem (1.0.0.v20060603) "Core File Systems" [Resolved] org.eclipse.core.jobs (3.2.0.v20060603) "Eclipse Jobs Mechanism" [Active] org.eclipse.core.resources (3.2.1.R32x_v20060914) "Core Resource Management" [Active] org.eclipse.core.runtime (3.2.0.v20060603) "Core Runtime" [Active] org.eclipse.core.runtime.compatibility (3.1.100.v20060603) "Core Runtime Plug-in Compatibility" [Active] org.eclipse.core.runtime.compatibility.auth (3.2.0.v20060511) "Authorization Compatibility Plug-in" [Active] org.eclipse.core.runtime.compatibility.registry (3.2.1.R32x_v20060907) "Eclipse Registry Compatibility Fragment" [Resolved] org.eclipse.equinox.common (3.2.0.v20060603) "Common Eclipse Runtime" [Active] org.eclipse.equinox.preferences (3.2.1.R32x_v20060717) "Eclipse Preferences Mechanism" [Active] org.eclipse.equinox.registry (3.2.1.R32x_v20060814) "Extension Registry Support" [Active] org.eclipse.help (3.2.1.R321_v20060920) "Help System Core" [Active] org.eclipse.help.appserver (3.1.100.v20060602) "Help Application Server" [Resolved] org.eclipse.help.base (3.2.1.R321_v20060822) "Help System Base" [Resolved] org.eclipse.help.ui (3.2.0.v20060602) "Help System UI" [Resolved] org.eclipse.help.webapp (3.2.1.R321_v20060803) "Help System Webapp" [Resolved] org.eclipse.jface (3.2.1.M20060908-1000) "JFace" [Resolved] org.eclipse.jface.databinding (1.0.0.I20060605-1400) "JFace Data Binding" [Resolved] org.eclipse.jface.text (3.2.1.r321_v20060810) "JFace Text" [Resolved] org.eclipse.rcp (3.2.0.v20060605) "Eclipse RCP" [Resolved] org.eclipse.sdk (3.2.1.r321_v20060705) "Eclipse Project SDK" [Installed] org.eclipse.search (3.2.1.r321_v20060726) "Search Support" [Active] org.eclipse.swt (3.2.1.v3235e) "Standard Widget Toolkit" [Resolved] org.eclipse.swt.win32.win32.x86 (3.2.1.v3235) "Standard Widget Toolkit for Windows" [Resolved] org.eclipse.text (3.2.0.v20060605-1400) "Text" [Resolved] org.eclipse.tomcat (4.1.130.v20060601) "Tomcat Wrapper" [Resolved] org.eclipse.ui (3.2.1.M20060913-0800) "Eclipse UI" [Active] org.eclipse.ui.editors (3.2.1.r321_v20060721) "Default Text Editor" [Active] org.eclipse.ui.forms (3.2.0.v20060602) "Eclipse Forms" [Active] org.eclipse.ui.ide (3.2.1.M20060915-1030) "Eclipse IDE UI" [Resolved] org.eclipse.ui.views (3.2.1.M20060906-0800) "Views" [Active] org.eclipse.ui.workbench (3.2.1.M20060906-0800) "Workbench" [Active] org.eclipse.ui.workbench.texteditor (3.2.0.v20060605-1400) "Text Editor Framework" [Active] org.eclipse.update.configurator (3.2.1.v20092006) "Install/Update Configurator" [Active] org.eclipse.update.core (3.2.1.v20092006) "Install/Update Core" [Resolved] org.eclipse.update.ui (3.2.1.v20092006) "Install/Update UI" [Resolved] system.bundle (3.2.1.R32x_v20060919) "OSGi System Bundle" [Active] User Preferences: #Mon May 07 16:00:26 CDT 2007 @org.eclipse.ui.editors=3.2.1.r321_v20060721 @org.apache.directory.ldapstudio.browser.common=0.8.0 /instance/org.eclipse.core.resources/version=1 @org.eclipse.core.resources=3.2.1.R32x_v20060914 /instance/org.eclipse.ui.editors/overviewRuler_migration=migrated_3.1 /instance/org.apache.directory.ldapstudio.browser.ui/searchResultEditorShowDn=false /instance/org.apache.directory.ldapstudio.browser.common/browserEnableFolding=false !/= /instance/org.apache.directory.ldapstudio.browser.common/templates=<?xml version\="1.0" encoding\="UTF-8"?><templates/> /instance/org.apache.directory.ldapstudio.browser.ui/searchResultEditorShowLinks=false file_export_version=3.0 /instance/org.apache.directory.ldapstudio.ldifeditor/templates=<?xml version\="1.0" encoding\="UTF-8"?><templates/> @org.apache.directory.ldapstudio.ldifeditor=0.8.0 @org.apache.directory.ldapstudio.browser.ui=0.8.0
        Hide
        Stefan Seelmann added a comment -

        Hi Matt,

        LS currently doesn't support paged search, I think we could exclude this.

        I am able to fetch 10000 entries from the server (ApacheDS or OpenLDAP), running LS on Linux.

        Have you tried to send the same search request with the same bind user using the command-line ldapsearch tool?
        Are you sure, that there are no server-side limitations, perhaps with your bind user?
        Are there any server logs?
        Could you record the request and response using Wireshark and attach the dump to this issue?

        Show
        Stefan Seelmann added a comment - Hi Matt, LS currently doesn't support paged search, I think we could exclude this. I am able to fetch 10000 entries from the server (ApacheDS or OpenLDAP), running LS on Linux. Have you tried to send the same search request with the same bind user using the command-line ldapsearch tool? Are you sure, that there are no server-side limitations, perhaps with your bind user? Are there any server logs? Could you record the request and response using Wireshark and attach the dump to this issue?
        Hide
        Emmanuel Lecharny added a comment -

        Matt,

        there is a SizeLimit you can set on the server you are using (at least, this should be possible). If the server limit is set, then you won't be able to receive more that this limit.

        Whcih server are you using ?

        Show
        Emmanuel Lecharny added a comment - Matt, there is a SizeLimit you can set on the server you are using (at least, this should be possible). If the server limit is set, then you won't be able to receive more that this limit. Whcih server are you using ?
        Hide
        Matt Green added a comment -

        I am using the Sun Directory Server 5.1 sp2. I have
        the server side setting set to 300K entries to return
        with a search time limit of 3600 seconds...

        — "Emmanuel Lecharny (JIRA)" <jira@apache.org>

        https://issues.apache.org/jira/browse/DIRSTUDIO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494142

        Show
        Matt Green added a comment - I am using the Sun Directory Server 5.1 sp2. I have the server side setting set to 300K entries to return with a search time limit of 3600 seconds... — "Emmanuel Lecharny (JIRA)" <jira@apache.org> https://issues.apache.org/jira/browse/DIRSTUDIO-95?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12494142
        Hide
        Matt Green added a comment -

        I have attached the screenshot of the directory configuration settings on the Sun directory server. The credentials (Directory Manager) work fine when used with the ldapsearch command or other ldap browsers (softerra, ldapbrowser 2.81).

        Show
        Matt Green added a comment - I have attached the screenshot of the directory configuration settings on the Sun directory server. The credentials (Directory Manager) work fine when used with the ldapsearch command or other ldap browsers (softerra, ldapbrowser 2.81).
        Hide
        Emmanuel Lecharny added a comment -

        I can seach for 1000 entries on ADS, but even if I set the server differently, this is the limit for LS.

        Stefan, any idea why I'm limited to 1K entries ?

        I'm using LS 0.8.0.

        Show
        Emmanuel Lecharny added a comment - I can seach for 1000 entries on ADS, but even if I set the server differently, this is the limit for LS. Stefan, any idea why I'm limited to 1K entries ? I'm using LS 0.8.0.
        Hide
        Matt Green added a comment -

        The Ethereal file has been uploaded as an attachment to this bug

        Show
        Matt Green added a comment - The Ethereal file has been uploaded as an attachment to this bug
        Hide
        Matt Green added a comment -

        This is the way that I have configured LS...and would think that this should be able to return 100K users. Have not been sucessful to date.

        Show
        Matt Green added a comment - This is the way that I have configured LS...and would think that this should be able to return 100K users. Have not been sucessful to date.
        Hide
        Emmanuel Lecharny added a comment -

        The log you sent us contains a 'SearchResultDone', with this message :
        "Time limit exceeded"

        I think that what is supposed to be seconds are milliseconds (3600).

        Can you try to set the timeLimit to 0 (infinite time respond) and check if you get everything ?

        Show
        Emmanuel Lecharny added a comment - The log you sent us contains a 'SearchResultDone', with this message : "Time limit exceeded" I think that what is supposed to be seconds are milliseconds (3600). Can you try to set the timeLimit to 0 (infinite time respond) and check if you get everything ?
        Hide
        Chris Custine added a comment -

        From the WireShark capture it looks like your timeLimit on the search is set to 4 seconds, so that may be limiting the returned results. The default in LDAP Studio is 0 which is infinite so somewhere you have set the time limit. I just noticed in your screenshot that your search is set to 3600 but that field is in milliseconds so it is getting rounded to 4. Try 0 and see if that returns larger results.

        Show
        Chris Custine added a comment - From the WireShark capture it looks like your timeLimit on the search is set to 4 seconds, so that may be limiting the returned results. The default in LDAP Studio is 0 which is infinite so somewhere you have set the time limit. I just noticed in your screenshot that your search is set to 3600 but that field is in milliseconds so it is getting rounded to 4. Try 0 and see if that returns larger results.
        Hide
        Stefan Seelmann added a comment -

        Chris is absolutely right. I will add a label to the limit field to indicate that the values are im milliseconds.

        @Matt:
        Sorry, but I wouldn't recommend to search that large amount of entries. All the entries and attributes are held in memory and LS will run out of memory. I am sure we could improve the memory usage, any suggestions are welcome. Imagine you get 100000 entries each with 1000 Byte of data results in 100MB data and Java Strings are double-bytes. By default LS starts with 128MB heap memory, you could increase it by appending the startup parameter "-vmargs Xmx512M". Of course it is possible to export/import such large amount of entries to/from LDIF.

        @Emmanuel:
        There are 3 stages of limits:
        1.) The default limits (countLimit 1000, timeLImit 0) currently hardcoded.
        2.) The connection specific limits. When creating a new connection the default limits are used to preset the limit parameters, of course the limits for a specific connection could be changed on the Options tab. The connection specific limits are used when browsing the DIT, Pierre had the idea to enable some kind of paged search.
        3.) The search specific limits. When creating a new search the connection specific limits are used to preset these limit parameters.
        So to get more then 1000 entries when browsing the DIT you could increase the connection limits.

        Show
        Stefan Seelmann added a comment - Chris is absolutely right. I will add a label to the limit field to indicate that the values are im milliseconds. @Matt: Sorry, but I wouldn't recommend to search that large amount of entries. All the entries and attributes are held in memory and LS will run out of memory. I am sure we could improve the memory usage, any suggestions are welcome. Imagine you get 100000 entries each with 1000 Byte of data results in 100MB data and Java Strings are double-bytes. By default LS starts with 128MB heap memory, you could increase it by appending the startup parameter "-vmargs Xmx512M". Of course it is possible to export/import such large amount of entries to/from LDIF. @Emmanuel: There are 3 stages of limits: 1.) The default limits (countLimit 1000, timeLImit 0) currently hardcoded. 2.) The connection specific limits. When creating a new connection the default limits are used to preset the limit parameters, of course the limits for a specific connection could be changed on the Options tab. The connection specific limits are used when browsing the DIT, Pierre had the idea to enable some kind of paged search. 3.) The search specific limits. When creating a new search the connection specific limits are used to preset these limit parameters. So to get more then 1000 entries when browsing the DIT you could increase the connection limits.
        Hide
        Emmanuel Lecharny added a comment -

        Thanks Stefan for the explanation.

        I would suggest that the Search screen give some informations about time limit, which is to be expressed in seconds, not in milliseconds (a SearchRequest SizeLimit is in seconds).

        I successfully loaded the 10 000 entries I'm playing with, thanks to your help !

        I don't think either that loading 300K entries in LS is reasonnable
        What would be just a good feature, however, would be to be able to show the tree structure without showing the leaves, which may result as a full scan of a DIT, without storing the result into LS, but only leaves which have children.

        Show
        Emmanuel Lecharny added a comment - Thanks Stefan for the explanation. I would suggest that the Search screen give some informations about time limit, which is to be expressed in seconds, not in milliseconds (a SearchRequest SizeLimit is in seconds). I successfully loaded the 10 000 entries I'm playing with, thanks to your help ! I don't think either that loading 300K entries in LS is reasonnable What would be just a good feature, however, would be to be able to show the tree structure without showing the leaves, which may result as a full scan of a DIT, without storing the result into LS, but only leaves which have children.
        Hide
        Matt Green added a comment -

        The LS tool is a fantastic piece of work. Can you tell me what you are targeting its user base for?
        The reason I am asking this is because 100K LDAP entries is not really that large of a request –

        The reason that I am using the LS tool is that I am searching on a filter and asking for a set of attributes returned for each entry matching the filter.
        If ldapsearch is used and the entry has all attributes then they are all returned but if the entry does not have all attributes then only the attributes present are returned.

        The LS tool is great in that even if the entry does not have the attribute present it still returns comma delimited place holder for where the missing attribute value would be for that entry.

        For example if this represents the attributes requested from ldap query "cn, givenname, sn, telephonenumber, description" on the below entries

        dn: uid=matt, ou=people, o=cc.com
        cn: matt green
        givenname: matt
        sn: green
        telephonenumber: 789.456.1234
        description: operator

        dn: uid=dave, ou=people, o=cc.com
        cn: dave green
        givenname: dave
        sn: green
        description: manager

        Your tools CSV output provide this

        "matt green", "matt", "green", "789.456.1234", "operator"
        "dave green", "dave", "green", ,"manager"

        I am trying to provide a simple tool for admins to use for data manipulation and extraction. The tool needs to be able to operate on datasets up to 250K entries and be able to output
        the results in a comma delimited/quoted format. The Softterra browser can perform on the dataset size but does not have the fantastic other qualities that LS has. Is there anything
        that can be done to enable this type of capability?

        I work with LDAP directories of all sorts in fairly large organizations and typically have to work on large number of entries at a time which usually end up having to construct a
        combination of shell and native ldap commands that take alot of time to construct. If the intent of LS is to be a tool to be used by main stream LDAP engineers it would seem
        reasonable to architect this ability into this great product. I do realize that this is a .8 version so please take this as a recommendation for future direction. In the meantime it looks like I
        have to go back to ldapsearch, grep, awk and sed land

        Thanks again to all for your prompt resonse to my questions – matt

        Show
        Matt Green added a comment - The LS tool is a fantastic piece of work. Can you tell me what you are targeting its user base for? The reason I am asking this is because 100K LDAP entries is not really that large of a request – The reason that I am using the LS tool is that I am searching on a filter and asking for a set of attributes returned for each entry matching the filter. If ldapsearch is used and the entry has all attributes then they are all returned but if the entry does not have all attributes then only the attributes present are returned. The LS tool is great in that even if the entry does not have the attribute present it still returns comma delimited place holder for where the missing attribute value would be for that entry. For example if this represents the attributes requested from ldap query "cn, givenname, sn, telephonenumber, description" on the below entries dn: uid=matt, ou=people, o=cc.com cn: matt green givenname: matt sn: green telephonenumber: 789.456.1234 description: operator dn: uid=dave, ou=people, o=cc.com cn: dave green givenname: dave sn: green description: manager Your tools CSV output provide this "matt green", "matt", "green", "789.456.1234", "operator" "dave green", "dave", "green", ,"manager" I am trying to provide a simple tool for admins to use for data manipulation and extraction. The tool needs to be able to operate on datasets up to 250K entries and be able to output the results in a comma delimited/quoted format. The Softterra browser can perform on the dataset size but does not have the fantastic other qualities that LS has. Is there anything that can be done to enable this type of capability? I work with LDAP directories of all sorts in fairly large organizations and typically have to work on large number of entries at a time which usually end up having to construct a combination of shell and native ldap commands that take alot of time to construct. If the intent of LS is to be a tool to be used by main stream LDAP engineers it would seem reasonable to architect this ability into this great product. I do realize that this is a .8 version so please take this as a recommendation for future direction. In the meantime it looks like I have to go back to ldapsearch, grep, awk and sed land Thanks again to all for your prompt resonse to my questions – matt
        Hide
        Stefan Seelmann added a comment -

        If you directly invoke the "Export LDIF" or "Export CSV" from the Connections view or the Browser view it is possible to export all the entries of your directory to LDIF or CSV.
        In that case they are directly streamed from the directory to the file and are not held in memory.

        However loading all the entries into LS to manipulate them manually isn't possible atm. Perhaps we could think about it later. It would require a big architecture change to make that possible.

        Another feature would be the "Batch Operation". You could select entries with an filter and then you define modifications on that entries.
        Till now it is an expermental tool, only some simple operations (add/delete/replace attribute) could be performed and it generates just an LDIF.
        Later we would add some advanced (perhaps script based) modification operations and it should be possible to perform this modifications directly.
        In that case it should be possible to manipulate 300k of entries. Perhaps you could define some examples of data manipulation operations you need?

        Show
        Stefan Seelmann added a comment - If you directly invoke the "Export LDIF" or "Export CSV" from the Connections view or the Browser view it is possible to export all the entries of your directory to LDIF or CSV. In that case they are directly streamed from the directory to the file and are not held in memory. However loading all the entries into LS to manipulate them manually isn't possible atm. Perhaps we could think about it later. It would require a big architecture change to make that possible. Another feature would be the "Batch Operation". You could select entries with an filter and then you define modifications on that entries. Till now it is an expermental tool, only some simple operations (add/delete/replace attribute) could be performed and it generates just an LDIF. Later we would add some advanced (perhaps script based) modification operations and it should be possible to perform this modifications directly. In that case it should be possible to manipulate 300k of entries. Perhaps you could define some examples of data manipulation operations you need?
        Hide
        Stefan Seelmann added a comment -

        I corrected the timelimit option (use seconds instead of milliseconds) as suggested by Emmanuel here: http://svn.apache.org/viewvc?rev=615634&view=rev

        @Matt:
        There wasn't more feedback from you, I will close this issue.

        It is not possible to load hundred-thousands of records into Studio. There are restictions in Java, Eclipse and the Studio architecture. However it is possible to do a direct CSV-Export.

        Show
        Stefan Seelmann added a comment - I corrected the timelimit option (use seconds instead of milliseconds) as suggested by Emmanuel here: http://svn.apache.org/viewvc?rev=615634&view=rev @Matt: There wasn't more feedback from you, I will close this issue. It is not possible to load hundred-thousands of records into Studio. There are restictions in Java, Eclipse and the Studio architecture. However it is possible to do a direct CSV-Export.
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Closing this issue.

        Show
        Pierre-Arnaud Marcelot added a comment - Closing this issue.

          People

          • Assignee:
            Stefan Seelmann
            Reporter:
            Matt Green
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development