RE: [Exist-open] Maximum documents in a collection

[Tom S. <to...@ep...>]

Hi Sunny, etc,

Thanks for your suggestion. I'm running the stand-alone server with the RPC
listener on port 8012. I'm sure no other processes are using this port.
However, I have noticed something strange. If I run my client to add only 10
documents to the collection, then use netstat to display current network
connection, the output includes:

  Proto  Local Address          Foreign Address        State
  TCP    HEULANDITE:1406        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:1407        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:1409        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:1410        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:1412        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:1415        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:1419        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:1420        localhost:8012         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1408         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1411         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1413         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1414         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1416         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1417         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1418         TIME_WAIT
  TCP    HEULANDITE:8012        localhost:1421         TIME_WAIT

So it looks like a large number of different connections are being used to
add the documents. After a wait of a few minutes, the connections clean
themselves up. Perhaps when I try to add 3,000 documents, there is an
attempt to open 3,000 different connections simultaneously, and something is
overloaded?

Here is the fragment of code I am using to add the documents, where "child"
is the open Collection:

    for ( int i = 1; i <= size; i++ )
    {
        String resourceID = String.valueOf(i);
        String content = makeDocument(i);
        XMLResource document = (XMLResource) 
            child.createResource(resourceID, "XMLResource");
	  document.setContent(content);
	  child.storeResource(document);
    }

Am I do something wrong that is causing too many connections to be
established with the eXist server?

Many thanks,

Tom Sugdem


-----Original Message-----
From: Sunny Das, Noida [mailto:su...@no...] 
Sent: 15 December 2004 12:41
To: Tom Sugden
Subject: RE: [Exist-open] Maximum documents in a collection

Are u sure no other process is using the port .

"  eht dlrow smees os hcum eht retteb morf ereh! "
-----Original Message-----
From: exi...@li...
[mailto:exi...@li...] On Behalf Of Tom Sugden
Sent: Wednesday, December 15, 2004 5:58 PM
To: exi...@li...
Subject: [Exist-open] Maximum documents in a collection

Hello,

Is there a maximum number of documents that eXist can contain within a
single collection?

I have written a simple Java client to create a new collection and populate
it with documents. The documents are small and of the form shown below:

  <entry id="1">
    <name>Ally Antonioletti</name>
    <address>826 Hume Crescent, Southampton</address>
    <phone>01670061244</phone>
  </entry>

The client is able to add 2,500 documents to a single collection without any
problem. However, if I try to increase this number of documents to 3,000,
the client fails with the following exception:

    org.xmldb.api.base.XMLDBException
	 
       Error code    : 1
       Message string: Address already in use: connect
       Explanation   : A vendor specific error has occurred.

     org.xmldb.api.base.XMLDBException: Address already in use: connect
	at org.exist.xmldb.RemoteCollection.store(RemoteCollection.java:424)
	at
org.exist.xmldb.RemoteCollection.storeResource(RemoteCollection.java:407)
	at CreateTestXMLDB.populateDatabase(CreateTestXMLDB.java:127)
	... 4 more
     Caused by: java.io.IOException: Address already in use: connect
	at
org.apache.xmlrpc.XmlRpcClient$Worker.execute(XmlRpcClient.java:444)
	at org.apache.xmlrpc.XmlRpcClient.execute(XmlRpcClient.java:163)
	at org.exist.xmldb.RemoteCollection.store(RemoteCollection.java:417)
	... 6 more

I am using eXist 1.0 Beta 2 with Java 1.4.2_04, and am running it in
stand-alone mode as recommended in the documentation. Is this a known
limitation of eXist or is it likely that I am doing something wrong?

Thank you,

Tom Sugden



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide Read honest & candid reviews
on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Exist-open mailing list
Exi...@li...
https://lists.sourceforge.net/lists/listinfo/exist-open