Hi Alan,
It may be that your jvm ran out of memory - you could try using
the batch script to start and setting arguments to the jvm such as:
-Xmx512m -Xms256m
to increase the default allocation of memory when you start your jvm
(mx is max, ms is min)
... I have to say that jxplorer is *not* a good tool to use for large
data sets at a single level; once you get over a couple of thousand
entries displayed, the java 'swing' tree component really starts to
grind...
- Chris
On 27/08/2005, at 5:41 AM, Alan Batie wrote:
Hi; I just found jxplorer, and it's great! (and this from a died-in-
the-wool command line user ;-) ).
But...
We have a 22000+ entry ldap database, and when it's loading it in
the Explore section on connection, it gets about halfway through
and croaks:
Search partially failed! - only 12,491 entries returned
javax.naming.CommunicationException: connection closed [Root
exception is java.io.IOException: connection closed]
(the server process stays running, so it's not crashing ---
openldap 2.2.27)
at com.sun.jndi.ldap.LdapCtx.getSearchReply(LdapCtx.java:1883)
at com.sun.jndi.ldap.LdapNamingEnumeration.getNextBatch
(LdapNamingEnumeration.java:110)
at com.sun.jndi.ldap.LdapNamingEnumeration.hasMoreImpl
(LdapNamingEnumeration.java:197)
at com.sun.jndi.ldap.LdapNamingEnumeration.hasMore
(LdapNamingEnumeration.java:170)
at com.ca.commons.naming.DXOps.postParseNameClassPairs
(DXOps.java:170)
at com.ca.commons.naming.DXOps.rawSearchOneLevel(DXOps.java:254)
at com.ca.commons.jndi.JNDIOps.list(JNDIOps.java:737)
at com.ca.directory.jxplorer.broker.JNDIBroker.unthreadedList
(JNDIBroker.java:728)
at com.ca.directory.jxplorer.broker.Broker.doListQuery
(Broker.java:388)
at com.ca.directory.jxplorer.broker.Broker.processRequest
(Broker.java:202)
at com.ca.directory.jxplorer.broker.JNDIBroker.processRequest
(JNDIBroker.java:360)
at com.ca.directory.jxplorer.broker.Broker.processQueue
(Broker.java:158)
at com.ca.directory.jxplorer.broker.JNDIBroker.processQueue
(JNDIBroker.java:877)
at com.ca.directory.jxplorer.broker.Broker.run(Broker.java:124)
at java.lang.Thread.run(Thread.java:552)
Caused by: java.io.IOException: connection closed
at com.sun.jndi.ldap.LdapClient.ensureOpen(LdapClient.java:1648)
at com.sun.jndi.ldap.LdapClient.getSearchReply(LdapClient.java:
661)
at com.sun.jndi.ldap.LdapCtx.getSearchReply(LdapCtx.java:1881)
... 14 more
--
NOTE TO OUTLOOK USERS: Some versions of Outlook have a bug in
dealing with digitally signed email like the one you're now reading:
when replying, before clicking Send, go to the Tools menu and make
sure that "Digitally Sign" is not checked (unless you actually
have a digital certificate, but most people don't yet --- see
https://www.thawte.com/email/ for information on getting one and
why you should. Feel free to ask me for help!).
Alan Batie - Peak System Administrator
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Jxplorer-users mailing list
Jxplorer-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jxplorer-users
