Application closing after java.net.SocketTimeoutException

2020-12-21 Thread rakshita04
Hi Team,

We are using ignite for persistent data between two nodes running on
separate machines.
sometimes our application stops with below error logs and exception-
[01:18:39,477][SEVERE][tcp-disco-srvr-[:47500]-#3][TcpDiscoverySpi] Failed
to accept TCP connection.
java.net.SocketTimeoutException: Accept timed out
at java.base/java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.base/java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:458)
at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:565)
at
java.base/sun.security.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:202)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:6353)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServerThread.body(ServerImpl.java:6276)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:61)
[01:18:39,505][SEVERE][tcp-disco-srvr-[:47500]-#3][] Critical system error
detected. Will be handled accordingly to configured handler
[hnd=StopNodeOrHaltFailureHandler [tryStop=false, timeout=0,
super=AbstractFailureHandler [ignoredFailureTypes=UnmodifiableSet
[SYSTEM_WORKER_BLOCKED, SYSTEM_CRITICAL_OPERATION_TIMEOUT]]],
failureCtx=FailureContext [type=SYSTEM_WORKER_TERMINATION,
err=java.net.SocketTimeoutException: Accept timed out]]
java.net.SocketTimeoutException: Accept timed out
at java.base/java.net.PlainSocketImpl.socketAccept(Native Method)
at
java.base/java.net.AbstractPlainSocketImpl.accept(AbstractPlainSocketImpl.java:458)
at java.base/java.net.ServerSocket.implAccept(ServerSocket.java:565)
at
java.base/sun.security.ssl.SSLServerSocketImpl.accept(SSLServerSocketImpl.java:202)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServer.body(ServerImpl.java:6353)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.spi.discovery.tcp.ServerImpl$TcpServerThread.body(ServerImpl.java:6276)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:61)
[01:18:39,562][SEVERE][tcp-disco-srvr-[:47500]-#3][] JVM will be halted
immediately due to the failure: [failureCtx=FailureContext
[type=SYSTEM_WORKER_TERMINATION, err=java.net.SocketTimeoutException: Accept
timed out]]

Can you tell us why its happenning?



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: How to extracts value from json string in .Net Ignite

2020-12-21 Thread siva
Hi,

But i am facing same issue.

not sure missing any configuration?
1.added jar file in libs folder
2.added function in default config at ignite installation config directory.
3.added function in both client and server nodes xml file.

I have restarted my application .Net client and server nodes.


0: jdbc:ignite:thin://127.0.0.1/MyTemplateFun> select
Custom_Json_Value("","") foo;

Ignite console log:
  
  [2020-12-21
20:55:33,918][ERROR][client-connector-#160%ServerNode%][JdbcRequestHandler]
Failed to execute SQL query [reqId=0, req=JdbcQueryExecuteRequest
[schemaName=MYTEMPLATEFUNCTION, pageSize=1024, maxRows=0, sqlQry=select
Custom_Json_Value("","") foo, args=[], stmtType=ANY_STATEMENT_TYPE,
autoCommit=true]]
class org.apache.ignite.internal.processors.query.IgniteSQLException: Failed
to set schema for DB connection for thread [schema=MYTEMPLATEFUNCTION]
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:587)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForSchema(IgniteH2Indexing.java:414)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.querySqlFields(IgniteH2Indexing.java:2179)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2128)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor$4.applyx(GridQueryProcessor.java:2123)
at
org.apache.ignite.internal.util.lang.IgniteOutClosureX.apply(IgniteOutClosureX.java:36)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.executeQuery(GridQueryProcessor.java:2693)
at
org.apache.ignite.internal.processors.query.GridQueryProcessor.querySqlFields(GridQueryProcessor.java:2137)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.executeQuery(JdbcRequestHandler.java:511)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.doHandle(JdbcRequestHandler.java:245)
at
org.apache.ignite.internal.processors.odbc.jdbc.JdbcRequestHandler.handle(JdbcRequestHandler.java:208)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:162)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:45)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: org.h2.jdbc.JdbcSQLException: Schema "MYTEMPLATEFUNCTION" not
found; SQL statement:
SET SCHEMA "MYTEMPLATEFUNCTION" [90079-197]
at
org.h2.message.DbException.getJdbcSQLException(DbException.java:357)
at org.h2.message.DbException.get(DbException.java:179)
at org.h2.message.DbException.get(DbException.java:155)
at org.h2.engine.Database.getSchema(Database.java:1808)
at org.h2.command.dml.Set.update(Set.java:409)
at org.h2.command.CommandContainer.update(CommandContainer.java:102)
at org.h2.command.Command.executeUpdate(Command.java:261)
at
org.h2.jdbc.JdbcStatement.executeUpdateInternal(JdbcStatement.java:169)
at org.h2.jdbc.JdbcStatement.executeUpdate(JdbcStatement.java:126)
at
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:579)
... 20 more
 
