Re: [wsjt-devel] Yaesu FT-991 tx forces USB mode

mode in WSJT-X rigs settings to Data/Pkt doesn't work? > > Mike W9MDB > > > > > > On Thursday, August 27, 2020, 02:15:45 PM CDT, Alexey Popov < > alexeuspo...@gmail.com> wrote: > > > Hi all! > > I have some trouble. > My Yaesu FT-991 connected

[wsjt-devel] Yaesu FT-991 tx forces USB mode

tton in the main window, the transceiver changes mode to USB. Can I change behavior to use device selected mode? Or select preferred mode in application? -- Alexey Popov ___ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[jira] [Created] (IGNITE-8127) .NET: Fix flaky test ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress

Alexey Popov created IGNITE-8127: Summary: .NET: Fix flaky test ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress Key: IGNITE-8127 URL: https://issues.apache.org/jira/browse/IGNITE-8127

[jira] [Updated] (IGNITE-8127) .NET: Fix flaky test ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress

[ https://issues.apache.org/jira/browse/IGNITE-8127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-8127: - Labels: MakeTeamcityGreenAgain (was: ) > .NET: Fix flaky t

[jira] [Created] (IGNITE-8127) .NET: Fix flaky test ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress

Alexey Popov created IGNITE-8127: Summary: .NET: Fix flaky test ClientConnectionTest.TestClientDisposeWhileOperationsAreInProgress Key: IGNITE-8127 URL: https://issues.apache.org/jira/browse/IGNITE-8127

[jira] [Issue Comment Deleted] (IGNITE-8108) .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup

[ https://issues.apache.org/jira/browse/IGNITE-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-8108: - Comment: was deleted (was: [~dpavlov], please review & commit) > .NET: Fi

[jira] [Commented] (IGNITE-8108) .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup

[ https://issues.apache.org/jira/browse/IGNITE-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422622#comment-16422622 ] Alexey Popov commented on IGNITE-8108: -- [~dpavlov], please review & commit

[jira] [Commented] (IGNITE-8108) .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup

[ https://issues.apache.org/jira/browse/IGNITE-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422546#comment-16422546 ] Alexey Popov commented on IGNITE-8108: -- TC run: https://ci.ignite.apache

[jira] [Commented] (IGNITE-8108) .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup

[ https://issues.apache.org/jira/browse/IGNITE-8108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16422544#comment-16422544 ] Alexey Popov commented on IGNITE-8108: -- Changes: 1. Fixed test with def

[jira] [Created] (IGNITE-8108) .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup

Alexey Popov created IGNITE-8108: Summary: .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup Key: IGNITE-8108 URL: https://issues.apache.org/jira/browse/IGNITE-8108

[jira] [Created] (IGNITE-8108) .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup

Alexey Popov created IGNITE-8108: Summary: .NET: Fix flaky EntityFrameworkCacheInitializationTest.TestConfigurationAndStartup Key: IGNITE-8108 URL: https://issues.apache.org/jira/browse/IGNITE-8108

[jira] [Comment Edited] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411168#comment-16411168 ] Alexey Popov edited comment on IGNITE-7928 at 3/26/18 1:2

[jira] [Updated] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7928: - Fix Version/s: 2.5 > .NET: Exception is not propagated to the C# client and the app ha

[jira] [Comment Edited] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411168#comment-16411168 ] Alexey Popov edited comment on IGNITE-7928 at 3/23/18 3:2

[jira] [Commented] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411534#comment-16411534 ] Alexey Popov commented on IGNITE-7928: -- [~vozerov], [~ptupitsyn], please review

[jira] [Comment Edited] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411168#comment-16411168 ] Alexey Popov edited comment on IGNITE-7928 at 3/23/18 3:0

[jira] [Commented] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16411168#comment-16411168 ] Alexey Popov commented on IGNITE-7928: -- https://ci.ignite.apache.org/viewType.

Re: .Net ICacheEntryFilter

Hi, Can you share a simple reproducer project for [InstanceResource] within ICacheEntryFilter? I can't find unit tests for that case in Apache Ignite source code. > but the field _ignite is null and we have no access to cache to get it. That sounds like a bug that should be fixed. Thanks, Alex

[jira] [Updated] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7928: - Labels: .NET (was: ) > .NET: Exception is not propagated to the C# client and the app ha

[jira] [Updated] (IGNITE-7928) .NET: Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7928: - Summary: .NET: Exception is not propagated to the C# client and the app hangs (was: Exception

[jira] [Assigned] (IGNITE-7928) Exception is not propagated to the C# client and the app hangs

[ https://issues.apache.org/jira/browse/IGNITE-7928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov reassigned IGNITE-7928: Assignee: Alexey Popov > Exception is not propagated to the C# client and the app ha

[jira] [Assigned] (IGNITE-7902) Enable either swap space or persistence but not both

[ https://issues.apache.org/jira/browse/IGNITE-7902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov reassigned IGNITE-7902: Assignee: (was: Ivan Rakov) > Enable either swap space or persistence but not b

[jira] [Updated] (IGNITE-7771) Names of Ignite JMX beans should not be quoted unless required

[ https://issues.apache.org/jira/browse/IGNITE-7771?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7771: - Affects Version/s: 2.4 > Names of Ignite JMX beans should not be quoted unless requi

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

Hi Yakov, Do the proposed changes look good to you? Thanks, Alexey -- Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/

[jira] [Updated] (IGNITE-7824) Rollback part of IGNITE-7170 changes

[ https://issues.apache.org/jira/browse/IGNITE-7824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7824: - Labels: newbie (was: ) > Rollback part of IGNITE-7170 chan

[jira] [Updated] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7851: - Fix Version/s: 2.5 > .NET: linq query throws "Hexadecimal string with odd number of ch

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16389330#comment-16389330 ] Alexey Popov commented on IGNITE-7851: -- TC results are green. h

[jira] [Updated] (IGNITE-7889) .NET: linq GroupBy and Where do not work together

[ https://issues.apache.org/jira/browse/IGNITE-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7889: - Fix Version/s: 2.5 > .NET: linq GroupBy and Where do not work toget

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388030#comment-16388030 ] Alexey Popov commented on IGNITE-7851: -- changes done, waiting for TC run &g

[jira] [Updated] (IGNITE-7889) .NET: linq GroupBy and Where do not work together.

[ https://issues.apache.org/jira/browse/IGNITE-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7889: - Summary: .NET: linq GroupBy and Where do not work together. (was: .NET: linq GroupBy and Where

[jira] [Commented] (IGNITE-7889) .NET: linq GroupBy and Where does not work together.

[ https://issues.apache.org/jira/browse/IGNITE-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387886#comment-16387886 ] Alexey Popov commented on IGNITE-7889: -- TC run: https://ci.ignite.apache

[jira] [Commented] (IGNITE-7889) .NET: linq GroupBy and Where does not work together.

[ https://issues.apache.org/jira/browse/IGNITE-7889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387877#comment-16387877 ] Alexey Popov commented on IGNITE-7889: -- Changes: 1. Unit test is added 2. Fi

[jira] [Created] (IGNITE-7889) .NET: linq GroupBy and Where does not work together.

Alexey Popov created IGNITE-7889: Summary: .NET: linq GroupBy and Where does not work together. Key: IGNITE-7889 URL: https://issues.apache.org/jira/browse/IGNITE-7889 Project: Ignite Issue

[jira] [Created] (IGNITE-7889) .NET: linq GroupBy and Where does not work together.

Alexey Popov created IGNITE-7889: Summary: .NET: linq GroupBy and Where does not work together. Key: IGNITE-7889 URL: https://issues.apache.org/jira/browse/IGNITE-7889 Project: Ignite Issue

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387717#comment-16387717 ] Alexey Popov commented on IGNITE-7851: -- Discussed with [~vozerov]. It was dec

[jira] [Created] (IGNITE-7888) ODBC: Add support for SQL_ATTR_LOGIN_TIMEOUT

Alexey Popov created IGNITE-7888: Summary: ODBC: Add support for SQL_ATTR_LOGIN_TIMEOUT Key: IGNITE-7888 URL: https://issues.apache.org/jira/browse/IGNITE-7888 Project: Ignite Issue Type

[jira] [Created] (IGNITE-7888) ODBC: Add support for SQL_ATTR_LOGIN_TIMEOUT

Alexey Popov created IGNITE-7888: Summary: ODBC: Add support for SQL_ATTR_LOGIN_TIMEOUT Key: IGNITE-7888 URL: https://issues.apache.org/jira/browse/IGNITE-7888 Project: Ignite Issue Type

Re: IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

Yakov, 1. The proposal list of parameters to deprecate: TcpDiscoverySpi.setConnectTimeout (covered by IgniteConfiguration.setFailureDetectionTimeout) TcpDiscoverySpi.setReconnectCount (covered by IgniteConfiguration.setFailureDetectionTimeout) TcpDiscoverySpi.setSocketTimeout (covered by IgniteCon

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16387436#comment-16387436 ] Alexey Popov commented on IGNITE-7851: -- [~ptupitsyn], ok got it. Why do we

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16386075#comment-16386075 ] Alexey Popov commented on IGNITE-7851: -- [~ptupitsyn] Could you please revie

[jira] [Resolved] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov resolved IGNITE-7851. -- Resolution: Fixed > .NET: linq query throws "Hexadecimal string with odd number of ch

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383458#comment-16383458 ] Alexey Popov commented on IGNITE-7851: -- TC run: https://ci.ignite.apache

[jira] [Commented] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383412#comment-16383412 ] Alexey Popov commented on IGNITE-7851: -- [~isapego], [~skalashnikov] Please re

[jira] [Assigned] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

[ https://issues.apache.org/jira/browse/IGNITE-7851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov reassigned IGNITE-7851: Assignee: Alexey Popov > .NET: linq query throws "Hexadecimal string with odd n

IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts

Hi Igniters, We often see similar questions from users and customers related to IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations. And we see several side-effects after incorrect timeout configuration. I tried to briefly describe these timeout settings (please

[jira] [Comment Edited] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

[ https://issues.apache.org/jira/browse/IGNITE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363879#comment-16363879 ] Alexey Popov edited comment on IGNITE-7704 at 3/1/18 1:3

[jira] [Created] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

Alexey Popov created IGNITE-7851: Summary: .NET: linq query throws "Hexadecimal string with odd number of characters" exception Key: IGNITE-7851 URL: https://issues.apache.org/jira/browse/I

[jira] [Created] (IGNITE-7851) .NET: linq query throws "Hexadecimal string with odd number of characters" exception

Alexey Popov created IGNITE-7851: Summary: .NET: linq query throws "Hexadecimal string with odd number of characters" exception Key: IGNITE-7851 URL: https://issues.apache.org/jira/browse/I

[jira] [Created] (IGNITE-7824) Rollback part of IGNITE-7170 changes

Alexey Popov created IGNITE-7824: Summary: Rollback part of IGNITE-7170 changes Key: IGNITE-7824 URL: https://issues.apache.org/jira/browse/IGNITE-7824 Project: Ignite Issue Type: Bug

[jira] [Created] (IGNITE-7824) Rollback part of IGNITE-7170 changes

Alexey Popov created IGNITE-7824: Summary: Rollback part of IGNITE-7170 changes Key: IGNITE-7824 URL: https://issues.apache.org/jira/browse/IGNITE-7824 Project: Ignite Issue Type: Bug

[jira] [Resolved] (IGNITE-6551) .NET: NPE in PlatformDotNetCacheStore on Java-only nodes

[ https://issues.apache.org/jira/browse/IGNITE-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov resolved IGNITE-6551. -- Resolution: Cannot Reproduce Already fixed by IGNITE-2967. Could not be reproduced > .

[jira] [Commented] (IGNITE-7191) JDBC: set socket buffer to 64k by default

[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16366954#comment-16366954 ] Alexey Popov commented on IGNITE-7191: -- No improvement is observed. Closing

[jira] [Updated] (IGNITE-7720) Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration

[ https://issues.apache.org/jira/browse/IGNITE-7720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov updated IGNITE-7720: - Description: https://apacheignite-sql.readme.io/docs/odbc-driver#section-cluster-configuration

[jira] [Created] (IGNITE-7720) Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration

Alexey Popov created IGNITE-7720: Summary: Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration Key: IGNITE-7720 URL: https://issues.apache.org/jira/browse/IGNITE-7720

[jira] [Created] (IGNITE-7720) Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration

Alexey Popov created IGNITE-7720: Summary: Update ODBC cluster configuration: replace OdbcConfiguration with ClientConnectorConfiguration Key: IGNITE-7720 URL: https://issues.apache.org/jira/browse/IGNITE-7720

[jira] [Created] (IGNITE-7705) DIscoverySpi should inherit networkTimeout from IgniteConfiguration

Alexey Popov created IGNITE-7705: Summary: DIscoverySpi should inherit networkTimeout from IgniteConfiguration Key: IGNITE-7705 URL: https://issues.apache.org/jira/browse/IGNITE-7705 Project: Ignite

[jira] [Created] (IGNITE-7705) DIscoverySpi should inherit networkTimeout from IgniteConfiguration

Alexey Popov created IGNITE-7705: Summary: DIscoverySpi should inherit networkTimeout from IgniteConfiguration Key: IGNITE-7705 URL: https://issues.apache.org/jira/browse/IGNITE-7705 Project: Ignite

[jira] [Comment Edited] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

[ https://issues.apache.org/jira/browse/IGNITE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363879#comment-16363879 ] Alexey Popov edited comment on IGNITE-7704 at 2/14/18 1:5

[jira] [Comment Edited] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

[ https://issues.apache.org/jira/browse/IGNITE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363879#comment-16363879 ] Alexey Popov edited comment on IGNITE-7704 at 2/14/18 1:3

[jira] [Commented] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

[ https://issues.apache.org/jira/browse/IGNITE-7704?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16363879#comment-16363879 ] Alexey Popov commented on IGNITE-7704: -- Sample descrip

[jira] [Created] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

Alexey Popov created IGNITE-7704: Summary: Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations Key: IGNITE-7704 URL: https://issues.apache.org/jira/browse/IGNITE-7704

[jira] [Created] (IGNITE-7704) Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations

Alexey Popov created IGNITE-7704: Summary: Document IgniteConfiguration, TcpDiscoverySpi, TcpCommunicationSpi timeouts and their relations Key: IGNITE-7704 URL: https://issues.apache.org/jira/browse/IGNITE-7704

Re: Logging using Log4Net

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

Re: Logging using Log4Net

Hi, Hm, actually, you've got several log4net misconfigurations in your solution. Everything was fine with Ignite config itself ). Please see updated minified solution attached. Just "build a solution" and it will restore all required packages. The following log4net misconfigurations fixed: 1. Yo

[jira] [Comment Edited] (IGNITE-3111) .NET: Configure SSL without Spring

[ https://issues.apache.org/jira/browse/IGNITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360365#comment-16360365 ] Alexey Popov edited comment on IGNITE-3111 at 2/13/18 10:5

Re: Logging using Log4Net

Hi, There could be several issues. Unfortunately, you just provided some config snippets. First of all, please add to your appender RollingLogFileAppender config. Then, please ensure that your log4net configuration section is actually used. It is better to have a separate file log4net.config f

[jira] [Commented] (IGNITE-3111) .NET: Configure SSL without Spring

[ https://issues.apache.org/jira/browse/IGNITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16360365#comment-16360365 ] Alexey Popov commented on IGNITE-3111: -- [~isapego] , fixed. Now we have

[jira] [Commented] (IGNITE-3111) .NET: Configure SSL without Spring

[ https://issues.apache.org/jira/browse/IGNITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358411#comment-16358411 ] Alexey Popov commented on IGNITE-3111: -- [~ptupitsyn] , please have a look ) &g

[jira] [Commented] (IGNITE-3111) .NET: Configure SSL without Spring

[ https://issues.apache.org/jira/browse/IGNITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358334#comment-16358334 ] Alexey Popov commented on IGNITE-3111: -- https://ci.ignite.apache.org/project.

[jira] [Commented] (IGNITE-3111) .NET: Configure SSL without Spring

[ https://issues.apache.org/jira/browse/IGNITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16358325#comment-16358325 ] Alexey Popov commented on IGNITE-3111: -- [~skalashnikov] ,[~isapego] , please re

[jira] [Assigned] (IGNITE-3111) .NET: Configure SSL without Spring

[ https://issues.apache.org/jira/browse/IGNITE-3111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov reassigned IGNITE-3111: Assignee: Alexey Popov > .NET: Configure SSL without Spr

[jira] [Created] (IGNITE-7627) Introduce a new eviction policy to avoid eviction of Index pages

Alexey Popov created IGNITE-7627: Summary: Introduce a new eviction policy to avoid eviction of Index pages Key: IGNITE-7627 URL: https://issues.apache.org/jira/browse/IGNITE-7627 Project: Ignite

[jira] [Created] (IGNITE-7627) Introduce a new eviction policy to avoid eviction of Index pages

Alexey Popov created IGNITE-7627: Summary: Introduce a new eviction policy to avoid eviction of Index pages Key: IGNITE-7627 URL: https://issues.apache.org/jira/browse/IGNITE-7627 Project: Ignite

[jira] [Commented] (IGNITE-7598) SQL: INSERT requires you to specify the column names even if you are adding values for all the columns of the table

[ https://issues.apache.org/jira/browse/IGNITE-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16348182#comment-16348182 ] Alexey Popov commented on IGNITE-7598: -- Please have a look at h

[jira] [Assigned] (IGNITE-6551) .NET: NPE in PlatformDotNetCacheStore on Java-only nodes

[ https://issues.apache.org/jira/browse/IGNITE-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov reassigned IGNITE-6551: Assignee: Alexey Popov > .NET: NPE in PlatformDotNetCacheStore on Java-only no

[jira] [Commented] (IGNITE-7191) JDBC: set socket buffer to 64k by default

[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16332465#comment-16332465 ] Alexey Popov commented on IGNITE-7191: -- [~ptupitsyn] , I run some benchmarks

Re: Remote client

Hi, Does your remote client has public IP? Please note that client node should be accessible for TCP incoming connections from a server node, i.e. the server node should be able to connect to client IP as well. Your client IP is 192.168.8.132. And your server node is not able to connect it. So

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi Larry, I checked the code. The issue is specific to your test data. You have relatively large initial entries (4.7 Kbytes) with the same index length (it is a just String). Please note that the index can't fit into the single page (4K). The rest of entries during .get() (from Store) are relati

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi Larry, I am without my PC for a while. I will check the file you attached later this week. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite best practice

Hi Sergey, There could not be an exact answer to your question. It depends mostly on your use-case. 1. first of all, you should look at CPU/mem/network usage 2. and then you should check SQL debugging guide, starting from EXPLAIN for your query. Please see [1] for details. 3. you could enable dat

Re: No user-defined default MemoryPolicy found

I checked the code Actually, you can ignore this warning ("WARNING: No user-defined default MemoryPolicy found; system default of 1GB size will be used."). Apache Ignite applies your defaultMemoryPolicySize Or you can change your config to avoid such warning:

Re: Use SQL to query IgniteRDD with scala at Zeppelin

Hi, Please note that REST protocol puts keys as String. So you have 3 Integer keys and 1 String key in a cache. That is the reason for your results. You can find details in topic [1] [1] http://apache-ignite-users.70518.x6.nabble.com/Rest-API-PUT-command-syntax-tc19158.html Thank you, Alexey

RE: failed to find sql table for type:

Hi, Do you still have this issue? Can you share your code? Ignite.NET solution has a QueryExample.cs, you can use it as a reference code. Thank you, Alexey From: kenn_thomp...@qat.com Sent: Wednesday, January 10, 2018 5:56 PM To: user@ignite.apache.org Subject: failed to find sql table for typ

Re: off heap memory usage

Hi Colin, You should use TotalAllocatedPages if you have persistence disabled. There is an know issue with PhysicalMemoryPages: https://issues.apache.org/jira/browse/IGNITE-6963 Thank you, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, You are right, "evicts=0" is related to cache evictions for on-heap caching [1]. It should be always 0 for you. I tried your case (with the same configs as you) and page evictions work fine with cache store enabled and indexed types. It seems that you have some misconfiguration. What are yo

RE: No user-defined default MemoryPolicy found

Hi, Please have a look at topic below to get an estimation of memory usage: http://apache-ignite-users.70518.x6.nabble.com/off-heap-memory-usage-tc19282.html I will check the warning later, it looks strange to me. Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No user-defined default MemoryPolicy found

ok. I see you are at 2.1. (migrating from 2.1 to 2.3) -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: No user-defined default MemoryPolicy found

Hi, I see the same message with 2.1 release. 2.3 does not have it. I will check 2.1 source code later. Do you use 2.1 release? Thanks, Alexey -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/

[jira] [Commented] (IGNITE-7191) JDBC: set socket buffer to 64k by default

[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322235#comment-16322235 ] Alexey Popov commented on IGNITE-7191: -- [~ptupitsyn] and [~tledkov-gridgain], c

[jira] [Comment Edited] (IGNITE-7191) JDBC: set socket buffer to 64k by default

[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322232#comment-16322232 ] Alexey Popov edited comment on IGNITE-7191 at 1/11/18 1:5

[jira] [Commented] (IGNITE-7191) JDBC: set socket buffer to 64k by default

[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322232#comment-16322232 ] Alexey Popov commented on IGNITE-7191: -- Scope of changes: 1. Server side def

[jira] [Comment Edited] (IGNITE-7191) JDBC: set socket buffer to 64k by default

[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16322232#comment-16322232 ] Alexey Popov edited comment on IGNITE-7191 at 1/11/18 1:5

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, Can you share your configuration for 1) cache 2) memory region? I see "evicts=0" in your stats that looks very strange. Are you sure you have a configured eviction policy in the data region (policyName=RefData)? Does this cache work fine (evicts some data) without Cache Store enabled? Thank

Re: Adding custom processor in Ignite Node

Hi, I am not sure that user-list will be able to help you with such questions. You should discuss the implementation options/details at dev-list (http://apache-ignite-developers.2346864.n4.nabble.com/). Probably, you don't need a custom processor class at all. Anyway: 1. Please have a look at th

[jira] [Assigned] (IGNITE-7191) JDBC: set socket buffer to 64k by default

[ https://issues.apache.org/jira/browse/IGNITE-7191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexey Popov reassigned IGNITE-7191: Assignee: Alexey Popov > JDBC: set socket buffer to 64k by defa

[jira] [Commented] (IGNITE-6946) Change Ignite Logger configuration on the fly

[ https://issues.apache.org/jira/browse/IGNITE-6946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16320344#comment-16320344 ] Alexey Popov commented on IGNITE-6946: -- Could be added to: https://cwiki.apache

Re: IgniteOutOfMemoryException when using putAll instead of put

Hi, You are right, cache.putAll() can't evict the entries from the batch it is working on, and you can get Ignite OOME. This is expected behavior because putAll get locks for all provided entry keys. That is critical: 1) for transactional caches and 2) any caches backed up by 3-rd party persisten

Re: ClassCastException using cache and continuous query

Hi Diego, It seems that your error is related to different class Loaders being used. I don't have an idea why this happens but please try to clean your "work" directory in Ignite home (IGNITE_HOME) after 1.8 -> 2.3 upgrade or set up a new IGNITE_HOME. Please share you node configs and IgniteFet

Re: Creating multiple Ignite grids on same machine

Hi Raymond, In your case you should configure: 1. different TcpDiscoverySpi local ports 2. different ports for TcpDiscoveryVmIpFinder (Vm = Static for .NET). You should not use a default ipFinder. 3. different TcpCommunicationSpi local ports Please see sample Java xml-configs as a reference samp

RE: Why does Ignite de-allocate memory regions ONLY during shutdown?

Hi John, Could you please re-phrase you question. What issue are you trying to solve? Probably, you should address your question directly to dev-list. Anyway, you can read about memory region architecture at [1] and [2]. Hope it helps. [1] https://apacheignite.readme.io/docs/memory-architectu

  1   2   3   4   5   6   7   8   9   10   >