Bugs item #888967, was opened at 2004-02-02 02:25
Message generated for change (Comment added) made by pegacat
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=480577&aid=888967&group_id=55394
Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Rejected
Priority: 5
Private: No
Submitted By: Marco Schirrmeister (mschirrmeister)
>Assigned to: Christopher Betts (pegacat)
Summary: expand large tree
Initial Comment:
Hi
When i expand my ou people with roughly 11000 entrys a
following error appaers.
"Search partially failed! - only 8074 entries returned."
After this, the progam hangs with "reading....", also
on the other ou's. Then i must reconnect.
Both searchlimits in jxplorer are that to 0.
In slapd.conf is the sizelimit set to 20000
--
Marco
----------------------------------------------------------------------
>Comment By: Christopher Betts (pegacat)
Date: 2012-01-03 03:44
Message:
Hi Folks,
I think there are two problems here; the first is a server error of
some sort (that's the 'Search partially failed' message, which comes from
the server).
The second may well be a memory problem; JX isn't great at large data
sets. However on current machines in 2012, 20,000 entries should be fine.
- Chris
----------------------------------------------------------------------
Comment By: Marcel Ritter (sfmarcel)
Date: 2005-04-26 12:35
Message:
Logged In: YES
user_id=321290
Hi there!
I had the same problem when browsing my LDAP directory with
~20000 entries. However the problem seems to be only
partially JXplorers fault:
I increased the maximum memory available to the java virtual
machine, and suddenly all users appeared in the browser! If
you wonder how to do this:
I just added the option "-Xmx256m" to the java call (to make
256M available to JVM - I'm running this on Linux but I
guess there a similar option to any JVM)
The default - according to the manual pages is 64M, which
may be a little low in some situations.
Perhaps the JXplorer developers could have a look at how to
decrease
the memory footprint?
Bye,
Marcel
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=480577&aid=888967&group_id=55394
------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create
new or port existing apps to sell to consumers worldwide. Explore the
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Jxplorer-devel mailing list
Jxplorer-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jxplorer-devel