Thanks.   



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: How to extracts value from json string in .Net Ignite

2020-12-21 Thread Ilya Kasnacheev
Hello!

Seems to work for me:

~/Downloads/apache-ignite-slim-2.9.0-bin% mkdir -p org/mycustomsqlfunction
~/Downloads/apache-ignite-slim-2.9.0-bin% cd org/mycustomsqlfunction
~/Downloads/apache-ignite-slim-2.9.0-bin/org/mycustomsqlfunction% cat >
MyCustomSQLFunction.java
package org.mycustomsqlfunction;

import org.apache.ignite.cache.query.annotations.QuerySqlFunction;

public class MyCustomSQLFunction {
   @QuerySqlFunction
   public static String Custom_Json_Value(String payload,String fieldName)
{
   System.out.println(payload);
   System.out.println(fieldName);
   return "Test";
   }
}%
~/Downloads/apache-ignite-slim-2.9.0-bin/org/mycustomsqlfunction% cd ../..
~/Downloads/apache-ignite-slim-2.9.0-bin% javac -cp
libs/ignite-core-2.9.0.jar:libs/ignite-indexing/ignite-indexing-2.9.0.jar:libs/ignite-indexing/h2-1.4.197.jar
org/mycustomsqlfunction/MyCustomSQLFunction.java
~/Downloads/apache-ignite-slim-2.9.0-bin% jar vcf
libs/mycustomsqlfunction.jar
org/mycustomsqlfunction/MyCustomSQLFunction.class
org/mycustomsqlfunction/MyCustomSQLFunction.class
~/Downloads/apache-ignite-slim-2.9.0-bin% vim config/default-config.xml
...
~/Downloads/apache-ignite-slim-2.9.0-bin% javac -cp
libs/ignite-core-2.9.0.jar:libs/ignite-indexing/ignite-indexing-2.9.0.jar:libs/ignite-indexing/h2-1.4.197.jar
org/mycustomsqlfunction/MyCustomSQLFunction.java
(130)~/Downloads/apache-ignite-slim-2.9.0-bin% bin/ignite.sh


~/Downloads/apache-ignite-slim-2.9.0-bin% bin/sqlline.sh
0: jdbc:ignite:thin://localhost/MyTemplateFun> !connect
jdbc:ignite:thin://localhost/"MyTemplateFunction"
Enter username for jdbc:ignite:thin://localhost/"MyTemplateFunction":
Enter password for jdbc:ignite:thin://localhost/"MyTemplateFunction":
1: jdbc:ignite:thin://localhost/"MyTemplateFu> select
custom_json_value('','') foo;
++
|  FOO   |
++
| Test   |
++
1 row selected (0,108 seconds)

Regards,
-- 
Ilya Kasnacheev


пн, 21 дек. 2020 г. в 17:39, siva :

