Thank a lot, Alex. You saved my day :) .
On Wed, Jul 3, 2019 at 12:14 AM Alex Plehanov
wrote:
> Hello,
>
> There was a bug [1] with one node thin client configuration, which is
> fixed now but was not released yet.
> You can try to add one more server address (the same address) as a
>
Hello,
There was a bug [1] with one node thin client configuration, which is fixed
now but was not released yet.
You can try to add one more server address (the same address) as a
workaround. For example:
ClientConfiguration cfg = new
ClientConfiguration().setAddresses(hostName + ":" +
I am having similar problem: I am testing with a one-node-cluster. After
restart the Ignite cluster(server), Java thin client is not reconnecting.
There is no port change on server for my case since I defined client port
in the Ignite configuration:
Hello, Rick
There should be a message in the server log:
"Client connector processor has started on TCP port x" with "INFO"
level.
пн, 1 июл. 2019 г. в 10:26, rick_tem :
> Thanks for your response. I tried 10801 and it failed. My question is how
> do I find out which port it is using?
>
>
Thanks for your response. I tried 10801 and it failed. My question is how
do I find out which port it is using?
Thanks,
Rick
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Well, it seems like you start two nodes on the same host, and as first
node occupies default thin client port (10800) the second node takes
the next one (10801).
I believe you use 127.0.0.1 or something like this for your thin client
host lists which effectively means 127.0.0.1:10800. So, your
Hi,
I am seeing that a thin client cannot reconnect (on the same port) after a
server shutdown. I have 1 backup enabled and load some data in the cache on
startup. Replication procedure is:
1) Start server 1
2) Try thin client --> it retrieves data
3) Start server 2
4) Kill server 1 (Server 2
