Re: ThinClient connection refused / disconnect
Thanks for confirmation! On Sat, Jul 2, 2022 at 3:32 PM wrote: > Fixed it. It was indeed a wrongly configured IP address! > > > On 15.06.22 22:29, don.tequ...@gmx.de wrote: > > Both server node and thin client are on the same computer, each running in > a separate Docker container with network „host“. CPU load does not seem to > be an issue and other server nodes on the same computer and from other > computers connect to the cluster just fine without such connection issues. > > I‘ll check the server logs more thoroughly. > > > > > On 15.06.22 at 21:14, Pavel Tupitsyn wrote: > > From: "Pavel Tupitsyn" > Date: 15. June 2022 > To: "user" > Cc: > Subject: Re: ThinClient connection refused / disconnect > Idle timeout is disabled by default. > > Regarding connection issues, either the server is overloaded and can't > accept connections, or there are network issues. > 1. Check if the network between client and server is reliable enough > (measure speed, check packet loss) > 2. Check server logs and resource utilization > > On Wed, Jun 15, 2022 at 5:47 PM wrote: > >> Hi, >> >> I'm experiencing a connection issue when using Java ThinClient at the >> customer site. It is using Ignite 2.13. >> >> From time to time it happens that the ThinClient cannot connect at >> startup and gets a "connection refused". After several tries it >> connects, but frequently is "loses" connection again and all further >> attempts to use the ignite client instance lead to connection refused >> again. Then after some time it connects again. >> >> at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) >> at >> java.base/sun.nio.ch >> .SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) >> at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) >> at >> >> org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) >> ... 25 common frames omitted >> Suppressed: org.apache.ignite.client.ClientConnectionException: >> Connection refused >> ... 26 common frames omitted >> Caused by: java.net.ConnectException: Connection refused >> at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) >> at >> java.base/sun.nio.ch >> .SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) >> at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) >> at >> >> org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) >> >> I can see there is a idle time out but I'm not setting this. So I assume >> the default value 0 means that no timeout should happen? >> >> >> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#DFLT_IDLE_TIMEOUT >> >> Thanks! >> >> >>
Re: ThinClient connection refused / disconnect
Fixed it. It was indeed a wrongly configured IP address!
On 15.06.22 22:29, don.tequ...@gmx.de wrote:
Both server node and thin client are on the same computer, each
running in a separate Docker container with network „host“. CPU load
does not seem to be an issue and other server nodes on the same
computer and from other computers connect to the cluster just fine
without such connection issues.
I‘ll check the server logs more thoroughly.
On 15.06.22 at 21:14, Pavel Tupitsyn wrote:
From: "Pavel Tupitsyn"
Date: 15. June 2022
To: "user"
Cc:
Subject: Re: ThinClient connection refused / disconnect
Idle timeout is disabled by default.
Regarding connection issues, either the server is overloaded and can't
accept connections, or there are network issues.
1. Check if the network between client and server is reliable enough
(measure speed, check packet loss)
2. Check server logs and resource utilization
On Wed, Jun 15, 2022 at 5:47 PM wrote:
Hi,
I'm experiencing a connection issue when using Java ThinClient at the
customer site. It is using Ignite 2.13.
From time to time it happens that the ThinClient cannot connect at
startup and gets a "connection refused". After several tries it
connects, but frequently is "loses" connection again and all further
attempts to use the ignite client instance lead to connection refused
again. Then after some time it connects again.
at java.base/sun.nio.ch
<http://sun.nio.ch>.SocketChannelImpl.checkConnect(Native Method)
at
java.base/sun.nio.ch
<http://sun.nio.ch>.SocketChannelImpl.finishConnect(SocketChannelImpl.java:774)
at java.base/sun.nio.ch
<http://sun.nio.ch>.SocketAdaptor.connect(SocketAdaptor.java:120)
at
org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125)
... 25 common frames omitted
Suppressed: org.apache.ignite.client.ClientConnectionException:
Connection refused
... 26 common frames omitted
Caused by: java.net.ConnectException: Connection refused
at java.base/sun.nio.ch
<http://sun.nio.ch>.SocketChannelImpl.checkConnect(Native Method)
at
java.base/sun.nio.ch
<http://sun.nio.ch>.SocketChannelImpl.finishConnect(SocketChannelImpl.java:774)
at java.base/sun.nio.ch
<http://sun.nio.ch>.SocketAdaptor.connect(SocketAdaptor.java:120)
at
org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125)
I can see there is a idle time out but I'm not setting this. So I
assume
the default value 0 means that no timeout should happen?
https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#DFLT_IDLE_TIMEOUT
Thanks!
Re: Re: ThinClient connection refused / disconnect
Both server node and thin client are on the same computer, each running in a separate Docker container with network „host“. CPU load does not seem to be an issue and other server nodes on the same computer and from other computers connect to the cluster just fine without such connection issues.I‘ll check the server logs more thoroughly.On 15.06.22 at 21:14, Pavel Tupitsyn wrote: From: "Pavel Tupitsyn" Date: 15. June 2022To: "user" Cc: Subject: Re: ThinClient connection refused / disconnect Idle timeout is disabled by default. Regarding connection issues, either the server is overloaded and can't accept connections, or there are network issues. 1. Check if the network between client and server is reliable enough (measure speed, check packet loss) 2. Check server logs and resource utilization On Wed, Jun 15, 2022 at 5:47 PM <don.tequ...@gmx.de> wrote: Hi, I'm experiencing a connection issue when using Java ThinClient at the customer site. It is using Ignite 2.13. From time to time it happens that the ThinClient cannot connect at startup and gets a "connection refused". After several tries it connects, but frequently is "loses" connection again and all further attempts to use the ignite client instance lead to connection refused again. Then after some time it connects again. at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) at org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) ... 25 common frames omitted Suppressed: org.apache.ignite.client.ClientConnectionException: Connection refused ... 26 common frames omitted Caused by: java.net.ConnectException: Connection refused at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) at org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) I can see there is a idle time out but I'm not setting this. So I assume the default value 0 means that no timeout should happen? https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#DFLT_IDLE_TIMEOUT Thanks!
Re: ThinClient connection refused / disconnect
Idle timeout is disabled by default. Regarding connection issues, either the server is overloaded and can't accept connections, or there are network issues. 1. Check if the network between client and server is reliable enough (measure speed, check packet loss) 2. Check server logs and resource utilization On Wed, Jun 15, 2022 at 5:47 PM wrote: > Hi, > > I'm experiencing a connection issue when using Java ThinClient at the > customer site. It is using Ignite 2.13. > > From time to time it happens that the ThinClient cannot connect at > startup and gets a "connection refused". After several tries it > connects, but frequently is "loses" connection again and all further > attempts to use the ignite client instance lead to connection refused > again. Then after some time it connects again. > > at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at > java.base/sun.nio.ch > .SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) > at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) > at > > org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) > ... 25 common frames omitted > Suppressed: org.apache.ignite.client.ClientConnectionException: > Connection refused > ... 26 common frames omitted > Caused by: java.net.ConnectException: Connection refused > at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) > at > java.base/sun.nio.ch > .SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) > at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) > at > > org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) > > I can see there is a idle time out but I'm not setting this. So I assume > the default value 0 means that no timeout should happen? > > > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#DFLT_IDLE_TIMEOUT > > Thanks! > > >
ThinClient connection refused / disconnect
Hi, I'm experiencing a connection issue when using Java ThinClient at the customer site. It is using Ignite 2.13. From time to time it happens that the ThinClient cannot connect at startup and gets a "connection refused". After several tries it connects, but frequently is "loses" connection again and all further attempts to use the ignite client instance lead to connection refused again. Then after some time it connects again. at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) at org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) ... 25 common frames omitted Suppressed: org.apache.ignite.client.ClientConnectionException: Connection refused ... 26 common frames omitted Caused by: java.net.ConnectException: Connection refused at java.base/sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) at java.base/sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:774) at java.base/sun.nio.ch.SocketAdaptor.connect(SocketAdaptor.java:120) at org.apache.ignite.internal.client.thin.io.gridnioserver.GridNioClientConnectionMultiplexer.open(GridNioClientConnectionMultiplexer.java:125) I can see there is a idle time out but I'm not setting this. So I assume the default value 0 means that no timeout should happen? https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/configuration/ClientConnectorConfiguration.html#DFLT_IDLE_TIMEOUT Thanks!
Re: connection refused
Hello! This is HTTP connection. Ignite does not use HTTP between servers and clients (thin and thick). The only relevant place where HTTP is used with Ignite is REST API. Can you show the method in the trace? at com.zetcode.restex.JerseyClient2.main (JerseyClient2.java:25) Regards, -- Ilya Kasnacheev вт, 2 июн. 2020 г. в 22:19, Clay Teahouse : > Thanks Wesley, Alex. Attached is a snapshot of the client log. I don't see > anything on the ignite server side. > I am/was trying to do get data from a replicated cache. > > On Tue, Jun 2, 2020 at 10:36 AM Alexandr Shapkin > wrote: > >> Hi, >> >> >> >> As Wesley mentioned, It’s quite difficult to say something specific about >> without the logs. >> >> >> >> As for the additional questions, can you explain, what Ignite API is >> being used? Is it a Compute API call or >> >> a regular cache GETs? >> >> >> >> It’s totally fine to spawn several user threads and access the server >> simultaneously. >> >> Regarding the node connectivity, by default there is a 1 connection per >> node, you can control it >> >> using the TcpCommunicationSpi#setConnectionsPerNode [1] >> >> >> >> You can check the pool and adjust the sizes using the following docs [2]. >> >> If you perform much compute API calls, you might be interested in >> increasing the server public pool size, >> >> striped pool for cache accesses and so on. >> >> >> >> In any case, it’s better to check your system resources utilization >> (CPU/memory/etc) if it’s about 100% on a client >> >> and 20% on a server, you might want to add several more clients to a >> cluster. >> >> >> >> [1] - >> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setConnectionsPerNode-int- >> >> >> >> [2] - https://apacheignite.readme.io/docs/thread-pools >> >> >> >> >> >> *From: *Clay Teahouse >> *Sent: *Tuesday, June 2, 2020 5:20 PM >> *To: *user@ignite.apache.org >> *Subject: *Re: connection refused >> >> >> >> It turned out if I inject a pause of 4-5 seconds, then the client >> connection goes through. >> >> Why the service grid requests go through immediately but the regular >> cache access requires a pause from the time an ignite instance is acquired? >> Subsequent calls are fast. The caches are replicated. >> >> Another question, probably trivial: >> >> Can you instantiate multiple concurrent connections from a client to the >> compute nodes? Is the number of connections limited by the number of >> threads? Or do I need to create separate client instances for each request? >> >> >> >> >> >> On Tue, Jun 2, 2020 at 5:46 AM Wesley Peng >> wrote: >> >> Does either client or server have any logs? >> >> >> >> Thanks >> >> >> >> On Tue, Jun 2, 2020 at 6:37 PM Clay Teahouse >> wrote: >> >> I'd appreciate your help with this issue. >> >> I have a server and a client node, the latter running in tomcat. I get >> connection refused if I try to connect to the server node from the client, >> although the server shows the client has joined the cluster. I don't have a >> problem running a service on the server's service grid from the client node. >> >> I don't have any issue connecting from any client anywhere, if the client >> is not running in tomcat. >> >> what could be the problem? >> >> >> >> >> >
Re: connection refused
Thanks Wesley, Alex. Attached is a snapshot of the client log. I don't see anything on the ignite server side. I am/was trying to do get data from a replicated cache. On Tue, Jun 2, 2020 at 10:36 AM Alexandr Shapkin wrote: > Hi, > > > > As Wesley mentioned, It’s quite difficult to say something specific about > without the logs. > > > > As for the additional questions, can you explain, what Ignite API is being > used? Is it a Compute API call or > > a regular cache GETs? > > > > It’s totally fine to spawn several user threads and access the server > simultaneously. > > Regarding the node connectivity, by default there is a 1 connection per > node, you can control it > > using the TcpCommunicationSpi#setConnectionsPerNode [1] > > > > You can check the pool and adjust the sizes using the following docs [2]. > > If you perform much compute API calls, you might be interested in > increasing the server public pool size, > > striped pool for cache accesses and so on. > > > > In any case, it’s better to check your system resources utilization > (CPU/memory/etc) if it’s about 100% on a client > > and 20% on a server, you might want to add several more clients to a > cluster. > > > > [1] - > https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setConnectionsPerNode-int- > > > > [2] - https://apacheignite.readme.io/docs/thread-pools > > > > > > *From: *Clay Teahouse > *Sent: *Tuesday, June 2, 2020 5:20 PM > *To: *user@ignite.apache.org > *Subject: *Re: connection refused > > > > It turned out if I inject a pause of 4-5 seconds, then the client > connection goes through. > > Why the service grid requests go through immediately but the regular > cache access requires a pause from the time an ignite instance is acquired? > Subsequent calls are fast. The caches are replicated. > > Another question, probably trivial: > > Can you instantiate multiple concurrent connections from a client to the > compute nodes? Is the number of connections limited by the number of > threads? Or do I need to create separate client instances for each request? > > > > > > On Tue, Jun 2, 2020 at 5:46 AM Wesley Peng wrote: > > Does either client or server have any logs? > > > > Thanks > > > > On Tue, Jun 2, 2020 at 6:37 PM Clay Teahouse > wrote: > > I'd appreciate your help with this issue. > > I have a server and a client node, the latter running in tomcat. I get > connection refused if I try to connect to the server node from the client, > although the server shows the client has joined the cluster. I don't have a > problem running a service on the server's service grid from the client node. > > I don't have any issue connecting from any client anywhere, if the client > is not running in tomcat. > > what could be the problem? > > > > > log2 Description: Binary data
RE: connection refused
Hi, As Wesley mentioned, It’s quite difficult to say something specific about without the logs. As for the additional questions, can you explain, what Ignite API is being used? Is it a Compute API call or a regular cache GETs? It’s totally fine to spawn several user threads and access the server simultaneously.Regarding the node connectivity, by default there is a 1 connection per node, you can control it using the TcpCommunicationSpi#setConnectionsPerNode [1] You can check the pool and adjust the sizes using the following docs [2].If you perform much compute API calls, you might be interested in increasing the server public pool size, striped pool for cache accesses and so on. In any case, it’s better to check your system resources utilization (CPU/memory/etc) if it’s about 100% on a client and 20% on a server, you might want to add several more clients to a cluster. [1] - https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/spi/communication/tcp/TcpCommunicationSpi.html#setConnectionsPerNode-int- [2] - https://apacheignite.readme.io/docs/thread-pools From: Clay TeahouseSent: Tuesday, June 2, 2020 5:20 PMTo: user@ignite.apache.orgSubject: Re: connection refused It turned out if I inject a pause of 4-5 seconds, then the client connection goes through.Why the service grid requests go through immediately but the regular cache access requires a pause from the time an ignite instance is acquired? Subsequent calls are fast. The caches are replicated.Another question, probably trivial:Can you instantiate multiple concurrent connections from a client to the compute nodes? Is the number of connections limited by the number of threads? Or do I need to create separate client instances for each request? On Tue, Jun 2, 2020 at 5:46 AM Wesley Peng <westley.p...@gmail.com> wrote:Does either client or server have any logs? Thanks On Tue, Jun 2, 2020 at 6:37 PM Clay Teahouse <clayteaho...@gmail.com> wrote:I'd appreciate your help with this issue.I have a server and a client node, the latter running in tomcat. I get connection refused if I try to connect to the server node from the client, although the server shows the client has joined the cluster. I don't have a problem running a service on the server's service grid from the client node.I don't have any issue connecting from any client anywhere, if the client is not running in tomcat.what could be the problem?
Re: connection refused
It turned out if I inject a pause of 4-5 seconds, then the client connection goes through. Why the service grid requests go through immediately but the regular cache access requires a pause from the time an ignite instance is acquired? Subsequent calls are fast. The caches are replicated. Another question, probably trivial: Can you instantiate multiple concurrent connections from a client to the compute nodes? Is the number of connections limited by the number of threads? Or do I need to create separate client instances for each request? On Tue, Jun 2, 2020 at 5:46 AM Wesley Peng wrote: > Does either client or server have any logs? > > Thanks > > On Tue, Jun 2, 2020 at 6:37 PM Clay Teahouse > wrote: > >> I'd appreciate your help with this issue. >> I have a server and a client node, the latter running in tomcat. I get >> connection refused if I try to connect to the server node from the client, >> although the server shows the client has joined the cluster. I don't have a >> problem running a service on the server's service grid from the client node. >> I don't have any issue connecting from any client anywhere, if the client >> is not running in tomcat. >> what could be the problem? >> >>
Re: connection refused
Does either client or server have any logs? Thanks On Tue, Jun 2, 2020 at 6:37 PM Clay Teahouse wrote: > I'd appreciate your help with this issue. > I have a server and a client node, the latter running in tomcat. I get > connection refused if I try to connect to the server node from the client, > although the server shows the client has joined the cluster. I don't have a > problem running a service on the server's service grid from the client node. > I don't have any issue connecting from any client anywhere, if the client > is not running in tomcat. > what could be the problem? > >
connection refused
I'd appreciate your help with this issue. I have a server and a client node, the latter running in tomcat. I get connection refused if I try to connect to the server node from the client, although the server shows the client has joined the cluster. I don't have a problem running a service on the server's service grid from the client node. I don't have any issue connecting from any client anywhere, if the client is not running in tomcat. what could be the problem?
Re: Connection Refused in Scala Ignite Client (Help!)
worked like a charm, thank you.
On Thu, Oct 17, 2019 at 2:54 AM Artem Budnikov
wrote:
> Hi,
>
> Looks like you are trying to connect to the wrong port. The default port
> for client connection is 10800.
>
> Change:
>
> val cfg2 = new ClientConfiguration().setAddresses("100.25.173.220:47100
> ..47700")
>
> to
>
> val cfg2 = new ClientConfiguration().setAddresses("100.25.173.220:10800")
>
>
> -Artem
> On 17.10.2019 03:39, alexanderko...@gmail.com wrote:
>
> You need to replace the ip finder on all nodes to use the s3 one.
>
> add the libraries from libs/optional/ignite-aws to your application's
> classpath.
>
> No file is required.
>
>
>
> *From:* sri hari kali charan Tummala
>
> *Sent:* Wednesday, October 16, 2019 8:10 PM
> *To:* user@ignite.apache.org; alexanderko...@gmail.com
> *Subject:* Re: Connection Refused in Scala Ignite Client (Help!)
>
>
>
> I this below property is while launching ignite on aws
>
> I already have ignite cluster running I just need to connect using java or
> Scala code which is failing with connection refused error.
>
>
>
> https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
>
>
>
>
>
>
>
> On Wednesday, October 16, 2019, sri hari kali charan Tummala <
> kali.tumm...@gmail.com> wrote:
>
> Do I need to keep any file inside the s3 bucket or is it just a empty
> bucket ? With aws credentials and bucket name ?
>
>
>
>
>
> On Wednesday, October 16, 2019, wrote:
>
> Hi,
>
>Try using the S3 IP Finder:
> https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
>
>
>
>
>
>
>
>
>
> "org.apache.ignite.spi.discovery.tcp.ipfinder.s3.TcpDiscoveryS3IpFinder">
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks, Alex
>
>
>
>
>
> *From:* sri hari kali charan Tummala
> *Sent:* Wednesday, October 16, 2019 5:55 PM
> *To:* user@ignite.apache.org
> *Subject:* Connection Refused in Scala Ignite Client (Help!)
>
>
>
> Hi All,
>
>
>
> I am trying to connect my ignite cluster which is created on AWS (), now I
> am suing scala code to connect to the client which is failing with
> connection refused error.
>
>
>
> In my security group I opened all the ports still I am having issues can
> anyone help.
>
>
>
> Error:-
>
>
> *Exception in thread "main"
> org.apache.ignite.client.ClientConnectionException: Ignite cluster is
> unavailable at org.apache.i*
> gnite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:114)
> at
> org.apache.ignite.internal.client.thin.TcpIgniteClient.lambda$new$0(TcpIgniteClient.java:79)
> at
> org.apache.ignite.internal.client.thin.ReliableChannel.(ReliableChannel.java:84)
> at
> org.apache.ignite.internal.client.thin.TcpIgniteClient.(TcpIgniteClient.java:86)
> at
> org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:205)
> at org.apache.ignite.Ignition.startClient(Ignition.java:586)
> at
> com.ignite.examples.igniteStartup.IgniteClientConnection$.main(IgniteClientConnection.scala:36)
> at
> com.ignite.examples.igniteStartup.IgniteClientConnection.main(IgniteClientConnection.scala)
> *Caused by: java.net.ConnectException: Connection refused (Connection
> refused)*
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net
> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at java.net
> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at java.net
> .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at java.net.Socket.connect(Socket.java:538)
> at java.net.Socket.(Socket.java:434)
> at java.net.Socket.(Socket.java:211)
> at
> org.apache.ignite.internal.client.thin.TcpClientChannel.createSocket(TcpClientChannel.java:216)
> at
> org.apache.ignite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:108)
> ... 7 more
>
>
>
> Scala Code:-
>
> package com.ignite.examples.igniteStartup
> import org.apache.ignite.Igniteimport org.apache.ignite.IgniteCacheimport
> org.apache.ignite.Ignitionimport
> org.apache.ignite.configuration.{ClientConfiguration,
> IgniteConfiguration}import
> org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinderimport
> org.apache.ignite.configuration.IgniteConfigurationimport
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi
Re: Connection Refused in Scala Ignite Client (Help!)
Hi,
Looks like you are trying to connect to the wrong port. The default port
for client connection is 10800.
Change:
val cfg2 = new
ClientConfiguration().setAddresses("100.25.173.220:47100..47700")
to
val cfg2 = new ClientConfiguration().setAddresses("100.25.173.220:10800")
-Artem
On 17.10.2019 03:39, alexanderko...@gmail.com wrote:
You need to replace the ip finder on all nodes to use the s3 one.
add the libraries from |libs/optional/ignite-aws| to your
application's classpath.
No file is required.
*From:* sri hari kali charan Tummala
*Sent:* Wednesday, October 16, 2019 8:10 PM
*To:* user@ignite.apache.org; alexanderko...@gmail.com
*Subject:* Re: Connection Refused in Scala Ignite Client (Help!)
I this below property is while launching ignite on aws
I already have ignite cluster running I just need to connect using
java or Scala code which is failing with connection refused error.
https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
On Wednesday, October 16, 2019, sri hari kali charan Tummala
mailto:kali.tumm...@gmail.com>> wrote:
Do I need to keep any file inside the s3 bucket or is it just a
empty bucket ? With aws credentials and bucket name ?
On Wednesday, October 16, 2019, mailto:alexanderko...@gmail.com>> wrote:
Hi,
Try using the S3 IP Finder:
https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
Thanks, Alex
*From:* sri hari kali charan Tummala mailto:kali.tumm...@gmail.com>>
*Sent:* Wednesday, October 16, 2019 5:55 PM
*To:* user@ignite.apache.org <mailto:user@ignite.apache.org>
*Subject:* Connection Refused in Scala Ignite Client (Help!)
Hi All,
I am trying to connect my ignite cluster which is created on
AWS (), now I am suing scala code to connect to the
client which is failing with connection refused error.
In my security group I opened all the ports still I am having
issues can anyone help.
Error:-
*Exception in thread "main"
org.apache.ignite.client.ClientConnectionException: Ignite
cluster is unavailable
at
org.apache.i*gnite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:114)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.lambda$new$0(TcpIgniteClient.java:79)
at
org.apache.ignite.internal.client.thin.ReliableChannel.(ReliableChannel.java:84)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.(TcpIgniteClient.java:86)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:205)
at org.apache.ignite.Ignition.startClient(Ignition.java:586)
at
com.ignite.examples.igniteStartup.IgniteClientConnection$.main(IgniteClientConnection.scala:36)
at
com.ignite.examples.igniteStartup.IgniteClientConnection.main(IgniteClientConnection.scala)
*Caused by: java.net.ConnectException: Connection refused
(Connection refused)*
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net
<http://java.net>.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net
<http://java.net>.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net
<http://java.net>.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.(Socket.java:434)
at java.net.Socket.(Socket.java:211)
at
org.apache.ignite.internal.client.thin.TcpClientChannel.createSocket(TcpClientChannel.java:216)
at
org.apache.ignite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:108)
... 7 more
Scala Code:-
package com.ignite.examples.igniteStartup import
org.apache.ignite.Ignite import org.apache.ignite.IgniteCache
import org.apache.ignite.Ignition import
org.apache.ignite.configuration.{ClientConfiguration,
IgniteConfiguration} import
org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
import org.apache.ignite.configuration.IgniteConfiguration
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi
import
org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
import java.util.Arrays import java.util.List import
com.ignite.examples.model.Address import
org.apache.ignite.client.{ClientCache
RE: Connection Refused in Scala Ignite Client (Help!)
You need to replace the ip finder on all nodes to use the s3 one.
add the libraries from libs/optional/ignite-aws to your application's classpath.
No file is required.
From: sri hari kali charan Tummala
Sent: Wednesday, October 16, 2019 8:10 PM
To: user@ignite.apache.org; alexanderko...@gmail.com
Subject: Re: Connection Refused in Scala Ignite Client (Help!)
I this below property is while launching ignite on aws
I already have ignite cluster running I just need to connect using java or
Scala code which is failing with connection refused error.
https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
On Wednesday, October 16, 2019, sri hari kali charan Tummala
mailto:kali.tumm...@gmail.com> > wrote:
Do I need to keep any file inside the s3 bucket or is it just a empty bucket ?
With aws credentials and bucket name ?
On Wednesday, October 16, 2019, mailto:alexanderko...@gmail.com> > wrote:
Hi,
Try using the S3 IP Finder:
https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
Thanks, Alex
From: sri hari kali charan Tummala mailto:kali.tumm...@gmail.com> >
Sent: Wednesday, October 16, 2019 5:55 PM
To: user@ignite.apache.org <mailto:user@ignite.apache.org>
Subject: Connection Refused in Scala Ignite Client (Help!)
Hi All,
I am trying to connect my ignite cluster which is created on AWS (), now I am
suing scala code to connect to the client which is failing with connection
refused error.
In my security group I opened all the ports still I am having issues can anyone
help.
Error:-
Exception in thread "main" org.apache.ignite.client.ClientConnectionException:
Ignite cluster is unavailable
at
org.apache.ignite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:114)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.lambda$new$0(TcpIgniteClient.java:79)
at
org.apache.ignite.internal.client.thin.ReliableChannel.(ReliableChannel.java:84)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.(TcpIgniteClient.java:86)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:205)
at org.apache.ignite.Ignition.startClient(Ignition.java:586)
at
com.ignite.examples.igniteStartup.IgniteClientConnection$.main(IgniteClientConnection.scala:36)
at
com.ignite.examples.igniteStartup.IgniteClientConnection.main(IgniteClientConnection.scala)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net <http://java.net>
.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at java.net <http://java.net>
.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net <http://java.net>
.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.(Socket.java:434)
at java.net.Socket.(Socket.java:211)
at
org.apache.ignite.internal.client.thin.TcpClientChannel.createSocket(TcpClientChannel.java:216)
at
org.apache.ignite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:108)
... 7 more
Scala Code:-
package com.ignite.examples.igniteStartup
import org.apache.ignite.Ignite
import org.apache.ignite.IgniteCache
import org.apache.ignite.Ignition
import org.apache.ignite.configuration.{ClientConfiguration,
IgniteConfiguration}
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
import org.apache.ignite.configuration.IgniteConfiguration
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
import java.util.Arrays
import java.util.List
import com.ignite.examples.model.Address
import org.apache.ignite.client.{ClientCache, IgniteClient}
import scala.collection.JavaConversions._
object IgniteClientConnection {
def main(args: Array[String]): Unit = {
System.out.println()
System.out.println(">>> Thin client put-get example started.")
System.out.println(">>> I am here.")
val cfg2 = new ClientConfiguration().setAddresses("100.25.173.220
<http://100.25.173.220> :47100..47700")
val igniteClient:IgniteClient = Ignition.startClient(cfg2)
val CACHE_NAME = "put-get-example";
//val cache:ClientCache[Integer, Address] =
igniteClient.getOrCreateCache(CACHE_NAME)
System.out.format(">>> Created cache [%s].\n", CACHE_NAME)
}
}
--
Thanks & Regards
Sri Tummala
--
Thanks & Regards
Sri Tummala
--
Thanks & Regards
Sri Tummala
Re: Connection Refused in Scala Ignite Client (Help!)
I this below property is while launching ignite on aws
I already have ignite cluster running I just need to connect using java or
Scala code which is failing with connection refused error.
https://apacheignite-mix.readme.io/docs/amazon-aws#section-
amazon-s3-based-discovery
On Wednesday, October 16, 2019, sri hari kali charan Tummala <
kali.tumm...@gmail.com> wrote:
> Do I need to keep any file inside the s3 bucket or is it just a empty
> bucket ? With aws credentials and bucket name ?
>
>
>
> On Wednesday, October 16, 2019, wrote:
>
>> Hi,
>>
>>Try using the S3 IP Finder: https://apacheignite-mix.readm
>> e.io/docs/amazon-aws#section-amazon-s3-based-discovery
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Thanks, Alex
>>
>>
>>
>>
>>
>> *From:* sri hari kali charan Tummala
>> *Sent:* Wednesday, October 16, 2019 5:55 PM
>> *To:* user@ignite.apache.org
>> *Subject:* Connection Refused in Scala Ignite Client (Help!)
>>
>>
>>
>> Hi All,
>>
>>
>>
>> I am trying to connect my ignite cluster which is created on AWS (), now
>> I am suing scala code to connect to the client which is failing with
>> connection refused error.
>>
>>
>>
>> In my security group I opened all the ports still I am having issues can
>> anyone help.
>>
>>
>>
>> Error:-
>>
>>
>> *Exception in thread "main"
>> org.apache.ignite.client.ClientConnectionException: Ignite cluster is
>> unavailableat org.apache.i*gnite.internal.cli
>> ent.thin.TcpClientChannel.(TcpClientChannel.java:114)
>> at org.apache.ignite.internal.client.thin.TcpIgniteClient.lambd
>> a$new$0(TcpIgniteClient.java:79)
>> at org.apache.ignite.internal.client.thin.ReliableChannel.> >(ReliableChannel.java:84)
>> at org.apache.ignite.internal.client.thin.TcpIgniteClient.> >(TcpIgniteClient.java:86)
>> at org.apache.ignite.internal.client.thin.TcpIgniteClient.start
>> (TcpIgniteClient.java:205)
>> at org.apache.ignite.Ignition.startClient(Ignition.java:586)
>> at com.ignite.examples.igniteStartup.IgniteClientConnection$.
>> main(IgniteClientConnection.scala:36)
>> at com.ignite.examples.igniteStartup.IgniteClientConnection.
>> main(IgniteClientConnection.scala)
>> *Caused by: java.net.ConnectException: Connection refused (Connection
>> refused)*
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSock
>> etImpl.java:350)
>> at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPl
>> ainSocketImpl.java:206)
>> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocket
>> Impl.java:188)
>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> at java.net.Socket.connect(Socket.java:589)
>> at java.net.Socket.connect(Socket.java:538)
>> at java.net.Socket.(Socket.java:434)
>> at java.net.Socket.(Socket.java:211)
>> at org.apache.ignite.internal.client.thin.TcpClientChannel.crea
>> teSocket(TcpClientChannel.java:216)
>> at org.apache.ignite.internal.client.thin.TcpClientChannel.> t>(TcpClientChannel.java:108)
>> ... 7 more
>>
>>
>>
>> Scala Code:-
>>
>> package com.ignite.examples.igniteStartup
>>
>> import org.apache.ignite.Ignite
>> import org.apache.ignite.IgniteCache
>> import org.apache.ignite.Ignition
>> import org.apache.ignite.configuration.{ClientConfiguration,
>> IgniteConfiguration}
>> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
>> import org.apache.ignite.configuration.IgniteConfiguration
>> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi
>> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
>> import java.util.Arrays
>> import java.util.List
>> import com.ignite.examples.model.Address
>> import org.apache.ignite.client.{ClientCache, IgniteClient}
>>
>> import scala.collection.JavaConversions._
>>
>> object IgniteClientConnection {
>> def main(args: Array[String]): Unit = {
>>
>> System.*out*.println()
>> System.*out*.println(">>> Thin client put-get example started.")
>> System.*out*.println(">>> I am here.")
>>
>> val cfg2 = new
>> ClientConfiguration().setAddresses("100.25.173.220:47100..47700")
>> val igniteClient:IgniteClient = Ignition.*startClient*(cfg2)
>> val CACHE_NAME = "put-get-example";
>> //val cache:ClientCache[Integer, Address] =
>> igniteClient.getOrCreateCache(CACHE_NAME)
>>
>> System.*out*.format(">>> Created cache [%s].\n", CACHE_NAME)
>>
>>
>>
>> }
>>
>> }
>>
>>
>>
>> --
>>
>> Thanks & Regards
>>
>> Sri Tummala
>>
>>
>>
>
>
> --
> Thanks & Regards
> Sri Tummala
>
>
>
--
Thanks & Regards
Sri Tummala
Re: Connection Refused in Scala Ignite Client (Help!)
Do I need to keep any file inside the s3 bucket or is it just a empty
bucket ? With aws credentials and bucket name ?
On Wednesday, October 16, 2019, wrote:
> Hi,
>
>Try using the S3 IP Finder: https://apacheignite-mix.
> readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Thanks, Alex
>
>
>
>
>
> *From:* sri hari kali charan Tummala
> *Sent:* Wednesday, October 16, 2019 5:55 PM
> *To:* user@ignite.apache.org
> *Subject:* Connection Refused in Scala Ignite Client (Help!)
>
>
>
> Hi All,
>
>
>
> I am trying to connect my ignite cluster which is created on AWS (), now I
> am suing scala code to connect to the client which is failing with
> connection refused error.
>
>
>
> In my security group I opened all the ports still I am having issues can
> anyone help.
>
>
>
> Error:-
>
>
> *Exception in thread "main"
> org.apache.ignite.client.ClientConnectionException: Ignite cluster is
> unavailableat org.apache.i*gnite.internal.client.thin.TcpClientChannel.<
> init>(TcpClientChannel.java:114)
> at org.apache.ignite.internal.client.thin.TcpIgniteClient.
> lambda$new$0(TcpIgniteClient.java:79)
> at org.apache.ignite.internal.client.thin.ReliableChannel.<
> init>(ReliableChannel.java:84)
> at org.apache.ignite.internal.client.thin.TcpIgniteClient.<
> init>(TcpIgniteClient.java:86)
> at org.apache.ignite.internal.client.thin.TcpIgniteClient.
> start(TcpIgniteClient.java:205)
> at org.apache.ignite.Ignition.startClient(Ignition.java:586)
> at com.ignite.examples.igniteStartup.IgniteClientConnection$.main(
> IgniteClientConnection.scala:36)
> at com.ignite.examples.igniteStartup.IgniteClientConnection.main(
> IgniteClientConnection.scala)
> *Caused by: java.net.ConnectException: Connection refused (Connection
> refused)*
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at java.net.AbstractPlainSocketImpl.doConnect(
> AbstractPlainSocketImpl.java:350)
> at java.net.AbstractPlainSocketImpl.connectToAddress(
> AbstractPlainSocketImpl.java:206)
> at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:
> 188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:589)
> at java.net.Socket.connect(Socket.java:538)
> at java.net.Socket.(Socket.java:434)
> at java.net.Socket.(Socket.java:211)
> at org.apache.ignite.internal.client.thin.TcpClientChannel.
> createSocket(TcpClientChannel.java:216)
> at org.apache.ignite.internal.client.thin.TcpClientChannel.<
> init>(TcpClientChannel.java:108)
> ... 7 more
>
>
>
> Scala Code:-
>
> package com.ignite.examples.igniteStartup
>
> import org.apache.ignite.Ignite
> import org.apache.ignite.IgniteCache
> import org.apache.ignite.Ignition
> import org.apache.ignite.configuration.{ClientConfiguration,
> IgniteConfiguration}
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
> import org.apache.ignite.configuration.IgniteConfiguration
> import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi
> import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
> import java.util.Arrays
> import java.util.List
> import com.ignite.examples.model.Address
> import org.apache.ignite.client.{ClientCache, IgniteClient}
>
> import scala.collection.JavaConversions._
>
> object IgniteClientConnection {
> def main(args: Array[String]): Unit = {
>
> System.*out*.println()
> System.*out*.println(">>> Thin client put-get example started.")
> System.*out*.println(">>> I am here.")
>
> val cfg2 = new
> ClientConfiguration().setAddresses("100.25.173.220:47100..47700")
> val igniteClient:IgniteClient = Ignition.*startClient*(cfg2)
> val CACHE_NAME = "put-get-example";
> //val cache:ClientCache[Integer, Address] =
> igniteClient.getOrCreateCache(CACHE_NAME)
>
> System.*out*.format(">>> Created cache [%s].\n", CACHE_NAME)
>
>
>
> }
>
> }
>
>
>
> --
>
> Thanks & Regards
>
> Sri Tummala
>
>
>
--
Thanks & Regards
Sri Tummala
RE: Connection Refused in Scala Ignite Client (Help!)
Hi,
Try using the S3 IP Finder:
https://apacheignite-mix.readme.io/docs/amazon-aws#section-amazon-s3-based-discovery
Thanks, Alex
From: sri hari kali charan Tummala
Sent: Wednesday, October 16, 2019 5:55 PM
To: user@ignite.apache.org
Subject: Connection Refused in Scala Ignite Client (Help!)
Hi All,
I am trying to connect my ignite cluster which is created on AWS (), now I am
suing scala code to connect to the client which is failing with connection
refused error.
In my security group I opened all the ports still I am having issues can anyone
help.
Error:-
Exception in thread "main" org.apache.ignite.client.ClientConnectionException:
Ignite cluster is unavailable
at
org.apache.ignite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:114)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.lambda$new$0(TcpIgniteClient.java:79)
at
org.apache.ignite.internal.client.thin.ReliableChannel.(ReliableChannel.java:84)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.(TcpIgniteClient.java:86)
at
org.apache.ignite.internal.client.thin.TcpIgniteClient.start(TcpIgniteClient.java:205)
at org.apache.ignite.Ignition.startClient(Ignition.java:586)
at
com.ignite.examples.igniteStartup.IgniteClientConnection$.main(IgniteClientConnection.scala:36)
at
com.ignite.examples.igniteStartup.IgniteClientConnection.main(IgniteClientConnection.scala)
Caused by: java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.(Socket.java:434)
at java.net.Socket.(Socket.java:211)
at
org.apache.ignite.internal.client.thin.TcpClientChannel.createSocket(TcpClientChannel.java:216)
at
org.apache.ignite.internal.client.thin.TcpClientChannel.(TcpClientChannel.java:108)
... 7 more
Scala Code:-
package com.ignite.examples.igniteStartup
import org.apache.ignite.Ignite
import org.apache.ignite.IgniteCache
import org.apache.ignite.Ignition
import org.apache.ignite.configuration.{ClientConfiguration,
IgniteConfiguration}
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
import org.apache.ignite.configuration.IgniteConfiguration
import org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi
import org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder
import java.util.Arrays
import java.util.List
import com.ignite.examples.model.Address
import org.apache.ignite.client.{ClientCache, IgniteClient}
import scala.collection.JavaConversions._
object IgniteClientConnection {
def main(args: Array[String]): Unit = {
System.out.println()
System.out.println(">>> Thin client put-get example started.")
System.out.println(">>> I am here.")
val cfg2 = new
ClientConfiguration().setAddresses("100.25.173.220:47100..47700")
val igniteClient:IgniteClient = Ignition.startClient(cfg2)
val CACHE_NAME = "put-get-example";
//val cache:ClientCache[Integer, Address] =
igniteClient.getOrCreateCache(CACHE_NAME)
System.out.format(">>> Created cache [%s].\n", CACHE_NAME)
}
}
--
Thanks & Regards
Sri Tummala
Re: TcpDiscoverSpi error connection refused
Thanks Denis.
Sent from my iPhone
> On 9 Apr 2018, at 18:22, Denis Mekhanikov <dmekhani...@gmail.com> wrote:
>
> There are the following lines in the TcpDiscoverySpi implementation:
>
> if (log.isDebugEnabled())
> log.error("Exception on direct send: " + e.getMessage(), e);
>
> So, these exceptions are shown only when debug logging is enabled, and they
> are logged as errors.
>
> Neeraj, you probably just didn't enable debug log on the second node, so you
> don't see these exceptions on it.
>
> Denis
>
> пн, 9 апр. 2018 г. в 7:00, Neeraj Vaidya <neeraj.vai...@yahoo.co.in>:
>> Hi Denis,
>> But this issue does not occur on node2 even if it is started before node1. I
>> feel even otherwise this message related to Discovery of level SEVERE is a
>> bit misleading. Wouldn’t it be visible when log level is anything higher
>> than DEBUG as well ? I agree this is not a functional issue as it only
>> occurs at startup when performing discovery and gets cleared when a peer is
>> discovered.
>>
>> Regards,
>> Neeraj
>>
>> Sent from my iPhone
>>
>>> On 8 Apr 2018, at 01:58, Amir Akhmedov <amir.akhme...@gmail.com> wrote:
>>>
>>> Hi Denis,
>>>
>>> I had a similar logs before and I can confirm I got them when enabled
>>> "debug" level but the log level "severe" was really confusing.
>>>
>>>> On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov <dmekhani...@gmail.com>
>>>> wrote:
>>>> Neeraj,
>>>>
>>>> You probably enabled debug logging on the following package:
>>>> org.apache.ignite.spi.discovery.tcp
>>>>
>>>> There is nothing wrong in these exceptions actually.
>>>> The first connection refused exception happens because there are two hosts
>>>> in the IP finder configuration, but when you start the first node, nobody
>>>> is bound to the discovery port on the second host. So, you get "Connection
>>>> refused" exception, when discovery SPI is trying to connect to the second
>>>> host.
>>>>
>>>> If you see a message like this, then it means, that discovery finished its
>>>> work successfully:
>>>> Topology snapshot [ver=1, servers=1, ...]
>>>>
>>>> You can disable debug logging not to see these exceptions.
>>>>
>>>> The second exception is also doesn't mean anything bad.
>>>> It only means, that some object was transferred to this node, and
>>>> connection was suddenly closed.
>>>>
>>>> So, none of these exceptions mean anything bad.
>>>>
>>>> Denis
>>>>
>>>> пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya <neeraj.vai...@yahoo.co.in>:
>>>>> Hi,
>>>>> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld
>>>>> stopped and disabled.
>>>>> The nodes are axlrate-node-1 and axlrate-node-2. I have updated
>>>>> default-config.xml in both servers
>>>>> My default-config.xml looks like below :
>>>>> -default-config.xml
>>>>> @ axlrate-node-1-
>>>>> http://www.springframework.org/schema/beans;
>>>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>>>>xsi:schemaLocation="
>>>>>http://www.springframework.org/schema/beans
>>>>>http://www.springframework.org/schema/beans/spring-beans.xsd;>
>>>>>
>>>>> >>>> class="org.apache.ignite.configuration.IgniteConfiguration">
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> >>>> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>>>
>>>>>
>>>>>
>>>>> axlrate-node-1
>>>>> axlrate-node-2
>>>>>
>>>>>
>
Re: TcpDiscoverSpi error connection refused
There are the following lines in the TcpDiscoverySpi implementation:
if (log.isDebugEnabled())
log.error("Exception on direct send: " + e.getMessage(), e);
So, these exceptions are shown only when debug logging is enabled, and they
are logged as errors.
Neeraj, you probably just didn't enable debug log on the second node, so
you don't see these exceptions on it.
Denis
пн, 9 апр. 2018 г. в 7:00, Neeraj Vaidya <neeraj.vai...@yahoo.co.in>:
> Hi Denis,
> But this issue does not occur on node2 even if it is started before node1.
> I feel even otherwise this message related to Discovery of level SEVERE is
> a bit misleading. Wouldn’t it be visible when log level is anything higher
> than DEBUG as well ? I agree this is not a functional issue as it only
> occurs at startup when performing discovery and gets cleared when a peer is
> discovered.
>
> Regards,
> Neeraj
>
> Sent from my iPhone
>
> On 8 Apr 2018, at 01:58, Amir Akhmedov <amir.akhme...@gmail.com> wrote:
>
> Hi Denis,
>
> I had a similar logs before and I can confirm I got them when enabled
> "debug" level but the log level "severe" was really confusing.
>
> On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov <dmekhani...@gmail.com>
> wrote:
>
>> Neeraj,
>>
>> You probably enabled debug logging on the following package:
>> *org.apache.ignite.spi.discovery.tcp*
>>
>> There is nothing wrong in these exceptions actually.
>> The first connection refused exception happens because there are two
>> hosts in the IP finder configuration, but when you start the first node,
>> nobody is bound to the discovery port on the second host. So, you get
>> *"Connection
>> refused" *exception, when discovery SPI is trying to connect to the
>> second host.
>>
>> If you see a message like this, then it means, that discovery finished
>> its work successfully:
>> *Topology snapshot [ver=1, servers=1, ...]*
>>
>> You can disable debug logging not to see these exceptions.
>>
>> The second exception is also doesn't mean anything bad.
>> It only means, that some object was transferred to this node, and
>> connection was suddenly closed.
>>
>> So, none of these exceptions mean anything bad.
>>
>> Denis
>>
>> пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya <neeraj.vai...@yahoo.co.in>:
>>
>>> Hi,
>>> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld
>>> stopped and disabled.
>>> The nodes are axlrate-node-1 and axlrate-node-2. I have updated
>>> default-config.xml in both servers
>>> My default-config.xml looks like below :
>>> -default-config.xml
>>> @ axlrate-node-1-
>>> http://www.springframework.org/schema/beans;
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>>xsi:schemaLocation="
>>>http://www.springframework.org/schema/beans
>>>http://www.springframework.org/schema/beans/spring-beans.xsd;>
>>>
>>> >> class="org.apache.ignite.configuration.IgniteConfiguration">
>>>
>>>
>>>
>>>
>>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder">
>>>
>>>
>>>
>>> axlrate-node-1
>>> axlrate-node-2
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> ---
>>>
>>> -default-config.xml
>>> @ axlrate-node-2-
>>> http://www.springframework.org/schema/beans;
>>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>>>xsi:schemaLocation="
>>>http://www.springframework.org/schema/beans
>>>http://www.springframework.org/schema/beans/spring-beans.xsd;>
>>>
>>> >> class="org.apache.ignite.configuration.IgniteConfiguration">
>>>
>>>
>>>
>>>
>>> >> class
Re: TcpDiscoverSpi error connection refused
Hi Denis, But this issue does not occur on node2 even if it is started before node1. I feel even otherwise this message related to Discovery of level SEVERE is a bit misleading. Wouldn’t it be visible when log level is anything higher than DEBUG as well ? I agree this is not a functional issue as it only occurs at startup when performing discovery and gets cleared when a peer is discovered. Regards, Neeraj Sent from my iPhone > On 8 Apr 2018, at 01:58, Amir Akhmedov <amir.akhme...@gmail.com> wrote: > > Hi Denis, > > I had a similar logs before and I can confirm I got them when enabled "debug" > level but the log level "severe" was really confusing. > >> On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov <dmekhani...@gmail.com> wrote: >> Neeraj, >> >> You probably enabled debug logging on the following package: >> org.apache.ignite.spi.discovery.tcp >> >> There is nothing wrong in these exceptions actually. >> The first connection refused exception happens because there are two hosts >> in the IP finder configuration, but when you start the first node, nobody is >> bound to the discovery port on the second host. So, you get "Connection >> refused" exception, when discovery SPI is trying to connect to the second >> host. >> >> If you see a message like this, then it means, that discovery finished its >> work successfully: >> Topology snapshot [ver=1, servers=1, ...] >> >> You can disable debug logging not to see these exceptions. >> >> The second exception is also doesn't mean anything bad. >> It only means, that some object was transferred to this node, and connection >> was suddenly closed. >> >> So, none of these exceptions mean anything bad. >> >> Denis >> >> пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya <neeraj.vai...@yahoo.co.in>: >>> Hi, >>> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld >>> stopped and disabled. >>> The nodes are axlrate-node-1 and axlrate-node-2. I have updated >>> default-config.xml in both servers >>> My default-config.xml looks like below : >>> -default-config.xml >>> @ axlrate-node-1- >>> http://www.springframework.org/schema/beans; >>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >>>xsi:schemaLocation=" >>>http://www.springframework.org/schema/beans >>>http://www.springframework.org/schema/beans/spring-beans.xsd;> >>> >>> >> class="org.apache.ignite.configuration.IgniteConfiguration"> >>> >>> >>> >>> >>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >>> >>> >>> >>> axlrate-node-1 >>> axlrate-node-2 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> --- >>> >>> -default-config.xml >>> @ axlrate-node-2- >>> http://www.springframework.org/schema/beans; >>>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >>>xsi:schemaLocation=" >>>http://www.springframework.org/schema/beans >>>http://www.springframework.org/schema/beans/spring-beans.xsd;> >>> >>> >> class="org.apache.ignite.configuration.IgniteConfiguration"> >>> >>> >>> >>> >>> >> class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >>> >>> >>> >>> axlrate-node-1 >>> axlrate-node-2 >>> >>> >>> >>> >>> >>> >>> >>> >>> >>>
Re: TcpDiscoverSpi error connection refused
Hi Denis, I had a similar logs before and I can confirm I got them when enabled "debug" level but the log level "severe" was really confusing. On Fri, Apr 6, 2018, 8:52 AM Denis Mekhanikov <dmekhani...@gmail.com> wrote: > Neeraj, > > You probably enabled debug logging on the following package: > *org.apache.ignite.spi.discovery.tcp* > > There is nothing wrong in these exceptions actually. > The first connection refused exception happens because there are two hosts > in the IP finder configuration, but when you start the first node, nobody > is bound to the discovery port on the second host. So, you get *"Connection > refused" *exception, when discovery SPI is trying to connect to the > second host. > > If you see a message like this, then it means, that discovery finished its > work successfully: > *Topology snapshot [ver=1, servers=1, ...]* > > You can disable debug logging not to see these exceptions. > > The second exception is also doesn't mean anything bad. > It only means, that some object was transferred to this node, and > connection was suddenly closed. > > So, none of these exceptions mean anything bad. > > Denis > > пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya <neeraj.vai...@yahoo.co.in>: > >> Hi, >> I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld >> stopped and disabled. >> The nodes are axlrate-node-1 and axlrate-node-2. I have updated >> default-config.xml in both servers >> My default-config.xml looks like below : >> -default-config.xml >> @ axlrate-node-1- >> http://www.springframework.org/schema/beans; >>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >>xsi:schemaLocation=" >>http://www.springframework.org/schema/beans >>http://www.springframework.org/schema/beans/spring-beans.xsd;> >> >> > class="org.apache.ignite.configuration.IgniteConfiguration"> >> >> >> >> >> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >> >> >> >> axlrate-node-1 >> axlrate-node-2 >> >> >> >> >> >> >> >> >> >> >> --- >> >> -default-config.xml >> @ axlrate-node-2- >> http://www.springframework.org/schema/beans; >>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >>xsi:schemaLocation=" >>http://www.springframework.org/schema/beans >>http://www.springframework.org/schema/beans/spring-beans.xsd;> >> >> > class="org.apache.ignite.configuration.IgniteConfiguration"> >> >> >> >> >> > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> >> >> >> >> axlrate-node-1 >> axlrate-node-2 >> >> >> >> >> >> >> >> >> >> >> --------------- >> >> >> When I try to start ignite on axlrate-node-1, I see the following error >> at startup. >> >> ---log >> on >> axlrate-node-1--- >> [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send: >> Connection refused (Connection refused) >> java.net.ConnectException: Connection refused (Connection refused) >> at java.net.PlainSocketImpl.socketConnect(Native Method) >> at java.net >> .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) >> at java.net >> .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) >>
Re: TcpDiscoverSpi error connection refused
Neeraj, You probably enabled debug logging on the following package: *org.apache.ignite.spi.discovery.tcp* There is nothing wrong in these exceptions actually. The first connection refused exception happens because there are two hosts in the IP finder configuration, but when you start the first node, nobody is bound to the discovery port on the second host. So, you get *"Connection refused" *exception, when discovery SPI is trying to connect to the second host. If you see a message like this, then it means, that discovery finished its work successfully: *Topology snapshot [ver=1, servers=1, ...]* You can disable debug logging not to see these exceptions. The second exception is also doesn't mean anything bad. It only means, that some object was transferred to this node, and connection was suddenly closed. So, none of these exceptions mean anything bad. Denis пт, 6 апр. 2018 г. в 2:34, Neeraj Vaidya <neeraj.vai...@yahoo.co.in>: > Hi, > I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld > stopped and disabled. > The nodes are axlrate-node-1 and axlrate-node-2. I have updated > default-config.xml in both servers > My default-config.xml looks like below : > -default-config.xml > @ axlrate-node-1- > http://www.springframework.org/schema/beans; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >xsi:schemaLocation=" >http://www.springframework.org/schema/beans >http://www.springframework.org/schema/beans/spring-beans.xsd;> > > class="org.apache.ignite.configuration.IgniteConfiguration"> > > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > > > > axlrate-node-1 > axlrate-node-2 > > > > > > > > > > > --- > > -default-config.xml > @ axlrate-node-2- > http://www.springframework.org/schema/beans; >xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; >xsi:schemaLocation=" >http://www.springframework.org/schema/beans >http://www.springframework.org/schema/beans/spring-beans.xsd;> > > class="org.apache.ignite.configuration.IgniteConfiguration"> > > > > > class="org.apache.ignite.spi.discovery.tcp.ipfinder.vm.TcpDiscoveryVmIpFinder"> > > > > axlrate-node-1 > axlrate-node-2 > > > > > > > > > > > --- > > > When I try to start ignite on axlrate-node-1, I see the following error at > startup. > > ---------------log > on > axlrate-node-1--- > [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send: > Connection refused (Connection refused) > java.net.ConnectException: Connection refused (Connection refused) > at java.net.PlainSocketImpl.socketConnect(Native Method) > at java.net > .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) > at java.net > .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at java.net > .AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1386) > at > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1349) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1169) > at > org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1016) > at &g
TcpDiscoverSpi error connection refused
Hi, I have 2 virtualbox guest OS'es (CentOS7 64-bit) , each having firewalld stopped and disabled. The nodes are axlrate-node-1 and axlrate-node-2. I have updated default-config.xml in both servers My default-config.xml looks like below : -default-config.xml @ axlrate-node-1- http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd;> axlrate-node-1 axlrate-node-2 --- -default-config.xml @ axlrate-node-2- http://www.springframework.org/schema/beans; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=" http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd;> axlrate-node-1 axlrate-node-2 --- When I try to start ignite on axlrate-node-1, I see the following error at startup. ---log on axlrate-node-1--- [09:14:41,747][SEVERE][main][TcpDiscoverySpi] Exception on direct send: Connection refused (Connection refused) java.net.ConnectException: Connection refused (Connection refused) at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1386) at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1349) at org.apache.ignite.spi.discovery.tcp.ServerImpl.sendMessageDirectly(ServerImpl.java:1169) at org.apache.ignite.spi.discovery.tcp.ServerImpl.sendJoinRequestMessage(ServerImpl.java:1016) at org.apache.ignite.spi.discovery.tcp.ServerImpl.joinTopology(ServerImpl.java:860) at org.apache.ignite.spi.discovery.tcp.ServerImpl.spiStart(ServerImpl.java:360) at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.spiStart(TcpDiscoverySpi.java:1846) at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:297) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:882) at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1852) at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:1002) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1909) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1652) at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1080) at org.apache.ignite.internal.IgnitionEx.startConfigurations(IgnitionEx.java:998) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:884) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:783) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:653) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:622) at org.apache.ignite.Ignition.start(Ignition.java:347) at org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:302) - Then, when I start the axlrate-node-2, the nodes discover each other successfully. However, when I stop axlrate-node-2, I see the following error in
Re: 答复: 答复: 答复: 答复: ignite Connection refused exception
Kevin, Actually, connections are not established frequently. If there is a lot of communication between two nodes, they will create it once and then reuse. So I'm not sure if it will cause degradation. In any case, this sounds like a network issue. I would recommend to investigate this separately from Ignite, using the network diagnostic tools like iperf and others. -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-Connection-refused-exception-tp6412p6550.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
答复: 答复: 答复: 答复: ignite Connection refused exception
Hi Val, After setting join timeout to 30s and socket timeout to 30s too. I can connect to the server. If each connection takes so long time, it may cause performance issue. Do you have any suggestions on client to server connect? Best regards, Kevin -邮件原件- 发件人: vkulichenko [mailto:valentin.kuliche...@gmail.com] 发送时间: 2016年7月26日 6:45 收件人: user@ignite.apache.org 主题: Re: 答复: 答复: 答复: ignite Connection refused exception Hi Kevin, The exception itself is actually printed out only in DEBUG mode. It will always happen if you provide a range of addresses, but only some of them are available. So this is not an issue. I noticed that it takes around a second to get 'Connection refused' from each address, so going through all of them can take some time. Can you try increasing the joinTimeout value to, for example, 30 seconds? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-Connection-refused-exception-tp6412p6523.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: 答复: 答复: ignite Connection refused exception
Hi Kevin, Can you please attach full logs files from all nodes, including the client? -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/ignite-Connection-refused-exception-tp6412p6479.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
答复: 答复: ignite Connection refused exception
Hi Val,
Your suggestion works like a charm.
Thank you very much.
Best regards,
Kevin
发件人: Vladimir Ozerov [mailto:voze...@gridgain.com]
发送时间: 2016年7月21日 19:10
收件人: user@ignite.apache.org
主题: Re: 答复: ignite Connection refused exception
Hi Kevin,
The last error message suggests that it was a problem when trying to establish
communication between two nodes on the same machine using shared memory
mechanics. It is not clear now what is the reason for this, but I would try to
disable shared memory and see if it helps.
In XML file please add the following bean:
...
And add the following line to your programmatic configuration:
TcpCommunicationSpi commSpi = new TcpCommunicationSpi();
commSpi.setSharedMemoryPort(-1);
igniteCCF.setCommunicationSpi(commSpi);
Please let me know if it resolves the problem. Otherwise please attach the
whole logs from all nodes.
Vladimir.
On Thu, Jul 21, 2016 at 12:03 PM, Zhengqingzheng
<zhengqingzh...@huawei.com<mailto:zhengqingzh...@huawei.com>> wrote:
Hi Denis,
I have configured TcpDiscoverySpi both on the server side and client side.
On the server side, my configuration is as follows:
10.120.70.122:47500..47509
10.120.89.196:47500..47509
On the client side, I am using java to configure the cache, here is the code:
TcpDiscoveryVmIpFinder ipFinder = new TcpDiscoveryVmIpFinder(false);
List addrs = new ArrayList();
addrs.add(IGNITE_NEW_ADDRESS);
addrs.add(IGNITE_ADDRESS);
ipFinder.setAddresses(addrs);
TcpDiscoverySpi discoverySpi = new TcpDiscoverySpi();
discoverySpi.setIpFinder(ipFinder);
// discoverySpi.setLocalAddress(instanceName);
// discoverySpi.setLocalPort(47505);
igniteCCF.setDiscoverySpi(discoverySpi);
TcpCommunicationSpi commSpi = new TcpCommunicationSpi();
igniteCCF.setCommunicationSpi(commSpi);
//create ignite instance
ignite = Ignition.start(igniteCCF);
But I still cannot connect to the server. Or I should see, it did connected to
the server, however, closed without communication.
When I check the server console, I can see the client node joined, but return
the following error:
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at
org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)
Caused by: class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
reconCnt=10, maxAckTimeout=60, forceSrvMode=false,
clientReconnectDisabled=false]
at
org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258)
at
org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660)
at
org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
... 36 more
Caused by: class org.apache.ignite.spi.IgniteSpiException: Failed to connect to
cluster, connection failed and failed to reconnect.
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$Reconnector.body(ClientImpl.java:1287)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
also I checked the log, the there are two types of error messages：
1.
[21:15:30,801][ERROR][grid-time-coordinator-#50%null%][GridClockSyncProcessor]
Failed to send time sync snapshot to remote node (did not leave grid?)
[nodeId=de5a1f4c-d051-4dec-97d0-37da943ebd88, msg=GridClockDeltaSnapshotMessage
[snapVer=GridClockDeltaVersion [ver=55, topVer=30],
deltas={66198003-510d-4170-8b8f-5316c01f3d58=8740,
8c38e19b-3aeb-4865-834b-ee6327913980=96665,
8fb43d92-da97-4be9-8ecd-50c6456d0362=72055,
2623a147-609e-4e64-97e3-e8a7fc9ccc42=96665,
109e1f29-6c93-4e77-a6e0-ba09adbc79eb=-3227,
6cbddaee-3fc9-4132-88ed-19ab1e5195a1=-5236,
de5a1f4c-d051-4dec-97d0-37da943ebd88=-10946}], err=Failed to send message (node
may have left the grid or TCP connection cannot be established due to firewall
issues) [node=TcpDiscoveryNode [id=de5a1f4c-d051-4dec-97d0-37da943ebd88,
addrs=[0:0:0:0:0:0:0:1, 10.135.66.169, 127.0.0.1],
sockAddrs=[/0:0:0:0:0:0:0:1:0, /0:0:0:0:0:0:0:1:0,
/10.135.66.169:0<http://10.135.66.169:0>, /127.0.0.1:0<http://127.0.0.1:0>],
discPort=
Re: 答复: ignite Connection refused exception
5,
> 109e1f29-6c93-4e77-a6e0-ba09adbc79eb=-3227,
> 6cbddaee-3fc9-4132-88ed-19ab1e5195a1=-5236,
> de5a1f4c-d051-4dec-97d0-37da943ebd88=-10946}], err=Failed to send message
> (node may have left the grid or TCP connection cannot be established due to
> firewall issues) [node=TcpDiscoveryNode
> [id=de5a1f4c-d051-4dec-97d0-37da943ebd88, addrs=[0:0:0:0:0:0:0:1,
> 10.135.66.169, 127.0.0.1], sockAddrs=[/0:0:0:0:0:0:0:1:0,
> /0:0:0:0:0:0:0:1:0, /10.135.66.169:0, /127.0.0.1:0], discPort=0,
> order=30, intOrder=20, lastExchangeTime=1469020510684, loc=false,
> ver=1.5.0#20151229-sha1:f1f8cda2, isClient=true], topic=TOPIC_TIME_SYNC,
> msg=GridClockDeltaSnapshotMessage [snapVer=GridClockDeltaVersion [ver=55,
> topVer=30], deltas={66198003-510d-4170-8b8f-5316c01f3d58=8740,
> 8c38e19b-3aeb-4865-834b-ee6327913980=96665,
> 8fb43d92-da97-4be9-8ecd-50c6456d0362=72055,
> 2623a147-609e-4e64-97e3-e8a7fc9ccc42=96665,
> 109e1f29-6c93-4e77-a6e0-ba09adbc79eb=-3227,
> 6cbddaee-3fc9-4132-88ed-19ab1e5195a1=-5236,
> de5a1f4c-d051-4dec-97d0-37da943ebd88=-10946}], policy=2]]
>
> 2.
> [09:00:10,873][ERROR][shmem-communication-acceptor-#40%null%][TcpCommunicationSpi]
> Failed to process incoming shared memory connection: null
>
>
>
> Any Idea how to fix it?
>
>
>
> Best regards,
>
> Kevin
>
>
>
> *发件人:* Denis Magda [mailto:dma...@gridgain.com]
> *发送时间:* 2016年7月20日 19:40
> *收件人:* user@ignite.apache.org
> *主题:* Re: ignite Connection refused exception
>
>
>
> Hi Kevin,
>
>
>
> The exception means that the connection was rejected on a remote side
> (server side). Please make sure that discovery SPI ports are opened between
> the server and client and that the client connects to a valid server node
> (the server node must listen for incoming connection in one of the ports
> specified in client’s IP finder configuration).
>
>
>
> —
>
> Denis
>
>
>
> On Jul 20, 2016, at 12:27 PM, Zhengqingzheng <zhengqingzh...@huawei.com>
> wrote:
>
>
>
> Hi there,
>
> When using ignite client connect to the server, I always get exceptions
> like this:
>
> [17:22:24,440][ERROR][tcp-client-disco-msg-worker-#4%default%][TcpDiscoverySpi]
> Exception on joining: Connection refused: connect
>
> java.net.ConnectException: Connection refused: connect
>
> at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
>
> at
> java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85)
>
> at
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>
> at
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>
> at
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>
> at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172)
>
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>
> at java.net.Socket.connect(Socket.java:589)
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1266)
>
> at
> org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1241)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:579)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:505)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:118)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:1508)
>
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1327)
>
> at
> org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
>
> and exceptions like this:
>
>
>
> [17:22:48,949][ERROR][main][IgniteKernal%default] Failed to start manager:
> GridManagerAdapter [enabled=true,
> name=o.a.i.i.managers.discovery.GridDiscoveryManager]
>
> class org.apache.ignite.IgniteCheckedException: Failed to start SPI:
> TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000,
> reconCnt=10, maxAckTimeout=60, forceSrvMode=false,
> clientReconnectDisabled=false]
>
> at
> org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258)
>
> at
> org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660)
>
> at
> org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505)
>
> at
> org.apache.ignite.internal.
Re: ignite Connection refused exception
Hi Kevin, The exception means that the connection was rejected on a remote side (server side). Please make sure that discovery SPI ports are opened between the server and client and that the client connects to a valid server node (the server node must listen for incoming connection in one of the ports specified in client’s IP finder configuration). — Denis > On Jul 20, 2016, at 12:27 PM, Zhengqingzheng <zhengqingzh...@huawei.com> > wrote: > > Hi there, > When using ignite client connect to the server, I always get exceptions like > this: > [17:22:24,440][ERROR][tcp-client-disco-msg-worker-#4%default%][TcpDiscoverySpi] > Exception on joining: Connection refused: connect > java.net.ConnectException: Connection refused: connect > at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) > at > java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) > at > java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) > at > java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > at > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) > at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > at java.net.Socket.connect(Socket.java:589) > at > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1266) > at > org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1241) > at > org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:579) > at > org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:505) > at > org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:118) > at > org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:1508) > at > org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1327) > at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) > and exceptions like this: > > [17:22:48,949][ERROR][main][IgniteKernal%default] Failed to start manager: > GridManagerAdapter [enabled=true, > name=o.a.i.i.managers.discovery.GridDiscoveryManager] > class org.apache.ignite.IgniteCheckedException: Failed to start SPI: > TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000, > reconCnt=10, maxAckTimeout=60, forceSrvMode=false, > clientReconnectDisabled=false] > at > org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258) > at > org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660) > at > org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505) > at > org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688) > at > org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547) > at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534) > at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515) > at org.apache.ignite.Ignition.start(Ignition.java:322) > at > com.huawei.soa.ignite.util.IgniteMetaUtils.initCache(IgniteMetaUtils.java:964) > at > com.huawei.soa.ignite.util.IgniteMetaUtils.init(IgniteMetaUtils.java:327) > at > com.huawei.soa.ignite.util.IgniteMetaUtils.(IgniteMetaUtils.java:296) > at > com.huawei.soa.ignite.util.IgniteMetaUtils.getInstance(IgniteMetaUtils.java:124) > at > com.huawei.soa.ignite.test.IgniteTest.loadProdCache0(IgniteTest.java:1565) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at > org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) > at > org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) > at > org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) > at > org.jun
ignite Connection refused exception
Hi there, When using ignite client connect to the server, I always get exceptions like this: [17:22:24,440][ERROR][tcp-client-disco-msg-worker-#4%default%][TcpDiscoverySpi] Exception on joining: Connection refused: connect java.net.ConnectException: Connection refused: connect at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method) at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:85) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:172) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) at java.net.Socket.connect(Socket.java:589) at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1266) at org.apache.ignite.spi.discovery.tcp.TcpDiscoverySpi.openSocket(TcpDiscoverySpi.java:1241) at org.apache.ignite.spi.discovery.tcp.ClientImpl.sendJoinRequest(ClientImpl.java:579) at org.apache.ignite.spi.discovery.tcp.ClientImpl.joinTopology(ClientImpl.java:505) at org.apache.ignite.spi.discovery.tcp.ClientImpl.access$900(ClientImpl.java:118) at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.tryJoin(ClientImpl.java:1508) at org.apache.ignite.spi.discovery.tcp.ClientImpl$MessageWorker.body(ClientImpl.java:1327) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) and exceptions like this: [17:22:48,949][ERROR][main][IgniteKernal%default] Failed to start manager: GridManagerAdapter [enabled=true, name=o.a.i.i.managers.discovery.GridDiscoveryManager] class org.apache.ignite.IgniteCheckedException: Failed to start SPI: TcpDiscoverySpi [addrRslvr=null, sockTimeout=5000, ackTimeout=5000, reconCnt=10, maxAckTimeout=60, forceSrvMode=false, clientReconnectDisabled=false] at org.apache.ignite.internal.managers.GridManagerAdapter.startSpi(GridManagerAdapter.java:258) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager.start(GridDiscoveryManager.java:660) at org.apache.ignite.internal.IgniteKernal.startManager(IgniteKernal.java:1505) at org.apache.ignite.internal.IgniteKernal.start(IgniteKernal.java:917) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start0(IgnitionEx.java:1688) at org.apache.ignite.internal.IgnitionEx$IgniteNamedInstance.start(IgnitionEx.java:1547) at org.apache.ignite.internal.IgnitionEx.start0(IgnitionEx.java:1003) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:534) at org.apache.ignite.internal.IgnitionEx.start(IgnitionEx.java:515) at org.apache.ignite.Ignition.start(Ignition.java:322) at com.huawei.soa.ignite.util.IgniteMetaUtils.initCache(IgniteMetaUtils.java:964) at com.huawei.soa.ignite.util.IgniteMetaUtils.init(IgniteMetaUtils.java:327) at com.huawei.soa.ignite.util.IgniteMetaUtils.(IgniteMetaUtils.java:296) at com.huawei.soa.ignite.util.IgniteMetaUtils.getInstance(IgniteMetaUtils.java:124) at com.huawei.soa.ignite.test.IgniteTest.loadProdCache0(IgniteTest.java:1565) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:497) at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:44) at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15) at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:41) at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:73) at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:46) at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:180) at org.junit.runners.ParentRunner.access$000(ParentRunner.java:41) at org.junit.runners.ParentRunner$1.evaluate(ParentRunner.java:173) at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28) at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:31) at org.junit.runners.ParentRunner.run
Re: Connection refused via JDBC
Hi, Please subscribe to the user list (this way we will not have to manually approve your emails, it's really annoying). All you need to do is send an email to “ user-subscr...@ignite.apache.org” and follow simple instructions in the reply. >From what I see, JdbcConnectionPool is H2 database specific factory that returns H2 DataSource. Take a look at the package name if the factory. If you want to use MySql instead then you should use some other standard way to create a MySql DataSource. -- Denis -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Connection-refused-via-JDBC-tp2490p2491.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Connection refused via JDBC
Already subscribed.. stil it doesnt goes to mail.what can i do. Coming to questn where to chnge the connection name n database n localhost to make it effect? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Connection-refused-via-JDBC-tp2490p2492.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
