I wish I could just go back and edit prior postings. :-)
... I should mention, if I do the above, but don't create 2 threads - that
is, synchronously index each item, close the TransportClient, create
another TransportClient and do the search, it works. So this is ONLY
happening when the two a
Final bit of info, and this seems important; one TransportClient is being
run in one thread, the other in another... so it goes like this:
Thread 1: Fork Thread 1
Thread 2: Create new TransportClient; Index list of items, not waiting for
Future objects (i.e. not calling actionGet())
Thread 1: Wh
I made a mistake in my statement above - I am using different
TransportClients for the indexing and the searching... so, one is doing the
indexing, and while that is going on, I'm doing the searching on a
different one.
- Tim
>
--
You received this message because you are subscribed to the
I have a situation where, using the Java API, I initiate a bunch of
indexing operations, but throw away the Future object (I don't need the
return status). This is so I can do a lot of indexing reasonably
asynchronously, so I don't have to hold up the GUI that triggers these
calls.
However, i
