java version "1.7.0_11"

Java(TM) SE Runtime Environment (build 1.7.0_11-b21)

Java HotSpot(TM) 64-Bit Server VM (build 23.6-b04, mixed mode)

I spent too much time on this, I gave up. I'll ask the question 
differently, I wanted to use the transport client at 9300 so I can index a 
file, and the intent to search it with http://localhost:9300/_search...for 
demo purposes since I didn't want to search it using java code. I am able 
to index the file with nodeBuilder, is there a way I can query it using 
http? My understanding is that the node is local, can I query it somehow 
over http?

On Wednesday, January 22, 2014 10:02:14 PM UTC-5, Ross Simpson wrote:
>
> java -version will tell you the exact version, patch level, vendor, and 
> architecture of that JVM.  The tricky bit can be finding out which JVM 
> you're actually using (usually the value in $JAVA_HOME or `which java`will 
> lead you in the right direction).  If you're running your example 
> under an IDE, it might well be using a different JVM than the ES server.
>
> I've had similar troubles to what you describe, but not on the localhost. 
>  Do you get the exception right away, or some time after starting up your 
> client?
>
> Ross
>
>
> On Thursday, 23 January 2014 10:34:40 UTC+11, ZenMaster80 wrote:
>>
>> Yes, I do have 0.90.9 across the board.
>> I know 9300 is opened.
>> I am not sure how to check if both are using same JVM?
>> es.yml is default, default clustername, nodename .. I only have the 
>> default (1 Node)... Do I need to specify unicast instead of the default 
>> which I believe uses multiCast?
>>
>> On Wednesday, January 22, 2014 3:25:26 PM UTC-5, Jörg Prante wrote:
>>>
>>> You wrote that you have a 0.90.9 cluster but you added 0.90.0 jars to 
>>> the client. Is that correct?
>>>
>>> Please check:
>>>
>>> - if your cluster nodes and client node is using exactly the same JVM
>>>
>>> - if your cluster and client use exactly the same ES version 
>>>
>>> - if your cluster and client use the same cluster name
>>>
>>> - reasons outside ES: IP blocking, network reachability, network 
>>> interfaces, IPv4/IPv6 etc.
>>>
>>> Then you should be able to connect with TransportClient.
>>>
>>> Jörg
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/15445d05-937e-45ce-800b-d57f82bf2af9%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to