> Hi,
>
>
> i have tried like below in both case i am getting error
>
> 1.Without cache name
>
> 0: jdbc:ignite:thin://127.0.0.1/> select Custom_Json_Value("","");
> Error: Failed to parse query. Function "CUSTOM_JSON_VALUE" not found; SQL
> statement:
> select Custom_Json_Value("","") [90022-197] (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Function "CUSTOM_JSON_VALUE"
> not found; SQL statement:
> select Custom_Json_Value("","") [90022-197]
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
>
> 2.i logged in with customfunction cache name 'MyTemplateFunction'
>
> select Custom_Json_Value("","");
>
> 0: jdbc:ignite:thin://127.0.0.1/MyTemplateFun> select
> Custom_Json_Value("","");
> Error: Failed to set schema for DB connection for thread
> [schema=MYTEMPLATEFUNCTION] (state=5,code=1)
> java.sql.SQLException: Failed to set schema for DB connection for thread
> [schema=MYTEMPLATEFUNCTION]
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/MyTemplateFun>
>
>
> Thanks.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: How to extracts value from json string in .Net Ignite

2020-12-21 Thread siva
Hi,


i have tried like below in both case i am getting error

1.Without cache name

0: jdbc:ignite:thin://127.0.0.1/> select Custom_Json_Value("","");
Error: Failed to parse query. Function "CUSTOM_JSON_VALUE" not found; SQL
statement:
select Custom_Json_Value("","") [90022-197] (state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Function "CUSTOM_JSON_VALUE"
not found; SQL statement:
select Custom_Json_Value("","") [90022-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)

2.i logged in with customfunction cache name 'MyTemplateFunction'

select Custom_Json_Value("","");

0: jdbc:ignite:thin://127.0.0.1/MyTemplateFun> select
Custom_Json_Value("","");
Error: Failed to set schema for DB connection for thread
[schema=MYTEMPLATEFUNCTION] (state=5,code=1)
java.sql.SQLException: Failed to set schema for DB connection for thread
[schema=MYTEMPLATEFUNCTION]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/MyTemplateFun>


Thanks.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: configuring DBEaver to connect to Ignite cluster with SSL enabled

2020-12-21 Thread Ilya Kasnacheev
Hello!

Looks OK. Did you also enable SSL in the ClientConnectorConfiguration?

Regards,
-- 
Ilya Kasnacheev


пн, 21 дек. 2020 г. в 16:44, Naveen :

> I did mention all these 5 properties mentioned, but still fails with the
> following message Failed to read incoming message (not enough data). Is
> there is something I am missing here Thanks
> --
> Sent from the Apache Ignite Users mailing list archive
>  at Nabble.com.
>


Re: configuring DBEaver to connect to Ignite cluster with SSL enabled

2020-12-21 Thread Naveen

I did mention all these 5 properties mentioned, but still fails with the
following messageFailed to read incoming message (not enough data).Is there
is something I am missing hereThanks



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: How to extracts value from json string in .Net Ignite

2020-12-21 Thread Ilya Kasnacheev
Hello!

I don't think that you need to qualify functions with schema name. Please
try it verbatim. You can specify default schema in the connection string,
or alternatively try to do actual select from that table:
https://ignite.apache.org/docs/latest/SQL/JDBC/jdbc-driver

Regards,
-- 
Ilya Kasnacheev


пн, 21 дек. 2020 г. в 15:40, siva :

> Hi,
> I have created and defined customsqlfunction
> IGNITE_HOME=apache-ignite-2.7.6-bin
> added Function jar at apache-ignite-2.7.6-bin\libs
>
> And added cache configuration in default-config
>  class="org.apache.ignite.configuration.IgniteConfiguration">
> 
>
>   
> 
> 
> 
>  value="org.mycustomsqlfunction.MyCustomSQLFunction"/>
>   
>
>   
> 
>
> And also added in .Net client and Server config files node like this
> 
>   
> 
>   
>   
>   
>value="org.mycustomsqlfunction.MyCustomSQLFunction"/>
> 
>   
> 
>
> *Java class file*
> package org.mycustomsqlfunction;
>
> import org.apache.ignite.cache.query.annotations.QuerySqlFunction;
>
> public class MyCustomSQLFunction {
> @QuerySqlFunction
> public static String Custom_Json_Value(String payload,String fieldName)
> {
> System.out.println(payload);
> System.out.println(fieldName);
> return "Test";
> }
> }
>
> But while running query getting error column not found:
>
> 0: jdbc:ignite:thin://127.0.0.1/> select
> "MyTemplateFunction".Custom_Json_Value("","");
> Error: Failed to parse query. Column  not found; SQL statement:
> select "MyTemplateFunction".Custom_Json_Value("","") [42122-197]
> (state=42000,code=1001)
> java.sql.SQLException: Failed to parse query. Column  not found; SQL
> statement:
> select "MyTemplateFunction".Custom_Json_Value("","") [42122-197]
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
> at
>
> org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
> at sqlline.Commands.execute(Commands.java:823)
> at sqlline.Commands.sql(Commands.java:733)
> at sqlline.SqlLine.dispatch(SqlLine.java:795)
> at sqlline.SqlLine.begin(SqlLine.java:668)
> at sqlline.SqlLine.start(SqlLine.java:373)
> at sqlline.SqlLine.main(SqlLine.java:265)
> 0: jdbc:ignite:thin://127.0.0.1/>
>
> what am i doing wrong.please help.
> Thanks.
>
>
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


RE: Getting error Node is out of topology (probably, due to short-time network problems)

2020-12-21 Thread BEELA GAYATRI
Hi Igor,

We have Observed the CPU and memory  utilizations on the servers where 
these nodes are running and the CPU utilizations are very less . Still we are 
observing the issue (sometimes we are getting jvm pauses after that node is 
getting out of topology, sometimes without jvm pauses  node is getting out of 
topology)

Sent from Mail for Windows 10

From: ibelyakov
Sent: Tuesday, December 15, 2020 9:19 PM
To: user@ignite.apache.org
Subject: RE: Getting error Node is out of topology (probably, due to short-time 
network problems)

"External email. Open with Caution"

Hi,

According to the provided GC logs I don't see anything suspicious.

Do you run Ignite nodes on VMs? If yes, do you have monitoring and is it
possible to check CPU usage during period of time when the issue happend?

Regards,
Igor



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

=-=-=
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you




Re: How to extracts value from json string in .Net Ignite

2020-12-21 Thread siva
Hi,
I have created and defined customsqlfunction 
IGNITE_HOME=apache-ignite-2.7.6-bin
added Function jar at apache-ignite-2.7.6-bin\libs

And added cache configuration in default-config


   
  




  
   
  


And also added in .Net client and Server config files node like this

  

  
  
  
  

  


*Java class file*
package org.mycustomsqlfunction;

import org.apache.ignite.cache.query.annotations.QuerySqlFunction;

public class MyCustomSQLFunction {
@QuerySqlFunction
public static String Custom_Json_Value(String payload,String fieldName)
{
System.out.println(payload);
System.out.println(fieldName);
return "Test";
}
}

But while running query getting error column not found:

0: jdbc:ignite:thin://127.0.0.1/> select
"MyTemplateFunction".Custom_Json_Value("","");
Error: Failed to parse query. Column  not found; SQL statement:
select "MyTemplateFunction".Custom_Json_Value("","") [42122-197]
(state=42000,code=1001)
java.sql.SQLException: Failed to parse query. Column  not found; SQL
statement:
select "MyTemplateFunction".Custom_Json_Value("","") [42122-197]
at
org.apache.ignite.internal.jdbc.thin.JdbcThinConnection.sendRequest(JdbcThinConnection.java:750)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute0(JdbcThinStatement.java:212)
at
org.apache.ignite.internal.jdbc.thin.JdbcThinStatement.execute(JdbcThinStatement.java:475)
at sqlline.Commands.execute(Commands.java:823)
at sqlline.Commands.sql(Commands.java:733)
at sqlline.SqlLine.dispatch(SqlLine.java:795)
at sqlline.SqlLine.begin(SqlLine.java:668)
at sqlline.SqlLine.start(SqlLine.java:373)
at sqlline.SqlLine.main(SqlLine.java:265)
0: jdbc:ignite:thin://127.0.0.1/>

what am i doing wrong.please help.
Thanks.





--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/


Re: not able to change keyspace name when Using 3rd Party Persistence (Cassandra) Together with Ignite Native Persistence

2020-12-21 Thread Ilya Kasnacheev
Hello!

I think that maybe you could try coding such a cache store which will
update this information. It's just that the default Cassandra store doesn't
seem to.

Regards,
-- 
Ilya Kasnacheev


сб, 19 дек. 2020 г. в 05:17, xmw45688 :

> Thanks for your confirmation, Ilya.
>
> I do have a follow-up question for you.
> When Ignite Persistence is used together with Cassandra.  The caches for
> Cassandra table mappings are provided via xml file.  The java class for the
> mappings is for BOTH Ignite Persistence and Cassandra cache store.  When a
> table is changed, the mapping class gets changed, and the cluster is
> started. Why is Ignite Persistence able to use this updated java class
> (added/removed variables from the class) to insert/update data into Ignite
> Persistence stores.  But for Cassandra Store, it appears to use the old
> definition of class.  For this case, what's effort if we want to use the
> new
> class of definition?  Do you think that it's reasonable to read the cache
> configuration (i.e. via xml) dynamically for 3rd party Cache store which
> does if the 3rd party store is used along.  I'm not an expert in java, I
> can
> definitely help (or find a resource to do it) to improve this request.
>
> Pleas let me know if I can submit a feature request.
>
> Appreciate your help.
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>


Re: configuring DBEaver to connect to Ignite cluster with SSL enabled

2020-12-21 Thread Ilya Kasnacheev
Hello!

You just need to set the following connection properties in dbeaver's
connection settings:

https://ignite.apache.org/docs/latest/SQL/JDBC/jdbc-driver

sslMode

Enables SSL connection. Available modes:

   -

   require: SSL protocol is enabled on the client. Only SSL connection is
   available.
   -

   disable: SSL protocol is disabled on the client. Only plain connection
   is supported.

sslClientCertificateKeyStoreUrl

URL of the client key store file. This is a mandatory parameter since SSL
context cannot be initialized without a key manager. If sslMode is require
and the key store URL isn’t specified in the Ignite properties, the value
of the JSSE property javax.net.ssl.keyStore is used.

sslClientCertificateKeyStorePassword

Client key store password.

If sslMode is require and the key store password isn’t specified in the
Ignite properties, the JSSE property javax.net.ssl.keyStorePassword is used.

sslTrustCertificateKeyStoreUrl

URL of the trust store file. This is an optional parameter; however, one of
these properties must be set: sslTrustCertificateKeyStoreUrl or sslTrustAll

If sslMode is require and the trust store URL isn’t specified in the Ignite
properties, the JSSE property javax.net.ssl.trustStore is used.

sslTrustCertificateKeyStorePassword

Trust store password.

If sslMode is require and the trust store password isn’t specified in the
Ignite properties, the JSSE property javax.net.ssl.trustStorePassword is
used.

Regards,
-- 
Ilya Kasnacheev


вс, 20 дек. 2020 г. в 16:06, Naveen :

> Hi
>
> Any pointers towards this
> Not finding any option on DBEaver tool to configure SSL certificates,
> Does DBEaver support configuring Ingite cluster enabled with SSL
>
> Thanks
> Naveen
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
>