[jira] [Created] (IGNITE-12083) Change release scripts according pre-build DEB/RPM folders
Dmitriy Pavlov created IGNITE-12083: --- Summary: Change release scripts according pre-build DEB/RPM folders Key: IGNITE-12083 URL: https://issues.apache.org/jira/browse/IGNITE-12083 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Fix For: 2.7.6 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12082) Automate version assignment to pre-build DEB/RPM or describe how to set packages version to RC version
Dmitriy Pavlov created IGNITE-12082: --- Summary: Automate version assignment to pre-build DEB/RPM or describe how to set packages version to RC version Key: IGNITE-12082 URL: https://issues.apache.org/jira/browse/IGNITE-12082 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Fix For: 2.7.6 https://ci.ignite.apache.org/viewLog.html?buildTypeId=Releases_ApacheIgniteMain_ReleaseBuild=4513186_Releases_ApacheIgniteMain_ReleaseBuild=ignite-2.7.6 RC 0 for 2.7.6. the build was successful, but versions for packages remain unchanged https://cwiki.apache.org/confluence/display/IGNITE/Release+Process does not require Release manager to update versions, but pre-build DEB & RPM keeps version from previous release. We need to add a new step https://cwiki.apache.org/confluence/display/IGNITE/Release+Process#ReleaseProcess-4.1.Updatereleasebranchversionsandyearincopyrightmessages e.g. 4.1.4, where will ask a release manager to update versions. May be similar with commit https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=84c2dac5103a448bdaee88cb8290fd6e05a435bb -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12077) Improve Checkstyle or other inspections profile to avoid using GG- reference in Ignite code base
Dmitriy Pavlov created IGNITE-12077: --- Summary: Improve Checkstyle or other inspections profile to avoid using GG- reference in Ignite code base Key: IGNITE-12077 URL: https://issues.apache.org/jira/browse/IGNITE-12077 Project: Ignite Issue Type: Test Reporter: Dmitriy Pavlov Time to time tests are Ignored or todo added with reference to GG- tickets " For example here https://github.com/apache/ignite/pull/6748/files#diff-2dd1dad039cddd36610c62a3dc2c1a28R223 It is suggested to add some inspection check on TC to reject patches if there is a line containing: - ": //ggsystems.atlassian.net/" - or at the same time Ignore or todo and "GG- [0-9] *" -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12071) Test failures after IGNITE-9562 fix
Dmitriy Pavlov created IGNITE-12071: --- Summary: Test failures after IGNITE-9562 fix Key: IGNITE-12071 URL: https://issues.apache.org/jira/browse/IGNITE-12071 Project: Ignite Issue Type: Test Reporter: Dmitriy Pavlov Assignee: Eduard Shangareev Fix For: 2.7.6 https://lists.apache.org/thread.html/94424a86283ba720a9ebcff37adc4782d271a07bc6470e148b57a715@%3Cdev.ignite.apache.org%3E Unfortunately, since https://issues.apache.org/jira/browse/IGNITE-9562 is planned to the 2.7.6 it is a blocker for the release *New test failure in master-nightly DiskPageCompressionConfigValidationTest.testIncorrectStaticCacheConfiguration https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2692660105095122533=%3Cdefault%3E=testDetails *New test failure in master-nightly DiskPageCompressionConfigValidationTest.testIncorrectDynamicCacheStartRequest https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1915110918646717850=%3Cdefault%3E=testDetails Changes may lead to failure were done by - eduard shangareev https://ci.ignite.apache.org/viewModification.html?modId=889258 -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-12010) [TC Bot] Consider newly contributed test as blocker if it runs more that 1 minute.
Dmitriy Pavlov created IGNITE-12010: --- Summary: [TC Bot] Consider newly contributed test as blocker if it runs more that 1 minute. Key: IGNITE-12010 URL: https://issues.apache.org/jira/browse/IGNITE-12010 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Long-running tests should be scaled by the scale factor, and/or moved to Run All nightly -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11994) [TC Bot] Prepare new view to select base branch and other build parameters
Dmitriy Pavlov created IGNITE-11994: --- Summary: [TC Bot] Prepare new view to select base branch and other build parameters Key: IGNITE-11994 URL: https://issues.apache.org/jira/browse/IGNITE-11994 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov New view required for reports view and for VISAs creation for non-standard master branches, additional features may be contributed to this new view later -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11975) Fix Ignite Examples on site - Data Grid feature, how to start
Dmitriy Pavlov created IGNITE-11975: --- Summary: Fix Ignite Examples on site - Data Grid feature, how to start Key: IGNITE-11975 URL: https://issues.apache.org/jira/browse/IGNITE-11975 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov https://ignite.apache.org/features/datagrid.html Contains several examples, which won't compile -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Created] (IGNITE-11962) [TC Bot] Test threated as recently contributed even if there were runs outside 21 days
Dmitriy Pavlov created IGNITE-11962: --- Summary: [TC Bot] Test threated as recently contributed even if there were runs outside 21 days Key: IGNITE-11962 URL: https://issues.apache.org/jira/browse/IGNITE-11962 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Before notifying about recently contributed test it is necessary to double-check - if there were runs outside 21 days limit - if test failures count is not equal to the suite execution count - every time test was executed, the suite was executed as well (this may protect from flaking appearing-disappearing tests init errors). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11947) [TC Bot] New failures notification are absent for several new failures
Dmitriy Pavlov created IGNITE-11947: --- Summary: [TC Bot] New failures notification are absent for several new failures Key: IGNITE-11947 URL: https://issues.apache.org/jira/browse/IGNITE-11947 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Notifications to email are missed sometimes. One possible reason is buildStartTs, which was not filled correctly in Issue, but after fix https://github.com/apache/ignite-teamcity-bot/commit/5573467d04eedbe9f79dd2b19e9675b76af78985 the situation is still the same, notifications not send -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11932) Follow ASF crypto process, declare encryption software usaged
Dmitriy Pavlov created IGNITE-11932: --- Summary: Follow ASF crypto process, declare encryption software usaged Key: IGNITE-11932 URL: https://issues.apache.org/jira/browse/IGNITE-11932 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov https://www.apache.org/dev/crypto.html We need to update https://svn.apache.org/repos/asf/infrastructure/site/trunk/content/licenses/exports/index.page/eccnmatrix.xml And inform users by including crypto notice -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11896) [TC Bot] Comment JIRA may not work for case aliased TC is used
Dmitriy Pavlov created IGNITE-11896: --- Summary: [TC Bot] Comment JIRA may not work for case aliased TC is used Key: IGNITE-11896 URL: https://issues.apache.org/jira/browse/IGNITE-11896 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov 'Comment JIRA' will not work for PR -less contribution in pr.html report -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11880) [TC Bot] Configurable notifications by build parameters/suite IDS & names
Dmitriy Pavlov created IGNITE-11880:
---
Summary: [TC Bot] Configurable notifications by build
parameters/suite IDS & names
Key: IGNITE-11880
URL: https://issues.apache.org/jira/browse/IGNITE-11880
Project: Ignite
Issue Type: Improvement
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
Support tagging build by custom rules, not only by build parameters, e.g. suite
name
Support configuring custom notification channels by tags present in suite.
Special filtering parameters option for Tc configuration now can be used for
filtering build and tagging it.
{noformat}
"filteringParameters": [
{
"name": "env.JAVA_HOME",
"selection": [
{"value":"%env.JDK_ORA_18%", "label":"JDK8"},
{"value":"%env.JDK_ORA_9%", "label":"JDK9"},
{"value":"%env.JDK_ORA_10%", "label":"JDK10"},
{"value":"%env.JDK_OPEN_11%", "label":"JDK11"}
]
}
]
{noformat}
Improve this feature by special parameter names, like _suiteName and regexps in
value
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11879) [TC Bot] Don't reject contribution because of ExitCodes/Timeouts if the same failure is present in master
Dmitriy Pavlov created IGNITE-11879: --- Summary: [TC Bot] Don't reject contribution because of ExitCodes/Timeouts if the same failure is present in master Key: IGNITE-11879 URL: https://issues.apache.org/jira/browse/IGNITE-11879 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov - Check failure rate for particular build problem in master, - don't add a suite to possible blockers if failure rate for the same problem (by code) is more than 25% -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11853) [TC Bot] Add special mode/flag for threating failures of licenses/javadoc and some other stable suites
Dmitriy Pavlov created IGNITE-11853: --- Summary: [TC Bot] Add special mode/flag for threating failures of licenses/javadoc and some other stable suites Key: IGNITE-11853 URL: https://issues.apache.org/jira/browse/IGNITE-11853 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov As the simplest solution, we could add suite IDs into branches.json -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11796) WAL recovery stopped with 'Partition consistency failure: newPageId'
Dmitriy Pavlov created IGNITE-11796:
---
Summary: WAL recovery stopped with 'Partition consistency failure:
newPageId'
Key: IGNITE-11796
URL: https://issues.apache.org/jira/browse/IGNITE-11796
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
Fix For: 2.8, 2.7.5
https://repository.apache.org/content/repositories/orgapacheignite-1436/ test
using TC bot showed that there can be a situation when DB contains an incorrect
record. This record probably does not lead to corruption (because 2.7.0 works
well with this DB).
But validation introduced in https://issues.apache.org/jira/browse/IGNITE-11030
stops WAL recovery.
{noformat}
java.util.concurrent.ExecutionException: java.lang.AssertionError: Partition
consistency failure: newPageId=1f3d3 (newPartId: 0)
pageId=101001af3d3 (partId: 26)
at java.base/java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.base/java.util.concurrent.FutureTask.get(FutureTask.java:205)
at
org.apache.ignite.ci.di.IgniteTcBotModule.lambda$configure$0(IgniteTcBotModule.java:61)
at
com.google.inject.internal.ProviderInternalFactory.provision(ProviderInternalFactory.java:85)
at
com.google.inject.internal.InternalFactoryToInitializableAdapter.provision(InternalFactoryToInitializableAdapter.java:57)
at
com.google.inject.internal.ProviderInternalFactory.circularGet(ProviderInternalFactory.java:59)
at
com.google.inject.internal.InternalFactoryToInitializableAdapter.get(InternalFactoryToInitializableAdapter.java:47)
at com.google.inject.internal.InjectorImpl$1.get(InjectorImpl.java:1050)
at
com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1086)
at
org.apache.ignite.ci.web.auth.AuthenticationFilter.filter(AuthenticationFilter.java:127)
at
org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:108)
at
org.glassfish.jersey.server.ContainerFilteringStage.apply(ContainerFilteringStage.java:44)
at org.glassfish.jersey.process.internal.Stages.process(Stages.java:173)
at
org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:245)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:248)
at org.glassfish.jersey.internal.Errors$1.call(Errors.java:244)
at org.glassfish.jersey.internal.Errors.process(Errors.java:292)
at org.glassfish.jersey.internal.Errors.process(Errors.java:274)
at org.glassfish.jersey.internal.Errors.process(Errors.java:244)
at
org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:265)
at
org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:232)
at
org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:679)
at
org.glassfish.jersey.servlet.WebComponent.serviceImpl(WebComponent.java:392)
at
org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:346)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:365)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:318)
at
org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:205)
at
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:857)
at
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:535)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:146)
at
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:548)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:257)
at
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:255)
at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1340)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:203)
at
org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
at
org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
at
org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:201)
at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1242)
at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:144)
at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
at org.eclipse.jetty.server.Server.handle(Server.java:503)
[jira] [Created] (IGNITE-11779) [TC Bot] Support configurable notifications for non-master branches
Dmitriy Pavlov created IGNITE-11779: --- Summary: [TC Bot] Support configurable notifications for non-master branches Key: IGNITE-11779 URL: https://issues.apache.org/jira/browse/IGNITE-11779 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Now dev.list notifications performed using fake common user and its settings. Need to add this rule to branches.json config and support other branches (e.g. release) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11778) [TC Bot] Implement unconditional blockers and add license check suites to blockers
Dmitriy Pavlov created IGNITE-11778: --- Summary: [TC Bot] Implement unconditional blockers and add license check suites to blockers Key: IGNITE-11778 URL: https://issues.apache.org/jira/browse/IGNITE-11778 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov License by RAT plugin validation should be also - considered as a blocker in PR validation - introduced failure should cause notification on tracked branches -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11777) [TC Bot] Send a notification in case test count in suite goes down and does not change during 4 runs in a row
Dmitriy Pavlov created IGNITE-11777: --- Summary: [TC Bot] Send a notification in case test count in suite goes down and does not change during 4 runs in a row Key: IGNITE-11777 URL: https://issues.apache.org/jira/browse/IGNITE-11777 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov In case tests stopped from being executed by a configuration error, the community can miss it because there are no notifications generated. Test count may be a floating value because of timeouts and exit codes, so we can compare only the successful run of suites. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11761) Normalize encoding for Ignite .NET test file
Dmitriy Pavlov created IGNITE-11761: --- Summary: Normalize encoding for Ignite .NET test file Key: IGNITE-11761 URL: https://issues.apache.org/jira/browse/IGNITE-11761 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov It is encoded in UTF-16, but all other files are UTF-8 Idea blocks me from changing encoding because of BOM exists. https://stackoverflow.com/questions/32986445/remove-a-bom-character-in-a-file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11760) [TC Bot] Support escaping or replacement of vertical dash in the suite name
Dmitriy Pavlov created IGNITE-11760: --- Summary: [TC Bot] Support escaping or replacement of vertical dash in the suite name Key: IGNITE-11760 URL: https://issues.apache.org/jira/browse/IGNITE-11760 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Usage of same special symbol in JIRA makes TC bot visa unreadable -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11740) [TC Bot] Add search for full branch name in contributions table, add mode branch preffered
Dmitriy Pavlov created IGNITE-11740: --- Summary: [TC Bot] Add search for full branch name in contributions table, add mode branch preffered Key: IGNITE-11740 URL: https://issues.apache.org/jira/browse/IGNITE-11740 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov For branch preferred mode - scan branches directly from GitHub more often - trigger build using branch name without special pull/nnn/head Resolve branch name if there are builds triggered, show it in the table -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11688) [TC Bot] Add more configuration options for VISA
Dmitriy Pavlov created IGNITE-11688: --- Summary: [TC Bot] Add more configuration options for VISA Key: IGNITE-11688 URL: https://issues.apache.org/jira/browse/IGNITE-11688 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov - project - default tracked branch -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11669) Research/test reflection based approach for creating direct buffers
Dmitriy Pavlov created IGNITE-11669: --- Summary: Research/test reflection based approach for creating direct buffers Key: IGNITE-11669 URL: https://issues.apache.org/jira/browse/IGNITE-11669 Project: Ignite Issue Type: Sub-task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov In 2.7.5 discussion https://lists.apache.org/thread.html/e575a96bd1eb2fe323006314c15f9fcce7400d56b8ba7a5587ebe44c@%3Cdev.ignite.apache.org%3E Ivan Pavluchin proposed a simple fix for the byte buffer creation problem: https://lists.apache.org/thread.html/84a35e720af7a0af849685d6abfd7d80a72eab9d7513106262568afa@%3Cdev.ignite.apache.org%3E It is necessary to test this approach (probably enforcing to apply it for all Javas) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11600) Fix launch script for Java 12
Dmitriy Pavlov created IGNITE-11600: --- Summary: Fix launch script for Java 12 Key: IGNITE-11600 URL: https://issues.apache.org/jira/browse/IGNITE-11600 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Fix For: 2.7.5 bin/ignite.bat:251 if "%MAJOR_JAVA_VER%" == "11" ( need to change to "%MAJOR_JAVA_VER%" GEQ "11" ( -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11570) Change git URL in release scripts to gitbox
Dmitriy Pavlov created IGNITE-11570: --- Summary: Change git URL in release scripts to gitbox Key: IGNITE-11570 URL: https://issues.apache.org/jira/browse/IGNITE-11570 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11491) [TC Bot] Adapt TC bot to AI CI git proxy: Build may be started without freshest changes
Dmitriy Pavlov created IGNITE-11491: --- Summary: [TC Bot] Adapt TC bot to AI CI git proxy: Build may be started without freshest changes Key: IGNITE-11491 URL: https://issues.apache.org/jira/browse/IGNITE-11491 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov If Ignite developer - pushes new fixes into the branch and - quite fast activates build or rebuild of changes from that branch, the last commit may be invisible by TeamCity because of git proxy sync lag. This lag ~ 1 minute. It is necessary to research opportunities to check if a triggered build is fresh or not, display it in the Bot or/and (better) warn a user if TC does not see required commit yet. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11486) Support Automatic modules for ignite-zookeeper: Resolve issues with logging packages conflict
Dmitriy Pavlov created IGNITE-11486:
---
Summary: Support Automatic modules for ignite-zookeeper: Resolve
issues with logging packages conflict
Key: IGNITE-11486
URL: https://issues.apache.org/jira/browse/IGNITE-11486
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Pavlov
Usage of Ignite Zookeeper module in a modular environment failed
{noformat}
error: the unnamed module reads package org.apache.log4j from both
slf4j.log4j12 and log4j
{noformat}
slf4j version is updated by the build system when Ignite Zookeeper is used.
{noformat}
+--- org.slf4j:slf4j-api:1.7.7 -> 1.7.25
+--- org.slf4j:slf4j-log4j12:1.7.7 -> 1.7.25
+--- org.slf4j:slf4j-api:1.7.25
\--- log4j:log4j:1.2.17
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11485) Support Automatic modules for ignite-hibernate: Package interference with hibernate core and hibernate for particular verion
Dmitriy Pavlov created IGNITE-11485:
---
Summary: Support Automatic modules for ignite-hibernate: Package
interference with hibernate core and hibernate for particular verion
Key: IGNITE-11485
URL: https://issues.apache.org/jira/browse/IGNITE-11485
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Pavlov
Hibernate 5.3:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from
both ignite.hibernate.5.3 and ignite.hibernate.core
{noformat}
Hibernate 5.1:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from
both ignite.hibernate.core and ignite.hibernate.5.1
{noformat}
Hibernate 4.2:
{noformat}
error: the unnamed module reads package org.apache.ignite.cache.hibernate from
both ignite.hibernate.core and ignite.hibernate.4.2
{noformat}
Probably we should be classes from hibernate-core module to
org.apache.ignite.cache.hibernate.core package, but this may affect public API
Following class will be moved in case we change core package:
- HibernateAccessStrategyAdapter
- HibernateAccessStrategyFactory
- HibernateCacheProxy
- HibernateExceptionConverter
- HibernateKeyTransformer
- HibernateNonStrictAccessStrategy
- HibernateReadOnlyAccessStrategy
- HibernateReadWriteAccessStrategy
- HibernateTransactionalAccessStrategy
Alternative solution: Hibernate 5.3 is not yet released so we could move
implementation for the newest version to its own subpackage. Formally it would
not be a breaking change.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11469) Support Automatic modules for ignite-rest-http: resolve package inference between Jetty & Tomcat
Dmitriy Pavlov created IGNITE-11469:
---
Summary: Support Automatic modules for ignite-rest-http: resolve
package inference between Jetty & Tomcat
Key: IGNITE-11469
URL: https://issues.apache.org/jira/browse/IGNITE-11469
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Pavlov
{noformat}
error: the unnamed module reads package javax.servlet.http from both
javax.servlet.api and tomcat.servlet.api
error: the unnamed module reads package javax.servlet.descriptor from both
javax.servlet.api and tomcat.servlet.api
error: the unnamed module reads package javax.servlet.annotation from both
javax.servlet.api and tomcat.servlet.api
error: the unnamed module reads package javax.servlet from both
javax.servlet.api and tomcat.servlet.api
{noformat}
Exclude of tomcat dependency solves the problem
{code}
compile(group: 'org.apache.ignite', name: 'ignite-rest-http', version: ignVer)
{
exclude group: 'org.apache.tomcat'
// to remove "javax.servlet.http, javax.servlet.descriptor,
javax.servlet.annotation, javax.servlet" package conflicts.
}
{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11467) Support Automatic modules for ignite-spring: Move of classes to a separate package or jar
Dmitriy Pavlov created IGNITE-11467:
---
Summary: Support Automatic modules for ignite-spring: Move of
classes to a separate package or jar
Key: IGNITE-11467
URL: https://issues.apache.org/jira/browse/IGNITE-11467
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Pavlov
Provided that [IGNITE-11464] is fixed and lucene is excluded from dependencies,
we still need refactor following packages to avoid packages conflicts:
{noformat}
error: the unnamed module reads package org.apache.ignite from both
ignite.spring and ignite.core
error: the unnamed module reads package org.apache.ignite.internal.util.spring
from both ignite.spring and ignite.core
error: the unnamed module reads package
org.apache.ignite.internal.processors.resource from both ignite.spring and
ignite.core
{noformat}
One from class in conflicting packages is org.apache.ignite.IgniteSpringBean,
which may be referenced outside of Ignite.
It mentioned at least here
http://qaru.site/questions/14880736/how-to-connect-apache-ignite-node-by-static-ip-address
with full class name:
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11464) Support Automatic modules for ignite-indexing: bypass or fix H2, Lucene, fix queries and visor package conflicts
Dmitriy Pavlov created IGNITE-11464:
---
Summary: Support Automatic modules for ignite-indexing: bypass or
fix H2, Lucene, fix queries and visor package conflicts
Key: IGNITE-11464
URL: https://issues.apache.org/jira/browse/IGNITE-11464
Project: Ignite
Issue Type: Sub-task
Reporter: Dmitriy Pavlov
{noformat}
error: the unnamed module reads package org.apache.lucene.search from both
lucene.sandbox and lucene.core
error: the unnamed module reads package org.apache.lucene.document from both
lucene.sandbox and lucene.core
error: the unnamed module reads package org.apache.lucene.analysis.standard
from both lucene.core and lucene.analyzers.common
error: the unnamed module reads package
org.apache.ignite.internal.processors.cache.query from both ignite.indexing and
ignite.core
error: the unnamed module reads package org.apache.ignite.internal.visor.verify
from both ignite.indexing and ignite.core
error: module ignite.indexing reads package org.apache.lucene.search from both
lucene.sandbox and lucene.core
error: module ignite.indexing reads package org.apache.lucene.document from
both lucene.sandbox and lucene.core
error: module ignite.indexing reads package org.apache.lucene.analysis.standard
from both lucene.core and lucene.analyzers.common
error: module ignite.indexing reads package
org.apache.ignite.internal.processors.cache.query from both ignite.indexing and
ignite.core
error: module ignite.indexing reads package
org.apache.ignite.internal.visor.verify from both ignite.indexing and
ignite.core
error: module cache.api reads package org.apache.lucene.search from both
lucene.sandbox and lucene.core
error: module cache.api reads package org.apache.lucene.document from both
lucene.sandbox and lucene.core
error: module cache.api reads package org.apache.lucene.analysis.standard from
both lucene.core and lucene.analyzers.common
error: module cache.api reads package
org.apache.ignite.internal.processors.cache.query from both ignite.indexing and
ignite.core
error: module cache.api reads package org.apache.ignite.internal.visor.verify
from both ignite.indexing and ignite.core
error: module annotations reads package org.apache.lucene.search from both
lucene.sandbox and lucene.core
error: module annotations reads package org.apache.lucene.document from both
lucene.sandbox and lucene.core
error: module annotations reads package org.apache.lucene.analysis.standard
from both lucene.core and lucene.analyzers.common
error: module annotations reads package
org.apache.ignite.internal.processors.cache.query from both ignite.indexing and
ignite.core
error: module annotations reads package org.apache.ignite.internal.visor.verify
from both ignite.indexing and ignite.core
error: module ignite.shmem reads package org.apache.lucene.search from both
lucene.sandbox and lucene.core
error: module ignite.shmem reads package org.apache.lucene.document from both
lucene.sandbox and lucene.core
error: module ignite.shmem reads package org.apache.lucene.analysis.standard
from both lucene.core and lucene.analyzers.common
error: module ignite.shmem reads package
org.apache.ignite.internal.processors.cache.query from both ignite.indexing and
ignite.core
error: module ignite.shmem reads package
org.apache.ignite.internal.visor.verify from both ignite.indexing and
ignite.core
error: module org.apache.commons.codec reads package org.apache.lucene.search
from both lucene.sandbox and lucene.core
error: module org.apache.commons.codec reads package org.apache.lucene.document
from both lucene.sandbox and lucene.core
error: module org.apache.commons.codec reads package
org.apache.lucene.analysis.standard from both lucene.core and
lucene.analyzers.common
error: module org.apache.commons.codec reads package
org.apache.ignite.internal.processors.cache.query from both ignite.indexing and
ignite.core
error: module org.apache.commons.codec reads package
org.apache.ignite.internal.visor.verify from both ignite.indexing and
ignite.core
error: module lucene.analyzers.common reads package org.apache.lucene.search
from both lucene.sandbox and lucene.core
error: module lucene.analyzers.common reads package org.apache.lucene.document
from both lucene.sandbox and lucene.core
error: module lucene.analyzers.common reads package
org.apache.lucene.analysis.standard from both lucene.core and
lucene.analyzers.common
error: module lucene.analyzers.common reads package
org.apache.ignite.internal.processors.cache.query from both ignite.indexing and
ignite.core
error: module lucene.analyzers.common reads package
org.apache.ignite.internal.visor.verify from both ignite.indexing and
ignite.core
error: module lucene.queryparser reads package org.apache.lucene.search from
both lucene.sandbox and lucene.core
error: module lucene.queryparser reads package org.apache.lucene.document from
both lucene.sandbox and
[jira] [Created] (IGNITE-11461) Automatic modules support for Apache Ignite: find and resolve packages conflicts
Dmitriy Pavlov created IGNITE-11461: --- Summary: Automatic modules support for Apache Ignite: find and resolve packages conflicts Key: IGNITE-11461 URL: https://issues.apache.org/jira/browse/IGNITE-11461 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Example of failure in modular environment: Error:java: the unnamed module reads package org.apache.ignite.internal.processors.cache.persistence.file from both ignite.core and ignite.direct.io -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11409) Fix Ignite Examples-LGPL pom file
Dmitriy Pavlov created IGNITE-11409: --- Summary: Fix Ignite Examples-LGPL pom file Key: IGNITE-11409 URL: https://issues.apache.org/jira/browse/IGNITE-11409 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov During [~IGINTE-11140] pom-standalone was updated. But we have one more POM file with reference to dependencies: It is necessary to adopt the commit https://github.com/apache/ignite/commit/332103e1997adaba67610ec2e4110cf20d65e406 to pom-standalone-lgpl.xml file -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11393) Create IgniteLinkTaglet.toString() implementation for Java9+
Dmitriy Pavlov created IGNITE-11393: --- Summary: Create IgniteLinkTaglet.toString() implementation for Java9+ Key: IGNITE-11393 URL: https://issues.apache.org/jira/browse/IGNITE-11393 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11273) IgniteCassandraStoreTestSuite failed under Java 11
Dmitriy Pavlov created IGNITE-11273:
---
Summary: IgniteCassandraStoreTestSuite failed under Java 11
Key: IGNITE-11273
URL: https://issues.apache.org/jira/browse/IGNITE-11273
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
https://ci.ignite.apache.org/viewLog.html?buildId=3027678=IgniteTests24Java8_CassandraStore
store.IgniteCassandraStoreTestSuite
{noformat}
java.lang.RuntimeException: Failed to start embedded Cassandra instance
at
org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:59)
Caused by: java.lang.ExceptionInInitializerError
at
org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
Caused by: java.lang.StringIndexOutOfBoundsException: begin 0, end -1, length 5
at
org.apache.ignite.testsuites.cassandra.store.IgniteCassandraStoreTestSuite.setUpClass(IgniteCassandraStoreTestSuite.java:56)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11266) Platform .NET test failed with Java 11 warning
Dmitriy Pavlov created IGNITE-11266:
---
Summary: Platform .NET test failed with Java 11 warning
Key: IGNITE-11266
URL: https://issues.apache.org/jira/browse/IGNITE-11266
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Following warning is unavoidable, because Java always warns about illegal
reflective access (at least for the first time). Probably we can change some
settings to avoid "The active test run was aborted. Reason".
{noformat}
[17:32:56][test] The active test run was aborted. Reason: WARNING: An illegal
reflective access operation has occurred
[17:32:56][test] WARNING: Illegal reflective access by
org.apache.ignite.internal.util.GridUnsafe$2
(file:/data/teamcity/work/9198da4c51c3e112/modules/core/target/classes/) to
field java.nio.Buffer.address
[17:32:56][test] WARNING: Please consider reporting this to the maintainers of
org.apache.ignite.internal.util.GridUnsafe$2
[17:32:56][test] WARNING: Use --illegal-access=warn to enable warnings of
further illegal reflective access operations
[17:32:56][test] WARNING: All illegal access operations will be denied in a
future release
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11265) JVM Crash is often on TeamCity for Java 11 runs
Dmitriy Pavlov created IGNITE-11265: --- Summary: JVM Crash is often on TeamCity for Java 11 runs Key: IGNITE-11265 URL: https://issues.apache.org/jira/browse/IGNITE-11265 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov All crash dumps complain about the same method org.apache.ignite.internal.processors.cache.persistence.tree.util.PageHandler.writeLock Data Structures (https://ci.ignite.apache.org/viewLog.html?buildId=3007882) https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_DataStructures/3007882:id/hs_err_pid2674225.log Other recent examples Queries 1 https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_Queries1/3027655:id/hs_err_pid2458635.log Client Nodes https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ClientNodes/3027569:id/hs_err_pid2431080.log Zookeeper Discovery https://ci.ignite.apache.org/repository/download/IgniteTests24Java8_ZooKeeperDiscovery1/3027601:id/hs_err_pid3473289.log -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11239) SPI and JDBC driver tests failed because of SSL connection timeout
Dmitriy Pavlov created IGNITE-11239: --- Summary: SPI and JDBC driver tests failed because of SSL connection timeout Key: IGNITE-11239 URL: https://issues.apache.org/jira/browse/IGNITE-11239 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi=ignite-11155=buildTypeStatusDiv https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver=ignite-11155=buildTypeStatusDiv Probably we should update Java versions installed on TC agents to avoid some EA-Java-related bugs. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
Dmitriy Pavlov created IGNITE-11233:
---
Summary: Ignite Build for Java 11 does not reuse ignite-tools from
Build Apache Ignite for some configurations, Compilation error
Key: IGNITE-11233
URL: https://issues.apache.org/jira/browse/IGNITE-11233
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
_Javadoc_ [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc=ignite-11213=buildTypeStatusDiv
SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy=ignite-11213=buildTypeStatusDiv
RDD* [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd=ignite-11213=buildTypeStatusDiv
JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11=ignite-11213=buildTypeStatusDiv
{noformat}
[21:28:31][Step 1/1] [INFO] Compiling 9 source files to
/data/teamcity/work/9198da4c51c3e112/modules/tools/target/classes
[21:28:32][Step 1/1] [INFO]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java
uses or overrides a deprecated API that is marked for removal.
[21:28:32][Step 1/1] [INFO]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:
Recompile with -Xlint:removal for details.
[21:28:32][Step 1/1] [INFO]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java
uses unchecked or unsafe operations.
[21:28:32][Step 1/1] [INFO]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/classgen/ClassesGenerator.java:
Recompile with -Xlint:unchecked for details.
[21:28:32][Step 1/1] [INFO]
-
[21:28:32][Step 1/1] [ERROR] COMPILATION ERROR :
[21:28:32][Step 1/1] [INFO]
-
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[21,29]
package com.sun.tools.doclets does not exist
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[30,42]
cannot find symbol
[21:28:32][Step 1/1] symbol: class Taglet
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[37,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[44,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[51,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[58,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[65,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[72,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[79,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[88,5]
method does not override or implement a method from a supertype
[21:28:32][Step 1/1] [ERROR]
/data/teamcity/work/9198da4c51c3e112/modules/tools/src/main/java/org/apache/ignite/tools/javadoc/IgniteLinkTaglet.java:[100,9]
cannot find symbol
[21:28:32][Step 1/1] symbol: class Taglet
[21:28:32][Step 1/1] location: class
[jira] [Created] (IGNITE-11213) A number of suites failed because of maven-surefire-plugin NPE for Java 11 build
Dmitriy Pavlov created IGNITE-11213:
---
Summary: A number of suites failed because of
maven-surefire-plugin NPE for Java 11 build
Key: IGNITE-11213
URL: https://issues.apache.org/jira/browse/IGNITE-11213
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
See, for example, Logging Run Config failure at
https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=2996808
{noformat}
test (default-cli) on project ignite-core: Execution default-cli of goal
org.apache.maven.plugins:maven-surefire-plugin:2.20.1:test failed.
NullPointerException -> [Help 1]
{noformat}
According https://maven.apache.org/surefire/maven-surefire-plugin/ at least
https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-surefire-plugin/3.0.0-M3
is required
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11198) [TC Bot] Apache Ignite TeamCity Bot unable to issue visa for special symbol '|'
Dmitriy Pavlov created IGNITE-11198: --- Summary: [TC Bot] Apache Ignite TeamCity Bot unable to issue visa for special symbol '|' Key: IGNITE-11198 URL: https://issues.apache.org/jira/browse/IGNITE-11198 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Presence of special symbol '|' in suite name, which failure during TC run, makes the Bot to be unable to left JIRA comment, JIRA REST failed with escape. Replace '|' to, for example, '_' symbol in suites name for JIRA comment generation -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11196) A number of suited failed because of maven-enforcer-plugin failure for Java 11 build
Dmitriy Pavlov created IGNITE-11196:
---
Summary: A number of suited failed because of
maven-enforcer-plugin failure for Java 11 build
Key: IGNITE-11196
URL: https://issues.apache.org/jira/browse/IGNITE-11196
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Peter Ivanov
A number of exit codes occurred in Java 11 tests build:
- SPI (URI Deploy) [ tests 0 Exit Code ] 1 queued
- RDD* [ tests 0 Exit Code ]
- OSGi [ tests 0 Exit Code ]
- Logging [ tests 0 Exit Code ]
- AOP [ tests 0 Exit Code ]
- JCache TCK 1.1 [ tests 0 Exit Code ]
- _Licenses Headers_ [ tests 0 Exit Code ]
- Cassandra Store [ tests 0 Exit Code ]
For example, SPI (URI Deploy) failed with maven enforcer plugin:
https://ci.ignite.apache.org/viewLog.html?tab=buildLog=tree=debug=all=2995900&_focus=1525
{noformat}
org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce (default) on project
ignite-tools: Execution default of goal
org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-enforcer-plugin:1.4:enforce:
java.lang.ExceptionInInitializerError: null
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11195) Platform C++ tests failed to find JVM for Java 11 build
Dmitriy Pavlov created IGNITE-11195:
---
Summary: Platform C++ tests failed to find JVM for Java 11 build
Key: IGNITE-11195
URL: https://issues.apache.org/jira/browse/IGNITE-11195
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
482 C++ tests failed with error
{noformat}
std::exception: JVM library is not found (did you set JAVA_HOME environment
variable?)
{noformat}
https://ci.ignite.apache.org/viewLog.html?buildId=2973675=IgniteTests24Java8_PlatformCWinX64Release=buildResultsDiv_IgniteTests24Java8=ignite-11155
Looks like we need somehow handle new parameters in C++ tests
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11190) Fix Apache Ignite tests of Camel Streamer under Java 11
Dmitriy Pavlov created IGNITE-11190: --- Summary: Fix Apache Ignite tests of Camel Streamer under Java 11 Key: IGNITE-11190 URL: https://issues.apache.org/jira/browse/IGNITE-11190 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Under Java 11 tests failed with an Error 500 - internal server error https://ci.ignite.apache.org/viewLog.html?buildId=2973663=buildResultsDiv=IgniteTests24Java8_Streamers Probably we need to pass startup parameters to 3rd party product/JVM. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
Dmitriy Pavlov created IGNITE-11191:
---
Summary: Fix Hibernate integration by providing JAXB dependency
during compile
Key: IGNITE-11191
URL: https://issues.apache.org/jira/browse/IGNITE-11191
Project: Ignite
Issue Type: Bug
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
https://ci.ignite.apache.org/viewLog.html?buildId=2973733=buildResultsDiv=IgniteTests24Java8_Hibernate53#testNameId-1306520535171712877
{noformat}
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1018)
Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.startHibernate(HibernateL2CacheSelfTest.java:1923)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.createSessionFactories(HibernateL2CacheSelfTest.java:1900)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheSelfTest.testVersionedEntity(HibernateL2CacheSelfTest.java:1026)
at org.apache.ignite.cache
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11189) Support Java 11 for Apache Ignite
Dmitriy Pavlov created IGNITE-11189: --- Summary: Support Java 11 for Apache Ignite Key: IGNITE-11189 URL: https://issues.apache.org/jira/browse/IGNITE-11189 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov This is an umbrella ticket to link all Java 11 related efforts in one ticket. 'Blocked by' link type is used in case change is mandatory to be done. Other link types, e.g. 'related to' used for nice-to-have fixes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11181) [TC Bot] Avoid notifications about too old failures
Dmitriy Pavlov created IGNITE-11181: --- Summary: [TC Bot] Avoid notifications about too old failures Key: IGNITE-11181 URL: https://issues.apache.org/jira/browse/IGNITE-11181 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Avoid emailing about failures older than some predefined limit -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
Dmitriy Pavlov created IGNITE-11155:
---
Summary: Add JVM options analysis to Ignition.start() or handle
and comment exceptions
Key: IGNITE-11155
URL: https://issues.apache.org/jira/browse/IGNITE-11155
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
In Ignite examples or using Ignite Embedded mode (using direct Ignition.start()
call from a user IDE), may fail with exceptions for JDKs newer than 8.
It may confuse the user. Instead of just logging an exception it is better to
output message with advice on how to fix it. E.g.
{noformat}
Please make sure --add-exports=java.base/sun.nio.ch=ALL-UNNAMED is enabled." +
"See
https://apacheignite.readme.io/docs/getting-started#section-running-ignite-with-java-9-10-11
for more info
{noformat}
Modern IDEs like IntelliJ will display the link as a clickable hyperlink and
Ignite in embedded mode will show how to set up Application configuration
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11153) Support Java 11 for control.sh
Dmitriy Pavlov created IGNITE-11153:
---
Summary: Support Java 11 for control.sh
Key: IGNITE-11153
URL: https://issues.apache.org/jira/browse/IGNITE-11153
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
JAXB module was removed from Java 11.
Please adopt ignite control.sh in the same way as it is done for ignite.sh/bat
{noformat}
elif [ $version -gt 8 ] && [ $version -lt 11 ]; then
JVM_OPTS="\
-XX:+AggressiveOpts \
--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
--add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
--add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
--illegal-access=permit \
--add-modules=java.transaction \
--add-modules=java.xml.bind \
${JVM_OPTS}"
elif [ $version -eq 11 ] ; then
JVM_OPTS="\
--add-exports=java.base/jdk.internal.misc=ALL-UNNAMED \
--add-exports=java.base/sun.nio.ch=ALL-UNNAMED \
--add-exports=java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
--add-exports=jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
--add-exports=java.base/sun.reflect.generics.reflectiveObjects=ALL-UNNAMED \
--illegal-access=permit \
${JVM_OPTS}"
{noformat}
But control.sh for master still declares --add-modules java.xml.bind \
{noformat}
JVM_OPTS="--add-exports java.base/jdk.internal.misc=ALL-UNNAMED \
--add-exports java.base/sun.nio.ch=ALL-UNNAMED \
--add-exports java.management/com.sun.jmx.mbeanserver=ALL-UNNAMED \
--add-exports jdk.internal.jvmstat/sun.jvmstat.monitor=ALL-UNNAMED \
--add-modules java.xml.bind \
${JVM_OPTS}"
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-11140) Check and fix Ignite examples for Java 11
Dmitriy Pavlov created IGNITE-11140: --- Summary: Check and fix Ignite examples for Java 11 Key: IGNITE-11140 URL: https://issues.apache.org/jira/browse/IGNITE-11140 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Apache Ignite has a nightly release builds, these builds contain examples, as well as releases. It is required to check these release builds for examples compatibility with Java 11 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11105) [TC Bot] Support Teamcity servers aliases
Dmitriy Pavlov created IGNITE-11105: --- Summary: [TC Bot] Support Teamcity servers aliases Key: IGNITE-11105 URL: https://issues.apache.org/jira/browse/IGNITE-11105 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Implement feature of aliasing TeamCity builds bat. Alias will act as a pointer to the real name of a server. It is necessary for a feature of linking builds with separate JIRA projects and/or GitHub forks without duplicating of all builds database. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11049) [TC Bot] Reset Credentials is broken
Dmitriy Pavlov created IGNITE-11049: --- Summary: [TC Bot] Reset Credentials is broken Key: IGNITE-11049 URL: https://issues.apache.org/jira/browse/IGNITE-11049 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov https://mtcga.gridgain.com/user.html Reset credentials gives Internal Server Error [500]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
Dmitriy Pavlov created IGNITE-11030:
---
Summary: Teamcity Bot cache is in unrecoverable state after bot
restart: need to check reasons
Key: IGNITE-11030
URL: https://issues.apache.org/jira/browse/IGNITE-11030
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
- TC Bot was stopped with kill command (default signal).
- Shutdown hook calls ignite close
But after updating to V190122 TC Bot DB was became unrecoverable for
"teamcityTestRunHist" cache with exception
{noformat}
Failure periodic check failed: javax.cache.CacheException: class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on lookup row: SearchRow
[key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
[idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
branch=281], hash=1241170874, cacheId=0]
com.google.common.util.concurrent.UncheckedExecutionException:
javax.cache.CacheException: class
org.apache.ignite.internal.processors.cache.persistence.tree.CorruptedTreeException:
Runtime failure on lookup row: SearchRow
[key=org.apache.ignite.ci.teamcity.ignited.runhist.RunHistKey
[idHash=1028871081, hash=1241170874, srvId=1411517106, testOrSuiteName=11924,
branch=281], hash=1241170874, cacheId=0]
at com.google.common.cache.LocalCache$Segment.get(LocalCache.java:2050)
at com.google.common.cache.LocalCache.get(LocalCache.java:3952)
at
com.google.common.cache.LocalCache$LocalManualCache.get(LocalCache.java:4871)
at
org.apache.ignite.ci.di.cache.GuavaCachedInterceptor.invoke(GuavaCachedInterceptor.java:59)
at
org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.getTestRunHist(TeamcityIgnitedImpl.java:404)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.lambda$initFromContext$0(SuiteCurrentStatus.java:155)
at java.util.Comparator.lambda$comparing$77a9974f$1(Comparator.java:469)
at
java.util.Collections$ReverseComparator2.compare(Collections.java:5178)
at java.util.TimSort.countRunAndMakeAscending(TimSort.java:355)
at java.util.TimSort.sort(TimSort.java:220)
at java.util.Arrays.sort(Arrays.java:1512)
at java.util.ArrayList.sort(ArrayList.java:1462)
at
org.apache.ignite.ci.web.model.current.SuiteCurrentStatus.initFromContext(SuiteCurrentStatus.java:160)
at
org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.lambda$initFromContext$0(ChainAtServerCurrentStatus.java:171)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at
java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at
org.apache.ignite.ci.web.model.current.ChainAtServerCurrentStatus.initFromContext(ChainAtServerCurrentStatus.java:167)
at
org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.lambda$getTrackedBranchTestFailures$1(TrackedBranchChainsProcessor.java:121)
at
java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at
java.util.stream.ReferencePipeline$2$1.accept(ReferencePipeline.java:175)
at
java.util.ArrayList$ArrayListSpliterator.forEachRemaining(ArrayList.java:1382)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at
java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at
java.util.stream.ForEachOps$ForEachOp.evaluateSequential(ForEachOps.java:151)
at
java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateSequential(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at
java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at
org.apache.ignite.ci.tcbot.chain.TrackedBranchChainsProcessor.getTrackedBranchTestFailures(TrackedBranchChainsProcessor.java:125)
at
org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76)
at
org.apache.ignite.ci.tcbot.issue.IssueDetector.checkFailuresEx(IssueDetector.java:445)
at
[jira] [Created] (IGNITE-10989) [TC Bot] Finalize refactoring and remove REST data persistent caches
Dmitriy Pavlov created IGNITE-10989: --- Summary: [TC Bot] Finalize refactoring and remove REST data persistent caches Key: IGNITE-10989 URL: https://issues.apache.org/jira/browse/IGNITE-10989 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov TC Bot was migrated to compacted storage of builds, so now it is no reason to keep old-fashioned REST request caches for TeamCity data -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10978) Remove unused tests marked with unclear todo
Dmitriy Pavlov created IGNITE-10978:
---
Summary: Remove unused tests marked with unclear todo
Key: IGNITE-10978
URL: https://issues.apache.org/jira/browse/IGNITE-10978
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
{noformat}
// TODO GG-11141.
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagTxPartitionedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagReplicatedSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagLocalSelfTest.class,
ignoredTests);
//
GridTestUtils.addTestIfNeeded(suite,GridCacheOnCopyFlagAtomicSelfTest.class,
ignoredTests);
{noformat}
Test classes not used, so there is no reason to keep it
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10942) [TC Bot] Optimize backround JIRA tickets sync
Dmitriy Pavlov created IGNITE-10942: --- Summary: [TC Bot] Optimize backround JIRA tickets sync Key: IGNITE-10942 URL: https://issues.apache.org/jira/browse/IGNITE-10942 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov JIRA sync is now performed in not an efficient manner. All project data is reloaded every 15 minutes, and this may create additional pressure for 3rd party services. Introduce incremental updates (update is running only until the first non-modified element found) and full updates. Check ticket data modification before saving into Ignite DB (will safe WAL & page store pressure). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10930) [TC Bot] Support PR-less contributions
Dmitriy Pavlov created IGNITE-10930: --- Summary: [TC Bot] Support PR-less contributions Key: IGNITE-10930 URL: https://issues.apache.org/jira/browse/IGNITE-10930 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov An Apache Ignite committer can prepare issue fix with origin/ignite-1 branch. And this contributions testing does not require any PR creations, because TC RunAll may be created without it. Support contributions detection by provided TC run for branches matching ignite-N, where N=0-9 If such RunAll presented for any tracked branch and JIRA issue is in PA state, we may display these branches as addition to PRs, show its report and setup VISA into IGNITE-N ticket. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10832) [TC Bot] Auto-trigger check win agents availability before triggering a build
Dmitriy Pavlov created IGNITE-10832: --- Summary: [TC Bot] Auto-trigger check win agents availability before triggering a build Key: IGNITE-10832 URL: https://issues.apache.org/jira/browse/IGNITE-10832 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Currently, Win Agents may be a bottle-neck in TC throughput. So it is reasonable to check constraint availability, but not only overall pool of agents -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10787) [TC Bot] Setup TC bot profiling on the server using SJK/stcap and prepare rules for Ignite thread groups
Dmitriy Pavlov created IGNITE-10787: --- Summary: [TC Bot] Setup TC bot profiling on the server using SJK/stcap and prepare rules for Ignite thread groups Key: IGNITE-10787 URL: https://issues.apache.org/jira/browse/IGNITE-10787 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov https://github.com/aragozin/jvm-tools Integrate tool into start scrips, prepare settings for capturing Prepare traces analysis and include into server monitoring page https://mtcga.gridgain.com/monitoring.html -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10677) [TC Bot] Include build failure on metric & exit code into critical failures
Dmitriy Pavlov created IGNITE-10677: --- Summary: [TC Bot] Include build failure on metric & exit code into critical failures Key: IGNITE-10677 URL: https://issues.apache.org/jira/browse/IGNITE-10677 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov It is necessary to setup dev.list notifications for _License_ failure and for Inspections: Core failures notification -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10639) Proof of concept for internal description for packages
Dmitriy Pavlov created IGNITE-10639: --- Summary: Proof of concept for internal description for packages Key: IGNITE-10639 URL: https://issues.apache.org/jira/browse/IGNITE-10639 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Need to test opportunities for documenting packages structure using package-info/readme.txt/readme.md -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10620) [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests
Dmitriy Pavlov created IGNITE-10620: --- Summary: [TC Bot] Implement Tracked Branches processor and IssueDetector unit tests Key: IGNITE-10620 URL: https://issues.apache.org/jira/browse/IGNITE-10620 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Implement actual tests for tracked branches processing and issue detectors. Skeletons: org.apache.ignite.ci.tcbot.issue.IssueDetectorTest#testDetector org.apache.ignite.ci.tcbot.chain.TrackedBranchProcessorTest#testTrackedBranchChainsProcessor The actual challenge is refactoring of configuration to use not singletons, but some injected interfaces with mock-able alternatives, refactor scheduler, and any other refactorings needed to cover issue detection by test. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10562) [TC Bot] DB contains invalid values for build references ID maps to value with other ID
Dmitriy Pavlov created IGNITE-10562:
---
Summary: [TC Bot] DB contains invalid values for build references
ID maps to value with other ID
Key: IGNITE-10562
URL: https://issues.apache.org/jira/browse/IGNITE-10562
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
{noformat}
http://ci.ignite.apache.org/viewLog.html?buildId=2253798buildTypeId=IgniteTests24Java8_Cloud;
href="/app/rest/latest/builds/id:2253798">
20181106T114741+0300
20181106T130017+0300
20181106T130156+0300
http://ci.ignite.apache.org/viewLog.html?buildId=2253788buildTypeId=IgniteTests24Java8_BuildApacheIgnite;
href="/app/rest/latest/builds/id:2253788"/>
http://ci.ignite.apache.org/viewModification.html?modId=837621personal=false;
href="/app/rest/latest/changes/id:837621"/>
http://ci.ignite.apache.org/viewLog.html?buildId=2253900buildTypeId=IgniteTests24Java8_RunAll;
href="/app/rest/latest/builds/id:2253900"/>
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-10498) [TC Bot] Handle conflict error returned by TeamCity for some build problems
Dmitriy Pavlov created IGNITE-10498: --- Summary: [TC Bot] Handle conflict error returned by TeamCity for some build problems Key: IGNITE-10498 URL: https://issues.apache.org/jira/browse/IGNITE-10498 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov java.lang.IllegalStateException: Invalid Response Code : 409: Responding with error, status code: 409 (Conflict). Details: jetbrains.buildServer.server.rest.errors.InvalidStateException: Build problem with id '2630' does not have an associated build. Cannot process this request at this time. Repeat later. at org.apache.ignite.ci.util.HttpUtil.getInputStream(HttpUtil.java:192) at org.apache.ignite.ci.util.HttpUtil.sendGetWithBasicAuth(HttpUtil.java:92) at org.apache.ignite.ci.teamcity.pure.TeamcityRecordingConnection.sendGet(TeamcityRecordingConnection.java:31) at org.apache.ignite.ci.IgniteTeamcityConnection.sendGetXmlParseJaxb(IgniteTeamcityConnection.java:373) at org.apache.ignite.ci.IgniteTeamcityConnection.getJaxbUsingHref(IgniteTeamcityConnection.java:454) at org.apache.ignite.ci.IgniteTeamcityConnection.getProblems(IgniteTeamcityConnection.java:313) at org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76) at org.apache.ignite.ci.IgnitePersistentTeamcity.getProblemsAndRegisterCritical(IgnitePersistentTeamcity.java:591) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.reloadBuild(ProactiveFatBuildSync.java:326) at org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.loadBuild(ProactiveFatBuildSync.java:271) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.lambda$doLoadBuilds$4(ProactiveFatBuildSync.java:217) at java.lang.Iterable.forEach(Iterable.java:75) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.doLoadBuilds(ProactiveFatBuildSync.java:212) at org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(MonitoredTaskInterceptor.java:111) at org.apache.ignite.ci.di.AutoProfilingInterceptor.invoke(AutoProfilingInterceptor.java:76) at org.apache.ignite.ci.teamcity.ignited.fatbuild.ProactiveFatBuildSync.doLoadBuilds(ProactiveFatBuildSync.java:81) at org.apache.ignite.ci.teamcity.ignited.TeamcityIgnitedImpl.actualizeRecentBuildRefs(TeamcityIgnitedImpl.java:517) at org.apache.ignite.ci.di.scheduler.NamedTask.runIfNeeded(NamedTask.java:122) at org.apache.ignite.ci.di.scheduler.TcBotScheduler.lambda$checkNamedTasks$2(TcBotScheduler.java:85) at java.util.concurrent.ConcurrentHashMap.forEach(ConcurrentHashMap.java:1597) at org.apache.ignite.ci.di.scheduler.TcBotScheduler.checkNamedTasks(TcBotScheduler.java:83) at org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(MonitoredTaskInterceptor.java:111) at org.apache.ignite.ci.di.scheduler.TcBotScheduler.lambda$sheduleNamed$1(TcBotScheduler.java:70) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset$$$capture(FutureTask.java:308) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) java.lang.IllegalStateException: Invalid Response Code : 409: Responding with error, status code: 409 (Conflict). Details: jetbrains.buildServer.server.rest.errors.InvalidStateException: Build problem with id '2630' does not have an associated build. Cannot process this request at this time. Repeat later. at org.apache.ignite.ci.util.HttpUtil.getInputStream(HttpUtil.java:192) at org.apache.ignite.ci.util.HttpUtil.sendGetWithBasicAuth(HttpUtil.java:92) at org.apache.ignite.ci.teamcity.pure.TeamcityRecordingConnection.sendGet(TeamcityRecordingConnection.java:31) at org.apache.ignite.ci.IgniteTeamcityConnection.sendGetXmlParseJaxb(IgniteTeamcityConnection.java:373) at org.apache.ignite.ci.IgniteTeamcityConnection.getJaxbUsingHref(IgniteTeamcityConnection.java:454) at org.apache.ignite.ci.IgniteTeamcityConnection.getProblems(IgniteTeamcityConnection.java:313) at
[jira] [Created] (IGNITE-10372) [TC Bot] Optimize master trends page
Dmitriy Pavlov created IGNITE-10372: --- Summary: [TC Bot] Optimize master trends page Key: IGNITE-10372 URL: https://issues.apache.org/jira/browse/IGNITE-10372 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Now loading of the page may take up to several minutes. It may be optimized - by avoiding tests list obtaining from composites (instead we may load chain of sub-builds) - by creating a cache of loaded builds in memory (e.g. guava soft values for the main method) - by excluding of usage of deprecated REST caching API approach -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10336) [TC Bot] Running build can cause bot to think there are no failures
Dmitriy Pavlov created IGNITE-10336: --- Summary: [TC Bot] Running build can cause bot to think there are no failures Key: IGNITE-10336 URL: https://issues.apache.org/jira/browse/IGNITE-10336 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Partially canceled builds support introduced a problem. During RunAll run there is possibility bot will count tests and suites and show no blockers found, but actually, we need to wait queued/running completion before any visa can be shown. https://mtcga.gridgain.com/pr.html?serverId=apache=IgniteTests24Java8_RunAll=pull/5431/head=Latest -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10275) [TC Bot] Several JIRA comments are issued in case ignite.cache.remove failed
Dmitriy Pavlov created IGNITE-10275: --- Summary: [TC Bot] Several JIRA comments are issued in case ignite.cache.remove failed Key: IGNITE-10275 URL: https://issues.apache.org/jira/browse/IGNITE-10275 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: PetrovMikhail Example of spam: https://issues.apache.org/jira/browse/IGNITE-9308 org/apache/ignite/ci/observer/ObserverTask.java:179 org.apache.ignite.IgniteCache#remove(K) returns false, so bot tries to re-comment ticket in next cycle. It is possible as a fast fix at first check removes result, as a full fix we can refactor visa requests queue to some new (probably synthetic key). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10243) [TC Bot] Support partially cancelled suites in RunAll
Dmitriy Pavlov created IGNITE-10243: --- Summary: [TC Bot] Support partially cancelled suites in RunAll Key: IGNITE-10243 URL: https://issues.apache.org/jira/browse/IGNITE-10243 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov For case, there is no TC run (RunAll) for the branch with normal status we can check if there are any with canceled status. If canceled status (unknown) appeared on the latest build in suite's rebuilds sequence, we can use the latest build successful. If there is only one build in rebuilds sequence and it was canceled => use this one as a possible blocker for PR report. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10211) [TC Bot] Support triggering non-master branches
Dmitriy Pavlov created IGNITE-10211: --- Summary: [TC Bot] Support triggering non-master branches Key: IGNITE-10211 URL: https://issues.apache.org/jira/browse/IGNITE-10211 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Currently triggering is supported only for default branch org/apache/ignite/ci/jobs/CheckQueueJob.java:106 Nightly build introduces a new tracked branch which is non-default Triggering now does not work. The second point is a check of queued builds: now it is not supporting any filtering branch of build in the queue. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10095) [TC Bot] Support Build Parameters storage in bot's DB and in run statistics
Dmitriy Pavlov created IGNITE-10095: --- Summary: [TC Bot] Support Build Parameters storage in bot's DB and in run statistics Key: IGNITE-10095 URL: https://issues.apache.org/jira/browse/IGNITE-10095 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov [TC Bot] Support Build Parameters storage in bot's DB, and support propagation of these parameters into run statistics It is needed to have a future opportunity to separate Java 8,10,11 Runs and also runs with short test set and full overnight run. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10071) [TC Bot] Background upload of a build and simultaneous bot restart may result in a queued build persisted but actually build is finished
Dmitriy Pavlov created IGNITE-10071: --- Summary: [TC Bot] Background upload of a build and simultaneous bot restart may result in a queued build persisted but actually build is finished Key: IGNITE-10071 URL: https://issues.apache.org/jira/browse/IGNITE-10071 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov TC bot new persistence based on continuous uploading builds from the TC server may become outdated during bot server restart. E.g. Run all which became completed in TC Bot's base may include queued/running builds, which may lead to missed test failures (As running build may not have these failures). -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-10030) [TC Bot] Background upload of changes, problems, and statistics
Dmitriy Pavlov created IGNITE-10030: --- Summary: [TC Bot] Background upload of changes, problems, and statistics Key: IGNITE-10030 URL: https://issues.apache.org/jira/browse/IGNITE-10030 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov After the implementation of [IGNITE-9848] load time is still long because of statistics and changes requires significant time to be loaded Refs: BuildChainProcessor#loadTestsAndProblems TeamcityIgnitedImpl#reloadBuild -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9869) [TC Bot] Running builds not uploaded into prefetched builds collection
Dmitriy Pavlov created IGNITE-9869: -- Summary: [TC Bot] Running builds not uploaded into prefetched builds collection Key: IGNITE-9869 URL: https://issues.apache.org/jira/browse/IGNITE-9869 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov PR inspection page shows there are running builds, Reproduced during #2744 IGNITE-6444: Validate that copyOnRead flag is configured with on-heap cache enabled. build check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9848) [TC Bot] Background upload of all builds from TC to the bot DB
Dmitriy Pavlov created IGNITE-9848: -- Summary: [TC Bot] Background upload of all builds from TC to the bot DB Key: IGNITE-9848 URL: https://issues.apache.org/jira/browse/IGNITE-9848 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov To fix slow loading of PR report and Master trends page. Upload all tracked and observed branches related builds into TC Bot's Ignite DB. Prepare compacted entities to reduce storage size. Implement idea of having fat build, which will represent replies from a number of REST services. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9800) Ignite TC bot: Simplify initial PR search and main navigation path for checking contribution
Dmitriy Pavlov created IGNITE-9800: -- Summary: Ignite TC bot: Simplify initial PR search and main navigation path for checking contribution Key: IGNITE-9800 URL: https://issues.apache.org/jira/browse/IGNITE-9800 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Show list of open PRs and provide an easy way to search PR or ticket. Show a reasonably simple index page with just a number of major use cases. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9648) Improve doc and javadoc for Ignite distrubuted lock
Dmitriy Pavlov created IGNITE-9648: -- Summary: Improve doc and javadoc for Ignite distrubuted lock Key: IGNITE-9648 URL: https://issues.apache.org/jira/browse/IGNITE-9648 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Make more clear statement how distributed locks relate to entry lock. Is it the same key for entry and for the acquired lock(K key); Is it possible to acquire the lock for unexistent entry? https://apacheignite.readme.io/docs/distributed-locks org.apache.ignite.IgniteCache#lock -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9542) Ignite TC bot: provide separated base/current branch history for PR page
Dmitriy Pavlov created IGNITE-9542: -- Summary: Ignite TC bot: provide separated base/current branch history for PR page Key: IGNITE-9542 URL: https://issues.apache.org/jira/browse/IGNITE-9542 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov https://issues.apache.org/jira/browse/IGNITE-9376 works incorrectly without separation of test history for the base and for a shown branch. It is suggested to refactor provided data for the current and for the base branch. It will allow showing blockers based on statistics from the base branch. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9521) Ignite TC bot: remove duplicates in PR analysis branch selection
Dmitriy Pavlov created IGNITE-9521: -- Summary: Ignite TC bot: remove duplicates in PR analysis branch selection Key: IGNITE-9521 URL: https://issues.apache.org/jira/browse/IGNITE-9521 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov A number of branches are shown in PR analysis section in the Bot Check branch/PR: Server: apache Chain: IgniteTests24Java8_RunAll -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9351) Log restore partition state start and finish events with elapsed time
Dmitriy Pavlov created IGNITE-9351:
--
Summary: Log restore partition state start and finish events with
elapsed time
Key: IGNITE-9351
URL: https://issues.apache.org/jira/browse/IGNITE-9351
Project: Ignite
Issue Type: Task
Reporter: Dmitriy Pavlov
Assignee: Dmitriy Pavlov
During startup of Ignite in addition to applying logical updates, there can be
a huge operation of restoring partition states, which for slow HDD and
relatively big count of partitions can require significant time.
It is suggested to add start and finish messages with elapsed time.
{noformat}
"exchange-worker-#42@3605" prio=5 tid=0x57 nid=NA waiting
java.lang.Thread.State: WAITING
at sun.misc.Unsafe.park(Unsafe.java:-1)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:304)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.get0(GridFutureAdapter.java:177)
at
org.apache.ignite.internal.util.future.GridFutureAdapter.getUninterruptibly(GridFutureAdapter.java:145)
at
org.apache.ignite.internal.processors.cache.persistence.file.AsyncFileIO.read(AsyncFileIO.java:95)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStore.read(FilePageStore.java:351)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:328)
at
org.apache.ignite.internal.processors.cache.persistence.file.FilePageStoreManager.read(FilePageStoreManager.java:312)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:779)
at
org.apache.ignite.internal.processors.cache.persistence.pagemem.PageMemoryImpl.acquirePage(PageMemoryImpl.java:624)
at
org.apache.ignite.internal.processors.cache.persistence.DataStructure.acquirePage(DataStructure.java:142)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.PagesList.init(PagesList.java:212)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.AbstractFreeList.(AbstractFreeList.java:370)
at
org.apache.ignite.internal.processors.cache.persistence.freelist.CacheFreeListImpl.(CacheFreeListImpl.java:47)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore$1.(GridCacheOffheapManager.java:1203)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.init0(GridCacheOffheapManager.java:1203)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheOffheapManager$GridCacheDataStore.updateCounter(GridCacheOffheapManager.java:1420)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.updateCounter(GridDhtLocalPartition.java:942)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtLocalPartition.(GridDhtLocalPartition.java:222)
at
org.apache.ignite.internal.processors.cache.distributed.dht.GridDhtPartitionTopologyImpl.forceCreatePartition(GridDhtPartitionTopologyImpl.java:843)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restorePartitionStates(GridCacheDatabaseSharedManager.java:2380)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.applyLastUpdates(GridCacheDatabaseSharedManager.java:2333)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.restoreState(GridCacheDatabaseSharedManager.java:1443)
at
org.apache.ignite.internal.processors.cache.persistence.GridCacheDatabaseSharedManager.beforeExchange(GridCacheDatabaseSharedManager.java:1183)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.distributedExchange(GridDhtPartitionsExchangeFuture.java:1132)
at
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:712)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body0(GridCachePartitionExchangeManager.java:2419)
at
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2299)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at java.lang.Thread.run(Thread.java:748)
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9301) Support method compute withNoResultCache in .Net
Dmitriy Pavlov created IGNITE-9301: -- Summary: Support method compute withNoResultCache in .Net Key: IGNITE-9301 URL: https://issues.apache.org/jira/browse/IGNITE-9301 Project: Ignite Issue Type: Task Components: platforms Reporter: Dmitriy Pavlov During https://issues.apache.org/jira/browse/IGNITE-6284 implementation new method was added - org.apache.ignite.IgniteCompute#withNoResultCache but this method was not supported in .NET API version. It is required to add correct support to .NET -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9132) Update Apache Camel dependency version
Dmitriy Pavlov created IGNITE-9132: -- Summary: Update Apache Camel dependency version Key: IGNITE-9132 URL: https://issues.apache.org/jira/browse/IGNITE-9132 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Fix For: 2.7 Upgrade Apache Camel Dependency to version 2.20.1 or later. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9131) Upgrade guava version in Apache Ignite
Dmitriy Pavlov created IGNITE-9131: -- Summary: Upgrade guava version in Apache Ignite Key: IGNITE-9131 URL: https://issues.apache.org/jira/browse/IGNITE-9131 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Fix For: 2.7 In most cases guava is used only for testing, but for some modules it is used for production code. Current version is 18 https://mvnrepository.com/artifact/com.google.guava/guava/18.0, which was released in 2014. It is suggested to upgrade to fresh version of library, e.g. to https://mvnrepository.com/artifact/com.google.guava/guava/25.1-jre -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9126) Update Apache Kafka dependency
Dmitriy Pavlov created IGNITE-9126: -- Summary: Update Apache Kafka dependency Key: IGNITE-9126 URL: https://issues.apache.org/jira/browse/IGNITE-9126 Project: Ignite Issue Type: Task Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Fix For: 2.7 It is suggested to update kafka in accordance with scala update, e.g. to https://mvnrepository.com/artifact/org.apache.kafka/kafka_2.11/1.0.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9123) Update Apache commons-collections in ignite-yarn module
Dmitriy Pavlov created IGNITE-9123: -- Summary: Update Apache commons-collections in ignite-yarn module Key: IGNITE-9123 URL: https://issues.apache.org/jira/browse/IGNITE-9123 Project: Ignite Issue Type: Bug Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Fix For: 2.7 It seems commons-collections version is not applied to some module. It was updated to 3.2.2 in 2016, but this update has no effect. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9058) Update Apache Tomcat dependency version
Dmitriy Pavlov created IGNITE-9058:
--
Summary: Update Apache Tomcat dependency version
Key: IGNITE-9058
URL: https://issues.apache.org/jira/browse/IGNITE-9058
Project: Ignite
Issue Type: Improvement
Reporter: Dmitriy Pavlov
Update tomcat-servlet-api to newer version (at least 8.0.52, 8.5.31+ or 9.0.8+)
{noformat}
org.apache.tomcat
tomcat-servlet-api
8.0.52
{noformat}
At least Ignite-rest-http, ignite-urideploy, and ignite-web will be affected by
this change.
It is required to run TC tartget RunAll to check all tests passed, it is
required to build fabric using DEVNOTES.txt to make sure full build will be
successfull
Probably it is required to run release step to make sure release candidate can
be prepared.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9057) Update JCraft dependency version in Apache Ignite
Dmitriy Pavlov created IGNITE-9057:
--
Summary: Update JCraft dependency version in Apache Ignite
Key: IGNITE-9057
URL: https://issues.apache.org/jira/browse/IGNITE-9057
Project: Ignite
Issue Type: Improvement
Reporter: Dmitriy Pavlov
Fix For: 2.7
Update ignite-ssh dependency version of com.jcraft:jsch to 0.1.54
{noformat}
com.jcraft
jsch
0.1.54
{noformat}
It is required to run TC tartget RunAll to check all tests passed, it is
required to build fabric using DEVNOTES.txt to make sure full build will be
successfull
Probably it is required to run release step to make sure release candidate can
be prepared.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-9046) Actualize dependency versions for Cassandra Cache Store
Dmitriy Pavlov created IGNITE-9046: -- Summary: Actualize dependency versions for Cassandra Cache Store Key: IGNITE-9046 URL: https://issues.apache.org/jira/browse/IGNITE-9046 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Fix For: 2.7 It is suggested A. to update commons-beanutils version. It can be done using property commons-beanutils.version in pom.xml: change 1.9.2 to latest version, currently it is 1.9.3 http://central.maven.org/maven2/commons-beanutils/commons-beanutils/1.9.3/commons-beanutils-1.9.3.pom B. Update Netty Project netty.version (currently 4.0.33.Final) Upgrade at least to 4.0.37.Final or later or to 4.1.1.Final or later It is required to run RunAll to check all tests passed, check full build locally using build.sh. Probably it is required to run release step to make sure release candidate can be prepared. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9044) Update scala dependency version in Apache Ignite
Dmitriy Pavlov created IGNITE-9044: -- Summary: Update scala dependency version in Apache Ignite Key: IGNITE-9044 URL: https://issues.apache.org/jira/browse/IGNITE-9044 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Fix For: 2.7 *ignite-scalar* scala.library.version=2.11.8, need to be at least 2.11.12 or newer. *ignite-scalar_2.10* scala210.library.version 2.10.6, need to be at least 2.10.7, probably newer *visor 2.10* scala210.jline.version = 2.10.4 , need to be at least 2.10.7, probably newer Probably impact would be wider. We need at least run run-all, local build.sh and optionally release candate step on TC. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9036) Update FasterXML jackson-databind dependency version in Apache Ignite
Dmitriy Pavlov created IGNITE-9036: -- Summary: Update FasterXML jackson-databind dependency version in Apache Ignite Key: IGNITE-9036 URL: https://issues.apache.org/jira/browse/IGNITE-9036 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Actual: jackson2.version in ignite parent pom is 2.6.5, required 2.9.5 or later, Latest version is 2.9.6 affected modules will be at least ignite-aws. It is required to run RunAll to check all tests passed, check full build locally using build.sh. Probably it is required to run release step to make sure release candidate can be prepared. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9035) Update log4j 2x version in Apache Ignite
Dmitriy Pavlov created IGNITE-9035: -- Summary: Update log4j 2x version in Apache Ignite Key: IGNITE-9035 URL: https://issues.apache.org/jira/browse/IGNITE-9035 Project: Ignite Issue Type: Test Reporter: Dmitriy Pavlov Fix For: 2.7 It is suggested to update log4j 2x version to log4j 2.8.2 or later. org.apache.logging.log4j log4j 2.8.2 pom It is required to run RunAll to check all tests passed. Probably it is required to run release step to make sure release candidate can be prepared. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-9005) Eviction policy MBeans change failed LifecycleAwareTest on cache name injectoin
Dmitriy Pavlov created IGNITE-9005:
--
Summary: Eviction policy MBeans change failed LifecycleAwareTest
on cache name injectoin
Key: IGNITE-9005
URL: https://issues.apache.org/jira/browse/IGNITE-9005
Project: Ignite
Issue Type: Test
Reporter: Dmitriy Pavlov
Assignee: Stanislav Lukyanov
Fix For: 2.7
http://apache-ignite-developers.2346864.n4.nabble.com/MTCGA-new-failures-in-builds-1485687-needs-to-be-handled-td32531.html
New test failure detected
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=7246907407546697403=%3Cdefault%3E=testDetails
after merging
IGNITE-8776 Eviction policy MBeans are never registered if
evictionPolicyFactory is used
Revert of commit makes test passing.
Locally test also failed. Failed with message
{noformat}
Unexpected cache name for
org.apache.ignite.internal.processors.cache.GridCacheLifecycleAwareSelfTest$TestEvictionPolicy@322714f4
expected: but was:
{noformat}
Message of failure seems to be related to TestEvictionPolicy instance from test
class.
Seems that returing call to cctx.kernalContext (). resource (). injectCacheName
(rsrc, cfg.getName ()); should fix issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8742) Direct IO 2 suite is timed out by out of disk space failure emulation test: WAL manager failure does not stoped.
Dmitriy Pavlov created IGNITE-8742:
--
Summary: Direct IO 2 suite is timed out by out of disk space
failure emulation test: WAL manager failure does not stoped.
Key: IGNITE-8742
URL: https://issues.apache.org/jira/browse/IGNITE-8742
Project: Ignite
Issue Type: Test
Components: persistence
Reporter: Dmitriy Pavlov
Test
org.apache.ignite.internal.processors.cache.persistence.IgniteNativeIoWalFlushFsyncSelfTest#testFailAfterStart
emulates problem with disc space using exception.
In direct IO environment real IO with disk is performed, tmpfs is not used.
Sometimes this error can come from rollover() of segment, failure handler
reacted accordingly.
{noformat}
detected. Will be handled accordingly to configured handler [hnd=class
o.a.i.failure.StopNodeFailureHandler, failureCtx=FailureContext
[type=CRITICAL_ERROR, err=class o.a.i.i.pagemem.wal.StorageException: Unable to
write]]
class org.apache.ignite.internal.pagemem.wal.StorageException: Unable to write
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.writeBuffer(FsyncModeFileWriteAheadLogManager.java:2964)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flush(FsyncModeFileWriteAheadLogManager.java:2640)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flush(FsyncModeFileWriteAheadLogManager.java:2572)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flushOrWait(FsyncModeFileWriteAheadLogManager.java:2525)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.close(FsyncModeFileWriteAheadLogManager.java:2795)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.access$700(FsyncModeFileWriteAheadLogManager.java:2340)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.rollOver(FsyncModeFileWriteAheadLogManager.java:1029)
at
org.apache.ignite.internal.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.log(FsyncModeFileWriteAheadLogManager.java:673)
{noformat}
But test seems to be not able to stop, node stopper thread tries to stop cache,
flush WAL. flush wait for rollover, which will never happen.
{noformat}
Thread [name="node-stopper", id=2836, state=WAITING, blockCnt=7, waitCnt=9]
Lock
[object=java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@47f6473,
ownerName=null, ownerId=-1]
at sun.misc.Unsafe.park(Native Method)
at java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
at
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitUninterruptibly(AbstractQueuedSynchronizer.java:1976)
at o.a.i.i.util.IgniteUtils.awaitQuiet(IgniteUtils.java:7473)
at
o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.flushOrWait(FsyncModeFileWriteAheadLogManager.java:2546)
at
o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.fsync(FsyncModeFileWriteAheadLogManager.java:2750)
at
o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager$FileWriteHandle.access$2000(FsyncModeFileWriteAheadLogManager.java:2340)
at
o.a.i.i.processors.cache.persistence.wal.FsyncModeFileWriteAheadLogManager.flush(FsyncModeFileWriteAheadLogManager.java:699)
at
o.a.i.i.processors.cache.GridCacheProcessor.stopCache(GridCacheProcessor.java:1243)
at
o.a.i.i.processors.cache.GridCacheProcessor.stopCaches(GridCacheProcessor.java:969)
at
o.a.i.i.processors.cache.GridCacheProcessor.stop(GridCacheProcessor.java:943)
at o.a.i.i.IgniteKernal.stop0(IgniteKernal.java:2289)
at o.a.i.i.IgniteKernal.stop(IgniteKernal.java:2167)
at o.a.i.i.IgnitionEx$IgniteNamedInstance.stop0(IgnitionEx.java:2588)
- locked o.a.i.i.IgnitionEx$IgniteNamedInstance@90f6bfd
at o.a.i.i.IgnitionEx$IgniteNamedInstance.stop(IgnitionEx.java:2551)
at o.a.i.i.IgnitionEx.stop(IgnitionEx.java:372)
at
o.a.i.failure.StopNodeFailureHandler$1.run(StopNodeFailureHandler.java:36)
at java.lang.Thread.run(Thread.java:748)
{noformat}
It seems invalidating environment of WAL manager is not working propertly.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8727) Provide way to test MMap WAL modes failures
Dmitriy Pavlov created IGNITE-8727: -- Summary: Provide way to test MMap WAL modes failures Key: IGNITE-8727 URL: https://issues.apache.org/jira/browse/IGNITE-8727 Project: Ignite Issue Type: Test Components: persistence Reporter: Dmitriy Pavlov Assignee: Andrey Gura Currently tests 4 are failed in PDS 2 suite with timeout: IgnitePdsTestSuite2: IgniteWalFlushBackgroundWithMmapBufferSelfTest.testFailAfterStart (fail rate 100,0%) IgnitePdsTestSuite2: IgniteWalFlushBackgroundWithMmapBufferSelfTest.testFailWhileStart (fail rate 100,0%) IgnitePdsTestSuite2: IgniteWalFlushLogOnlyWithMmapBufferSelfTest.testFailAfterStart (fail rate 100,0%) IgnitePdsTestSuite2: IgniteWalFlushLogOnlyWithMmapBufferSelfTest.testFailWhileStart (fail rate 100,0%) Tests tries to emulate failure using exceptions in file IO, but MMap-ed modes does not allow currently to be tested with current tests approach. It is suggested to create new testing opportunities for MMap modes. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8604) .NET test failures probably after IGNITE-5789 merge
Dmitriy Pavlov created IGNITE-8604:
--
Summary: .NET test failures probably after IGNITE-5789 merge
Key: IGNITE-8604
URL: https://issues.apache.org/jira/browse/IGNITE-8604
Project: Ignite
Issue Type: Improvement
Reporter: Dmitriy Pavlov
Assignee: Ilya Kasnacheev
62 new failed tests in .NET
{noformat}
Store.CacheStoreTest
Current failure:refs/heads/master #254 Changes (8)
24 May 18 02:16
First failure: refs/heads/master #1 No changes 26 Apr
18 10:36
TearDown method failed. HandleRegistry is not empty in grid '' (expected 4,
actual 5):
'[2, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
[3, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
[4, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]
[5, Apache.Ignite.Core.Impl.Cache.Store.CacheStore]'
at NUnit.Framework.Assert.Fail(String message, Object[] args)
at Apache.Ignite.Core.Tests.TestUtils.AssertHandleRegistryHasItems(IIgnite
grid, Int32 expectedCount, Int32 timeout) in
c:\BuildAgent\work\c182b70f2dfa6507\modules\platforms\dotnet\Apache.Ignite.Core.Tests\TestUtils.Common.cs:line
339
at Apache.Ignite.Core.Tests.Cache.Store.CacheStoreTest.AfterTests
{noformat}
First time these test failed
https://ci.ignite.apache.org/viewLog.html?buildId=1323959=buildResultsDiv=IgniteTests24Java8_PlatformNet
Probably it is caused by merge:
https://issues.apache.org/jira/browse/IGNITE-5789
I've tried to revert commit in ignite-5789-1 branch and results:
https://ci.ignite.apache.org/viewLog.html?buildId=1326520=buildResultsDiv=IgniteTests24Java8_PlatformNet
Other test failed, but current tests were passed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8599) Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge from Direct IO suite
Dmitriy Pavlov created IGNITE-8599: -- Summary: Remove LocalWalModeChangeDuringRebalancingSelfTest.testWithExchangesMerge from Direct IO suite Key: IGNITE-8599 URL: https://issues.apache.org/jira/browse/IGNITE-8599 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Dmitriy Pavlov Fix For: 2.6 https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=6346758468206865681=%3Cdefault%3E=testDetails It falls only in Direct IO It is necessary to exclude it from direct IO if it gives a lot of load. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8503) IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has flaky failure: Entry which should be expired by TTL policy is available after grid restart
Dmitriy Pavlov created IGNITE-8503:
--
Summary: IgnitePdsWithTtlTest.testTtlIsAppliedAfterRestart has
flaky failure: Entry which should be expired by TTL policy is available after
grid restart
Key: IGNITE-8503
URL: https://issues.apache.org/jira/browse/IGNITE-8503
Project: Ignite
Issue Type: Improvement
Components: persistence
Reporter: Dmitriy Pavlov
Test was added during https://issues.apache.org/jira/browse/IGNITE-5874
development.
This test restarts grid and checks all entries are not present in grid.
But with high possiblity one from 7000 entries to be expired is resurrected
instead and returned by cache get.
{noformat}
After timeout {{
>>>
>>> Cache memory stats [igniteInstanceName=db.IgnitePdsWithTtlTest0,
>>> cache=expirableCache]
>>> Cache size: 0
>>> Cache partition topology stats
>>> [igniteInstanceName=db.IgnitePdsWithTtlTest0, grp=group1]
>>>
>>> Cache event manager memory stats
>>> [igniteInstanceName=db.IgnitePdsWithTtlTest0, cache=expirableCache,
>>> stats=N/A]
>>>
>>> Query manager memory stats [igniteInstanceName=db.IgnitePdsWithTtlTest0,
>>> cache=expirableCache]
>>> threadsSize: 0
>>> futsSize: 0
>>>
>>> TTL processor memory stats [igniteInstanceName=db.IgnitePdsWithTtlTest0,
>>> cache=expirableCache]
>>> pendingEntriesSize: 0
}} After timeout
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (IGNITE-8480) Broken Ignite Examples test Support Spring Data 2.0
Dmitriy Pavlov created IGNITE-8480: -- Summary: Broken Ignite Examples test Support Spring Data 2.0 Key: IGNITE-8480 URL: https://issues.apache.org/jira/browse/IGNITE-8480 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Roman Meerson https://issues.apache.org/jira/browse/IGNITE-6879 implementation was introduced support of spring data of version 2.0+ But example test is broken on TC after this change [Examples |https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Examples=%3Cdefault%3E=buildTypeStatusDiv] IgniteExamplesSelfTestSuite: SpringDataExampleSelfTest.testSpringDataExample Test history: [https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-9052304574499269123=%3Cdefault%3E=testDetails] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8456) Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but persistence enabled
Dmitriy Pavlov created IGNITE-8456: -- Summary: Print warning if IGNITE_HOME & WORK and persistentStoreDir is not set, but persistence enabled Key: IGNITE-8456 URL: https://issues.apache.org/jira/browse/IGNITE-8456 Project: Ignite Issue Type: Improvement Components: persistence Reporter: Dmitriy Pavlov Fix For: 2.6 In method org.apache.ignite.internal.util.IgniteUtils#workDirectory Ignite determine Work dir to be set, same value may be used in case persistence Store Folder is not set and IGNITE_HOME is not specified. In case work dir is not specified, temp directory is used for Ignite Work. But for persistence enabled case this means user DB goes to temp folder and may be removed later. User may be confused by this behaviour. See: [https://stackoverflow.com/questions/48434929/apache-ignite-persistent-storage] and related Dev.List discussion [http://apache-ignite-developers.2346864.n4.nabble.com/IGNITE-HOME-for-persistence-td26470.html] -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8401) Assertion error ocurred in JettyRestProcessorAuthenticationWithCredsSelfTest
Dmitriy Pavlov created IGNITE-8401: -- Summary: Assertion error ocurred in JettyRestProcessorAuthenticationWithCredsSelfTest Key: IGNITE-8401 URL: https://issues.apache.org/jira/browse/IGNITE-8401 Project: Ignite Issue Type: Improvement Reporter: Dmitriy Pavlov Assignee: Stanilovsky Evgeny Following tests began to fail after merge https://issues.apache.org/jira/browse/IGNITE-8066 with assertion added in this ticket. *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithCredsSelfTest.testDeactivateActivate[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2035731000398727816=%3Cdefault%3E=testDetails]* *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithCredsSelfTest.testRemove[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=5513793448643455005=%3Cdefault%3E=testDetails]* *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithCredsSelfTest.testRemoveAll[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-1721357182035817455=%3Cdefault%3E=testDetails]* *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithCredsSelfTest.testVisorGateway[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-2028785123619746743=%3Cdefault%3E=testDetails]* *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithTokenSelfTest.testDeactivateActivate[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-334626288130660999=%3Cdefault%3E=testDetails]* *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithTokenSelfTest.testRemove[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=-5504915680838168777=%3Cdefault%3E=testDetails]* *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithTokenSelfTest.testRemoveAll[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1220211038727255366=%3Cdefault%3E=testDetails]* *IgniteClientTestSuite: JettyRestProcessorAuthenticationWithTokenSelfTest.testVisorGateway[ (fail rate 11,1%)|https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=2613252696282859254=%3Cdefault%3E=testDetails]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (IGNITE-8381) testNodeSingletonDeploy in Basic 2 has high fail rate
Dmitriy Pavlov created IGNITE-8381:
--
Summary: testNodeSingletonDeploy in Basic 2 has high fail rate
Key: IGNITE-8381
URL: https://issues.apache.org/jira/browse/IGNITE-8381
Project: Ignite
Issue Type: Improvement
Reporter: Dmitriy Pavlov
Assignee: Vyacheslav Daradur
IgniteServiceConfigVariationsFullApiTestSuite:
IgniteServiceConfigVariationsFullApiTest.testNodeSingletonDeploy
is one from most failing test in TC Run All now
On dev.list IEP-17 is discussed to redesign services and fix deployemnt. In the
same time test itself can't await service to be deployed and confuses Igniters
in RunAll PR results.
It is suggested to find out fast fix to make test passing. It should be
probably based on waiting instead of checking deployed state.
Test history
https://ci.ignite.apache.org/project.html?projectId=IgniteTests24Java8=1909279554207447487=%3Cdefault%3E=testDetails
{noformat}
class org.apache.ignite.IgniteException: Service not found: testService
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1858)
at
org.apache.ignite.internal.processors.job.GridJobWorker$2.call(GridJobWorker.java:568)
at
org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6695)
at
org.apache.ignite.internal.processors.job.GridJobWorker.execute0(GridJobWorker.java:562)
at
org.apache.ignite.internal.processors.job.GridJobWorker.body(GridJobWorker.java:491)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110)
at
org.apache.ignite.internal.processors.job.GridJobProcessor.processJobExecuteRequest(GridJobProcessor.java:1189)
at
org.apache.ignite.internal.processors.job.GridJobProcessor$JobExecutionListener.onMessage(GridJobProcessor.java:1921)
at
org.apache.ignite.internal.managers.communication.GridIoManager.invokeListener(GridIoManager.java:1556)
at
org.apache.ignite.internal.managers.communication.GridIoManager.processRegularMessage0(GridIoManager.java:1184)
at
org.apache.ignite.internal.managers.communication.GridIoManager.access$4200(GridIoManager.java:125)
at
org.apache.ignite.internal.managers.communication.GridIoManager$9.run(GridIoManager.java:1091)
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: class
org.apache.ignite.internal.processors.service.GridServiceNotFoundException:
Service not found: testService
at
org.apache.ignite.internal.processors.service.GridServiceProxy$ServiceProxyCallable.call(GridServiceProxy.java:415)
at
org.apache.ignite.internal.processors.closure.GridClosureProcessor$C2.execute(GridClosureProcessor.java:1855)
... 14 more
{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
