[jira] [Updated] (IGNITE-9672) Move o.a.i.i.processors.cache.persistence.tree.io.PageMetaIO to metastore.
[ https://issues.apache.org/jira/browse/IGNITE-9672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-9672: --- Ignite Flags: (was: Docs Required) > Move o.a.i.i.processors.cache.persistence.tree.io.PageMetaIO to metastore. > -- > > Key: IGNITE-9672 > URL: https://issues.apache.org/jira/browse/IGNITE-9672 > Project: Ignite > Issue Type: Improvement >Reporter: Alexei Scherbakov >Assignee: Ivan Daschinskiy >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > We have in current implementation special meta page related to snapshot > functionality. > Meta page is stored in index partition. > If index.bin is removed (for triggering index rebuild), all information is > lost and incremental snapshot logic is broken. > Solution: move snapshot metadata in metastore. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765917#comment-16765917
]
Dmitriy Pavlov commented on IGNITE-11216:
-
*This issue contains 2 commits* :
https://github.com/apache/ignite/commit/12bd7cdfbb6eb296d7d76bbe738f1c10a309296f
https://github.com/apache/ignite/commit/033170d90f6c0618b9d6a3fd997e13a5ec1fff89
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765798#comment-16765798
]
Dmitriy Pavlov commented on IGNITE-11216:
-
[~vveider] [~Artukhov], WDYT about the following approach.
In case we're unable to determine java version (e.g. home is missing) we will
use Java11 options as it is, but add an option to ignore unrecognized options
(to keep the ability to run it on Java 8).
I mean usage of -XX:+IgnoreUnrecognizedVMOptions
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765131#comment-16765131
]
Dmitriy Pavlov commented on IGNITE-11216:
-
[~Artukhov] please align the solution with [~vveider]. I can merge second
commit once it is clear how to handle
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765023#comment-16765023
]
Dmitriy Pavlov commented on IGNITE-11216:
-
[~ustas], yes, warning about reflective access in unavoidable.
See also https://docs.oracle.com/en/java/javase/11/tools/java.html
--illegal-access and it's value 'permit'
{quote}
This mode opens each package in each module in the run-time image to code in
all unnamed modules (such as code on the class path), if that package existed
in JDK 8. This enables both static access (for example, by compiled bytecode),
and deep reflective access through the platform's various reflection APIs. The
first reflective-access operation to any such package causes a warning to be
issued. However, no warnings are issued after the first occurrence. This single
warning describes how to enable further warnings. This mode is the default for
the current JDK but will change in a future release.
{quote}
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11265) JVM Crash is often on TeamCity for Java 11 runs
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11265: Priority: Critical (was: Major) > 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 >Priority: Critical > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > > 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] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16765033#comment-16765033
]
Dmitriy Pavlov commented on IGNITE-11155:
-
New comment for failure looks like the following exception
!start-java11-2.png!
> 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
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11-2.png, start-java11.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Attachment: start-java11-2.png
> 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
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11-2.png, start-java11.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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] [Commented] (IGNITE-6879) Support Spring Data 2.0
[ https://issues.apache.org/jira/browse/IGNITE-6879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764966#comment-16764966 ] Dmitriy Pavlov commented on IGNITE-6879: [~GreenNun] yes, removal of spring-data is mentioned in https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0+Wishlist Feel free to monitor dev.list and remind Ignite developers to refactor this dependency when 3.0 comes. > Support Spring Data 2.0 > --- > > Key: IGNITE-6879 > URL: https://issues.apache.org/jira/browse/IGNITE-6879 > Project: Ignite > Issue Type: Improvement > Components: spring >Affects Versions: 2.3 >Reporter: Alexey Kukushkin >Assignee: Roman Meerson >Priority: Major > Fix For: 2.7 > > > Ignite-spring and ignite-spring-data now use Spring 1.1 and cannot be rebuilt > with Spring 2.0. Trying to change the Spring dependency version to > 2.0.0.release results in compile errors like below and requires regression in > general. > This improvement was created to either migrate from Spring 1.1 to 2.0 or > create another set of modules ignite-spring-xxx-2 to have backward > compatibility with Spring 1.1. > [ERROR] > /Users/kukushal/Dev/incubator-ignite/modules/spring-data/src/main/java/org/apache/ignite/springdata/repository/IgniteRepository.java:[57,10] > name clash: deleteAll(java.lang.Iterable) in > org.apache.ignite.springdata.repository.IgniteRepository and > deleteAll(java.lang.Iterable) in > org.springframework.data.repository.CrudRepository have the same erasure, yet > neither overrides the other -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Comment Edited] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764938#comment-16764938
]
Dmitriy Pavlov edited comment on IGNITE-11155 at 2/11/19 1:10 PM:
--
[~ibessonov] thank you for review.
[~dmagda] thank you for your valuable proposal. I'll add demarcation of
parameters in the warning.
I suggest keeping the link in the warning because
- It shows users, that product is trying to help them to solve the issue, it
is a positive thing, even if the section will be renamed. At least page should
be available.
- It is easy to find in IntelliJ Idea/Teamcity logs because the link is
{color:#59afe1}+blue+{color} (near error text, which is
{color:#d04437}red{color}). It underlines that it is not just NPE or OOME, but
the problem which has a solution and advice about it. It may help the user to
continue to try Ignite examples instead of a too fast decision that product is
not operational.
was (Author: dpavlov):
[~ibessonov] thank you for review.
[~dmagda] thank you for your valuable proposal. I'll add demarcation of
parameters in the warning.
I suggest keeping the link in the warning because
- It shows users, that product is trying to help them to solve the issue, it
is a positive thing, even if the section will be renamed. At least page should
be available.
- It is easy to find in IntelliJ Idea/Teamcity logs because the link is
{color:#59afe1}+blue +{color}(which err. text, which is
{color:#d04437}red{color}). It underlines that it is not just NPE or OOME, but
the problem which has a solution and advice about it. It may help the user to
continue to try Ignite examples instead of a too fast decision that product is
not operational.
> 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
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16764938#comment-16764938
]
Dmitriy Pavlov commented on IGNITE-11155:
-
[~ibessonov] thank you for review.
[~dmagda] thank you for your valuable proposal. I'll add demarcation of
parameters in the warning.
I suggest keeping the link in the warning because
- It shows users, that product is trying to help them to solve the issue, it
is a positive thing, even if the section will be renamed. At least page should
be available.
- It is easy to find in IntelliJ Idea/Teamcity logs because the link is
{color:#59afe1}+blue +{color}(which err. text, which is
{color:#d04437}red{color}). It underlines that it is not just NPE or OOME, but
the problem which has a solution and advice about it. It may help the user to
continue to try Ignite examples instead of a too fast decision that product is
not operational.
> 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
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Fix Version/s: 2.8
> 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
>Priority: Major
> Fix For: 2.8
>
> Attachments: start-java11.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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] [Commented] (IGNITE-11266) Platform .NET test failed with Java 11 warning
[
https://issues.apache.org/jira/browse/IGNITE-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763809#comment-16763809
]
Dmitriy Pavlov commented on IGNITE-11266:
-
[~ptupitsyn], it is absolutely impossible, it is generated by JVM.
see also docs about parameter
--illegal-access=permit here
https://docs.oracle.com/en/java/javase/11/tools/java.html#GUID-3B1CE181-CD30-4178-9602-230B800D4FAE
> 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
>Priority: Major
>
> 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".
> https://ci.ignite.apache.org/viewLog.html?buildId=3027650
> {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-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&buildTypeId=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] [Commented] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763606#comment-16763606
]
Dmitriy Pavlov commented on IGNITE-11233:
-
Ok, let's move RDD and Platform .NET to standalone issues. I've retriggered
builds for my branch. If it passes now, let's resolve this one.
> 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
>Assignee: Peter Ivanov
>Priority: Critical
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch=ignite-11213&tab=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=buildTypeStatusDiv
> Platform .NET (NuGet)* [ tests 0 Exit Code ]
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=3007897&_focus=904
> {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/Ig
[jira] [Commented] (IGNITE-11266) Platform .NET test failed with Java 11 warning
[
https://issues.apache.org/jira/browse/IGNITE-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763558#comment-16763558
]
Dmitriy Pavlov commented on IGNITE-11266:
-
[~ptupitsyn], could you please take a look at this failure? How can we
reconfigure the tests to ignore the warning (If the warning is the only reason
for the failure)?
> 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
>Priority: Major
>
> 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".
> https://ci.ignite.apache.org/viewLog.html?buildId=3027650
> {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] [Updated] (IGNITE-11265) JVM Crash is often on TeamCity for Java 11 runs
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11265: Attachment: hs_err_pid2458635.log.txt hs_err_pid2431080.log.txt hs_err_pid3473289.log.txt hs_err_pid2674225.log.txt > 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 >Priority: Major > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > > 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] [Commented] (IGNITE-11265) JVM Crash is often on TeamCity for Java 11 runs
[ https://issues.apache.org/jira/browse/IGNITE-11265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763559#comment-16763559 ] Dmitriy Pavlov commented on IGNITE-11265: - [~agoncharuk] could you please take a look at the failure? I suppose we have a bug in our code, and Java 11 just a reproducer for it. > 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 >Priority: Major > Attachments: hs_err_pid2431080.log.txt, hs_err_pid2458635.log.txt, > hs_err_pid2674225.log.txt, hs_err_pid3473289.log.txt > > > 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] [Updated] (IGNITE-11266) Platform .NET test failed with Java 11 warning
[
https://issues.apache.org/jira/browse/IGNITE-11266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11266:
Description:
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".
https://ci.ignite.apache.org/viewLog.html?buildId=3027650
{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}
was:
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}
> 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
>Priority: Major
>
> 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".
> https://ci.ignite.apache.org/viewLog.html?buildId=3027650
> {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-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] [Commented] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763554#comment-16763554
]
Dmitriy Pavlov commented on IGNITE-11216:
-
I don't understand how the fix works, so [~ustas], could you please review this
fix?
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11216:
Ignite Flags: (was: Docs Required)
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Assignee: Peter Ivanov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {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] [Commented] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763481#comment-16763481 ] Dmitriy Pavlov commented on IGNITE-11255: - [~voropava], Please fill ticket description, you may provide a reference to TC runs with failures, stack traces, any other details, which will help to find or fix the issue. > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11255: Ignite Flags: (was: Docs Required) > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11255) Fix test failure after IGNITE-7648
[ https://issues.apache.org/jira/browse/IGNITE-11255?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16763398#comment-16763398 ] Dmitriy Pavlov commented on IGNITE-11255: - Please fill ticket description, you may provide a reference to TC runs with failures, stack traces, any other details, which will help to find or fix the issue. > Fix test failure after IGNITE-7648 > -- > > Key: IGNITE-11255 > URL: https://issues.apache.org/jira/browse/IGNITE-11255 > Project: Ignite > Issue Type: Bug >Reporter: Pavel Voronkin >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762697#comment-16762697
]
Dmitriy Pavlov commented on IGNITE-11155:
-
https://ci.ignite.apache.org/viewLog.html?buildId=3027679&buildTypeId=IgniteTests24Java8_RunAll
> 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
>Priority: Major
> Attachments: start-java11.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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] [Commented] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762694#comment-16762694
]
Dmitriy Pavlov commented on IGNITE-11153:
-
[~ustas] thank you for review.
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762688#comment-16762688
]
Dmitriy Pavlov commented on IGNITE-11155:
-
[~dmagda], [~agoncharuk], do you think this warning is enough?
!start-java11.png!
> 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
>Priority: Major
> Attachments: start-java11.png
>
>
> 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] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Attachment: start-java11.png
> 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
>Priority: Major
> Attachments: start-java11.png
>
>
> 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] [Updated] (IGNITE-11239) SPI and JDBC driver tests failed because of SSL connection timeout for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11239: Ignite Flags: (was: Docs Required) > SPI and JDBC driver tests failed because of SSL connection timeout for Java 11 > -- > > Key: IGNITE-11239 > URL: https://issues.apache.org/jira/browse/IGNITE-11239 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Priority: Major > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi&branch=ignite-11155&tab=buildTypeStatusDiv > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&branch=ignite-11155&tab=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] [Commented] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16762602#comment-16762602
]
Dmitriy Pavlov commented on IGNITE-11153:
-
[~ARomantsov], thank you for checking these changes. [~vveider] thank you for
contribution.
Merged to master
https://github.com/apache/ignite/commit/e70a3b4dd973a9a8dc7a77c61900304fd5512e48
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Dmitriy Pavlov
>Assignee: Peter Ivanov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> 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] [Updated] (IGNITE-11239) SPI and JDBC driver tests failed because of SSL connection timeout for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11239: Summary: SPI and JDBC driver tests failed because of SSL connection timeout for Java 11 (was: SPI and JDBC driver tests failed because of SSL connection timeout) > SPI and JDBC driver tests failed because of SSL connection timeout for Java 11 > -- > > Key: IGNITE-11239 > URL: https://issues.apache.org/jira/browse/IGNITE-11239 > Project: Ignite > Issue Type: Task >Reporter: Dmitriy Pavlov >Priority: Major > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi&branch=ignite-11155&tab=buildTypeStatusDiv > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&branch=ignite-11155&tab=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] [Updated] (IGNITE-11239) SPI and JDBC driver tests failed because of SSL connection timeout
[ https://issues.apache.org/jira/browse/IGNITE-11239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11239: Issue Type: Task (was: Bug) > 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: Task >Reporter: Dmitriy Pavlov >Priority: Major > > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Spi&branch=ignite-11155&tab=buildTypeStatusDiv > https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&branch=ignite-11155&tab=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-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&branch=ignite-11155&tab=buildTypeStatusDiv https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JdbcDriver&branch=ignite-11155&tab=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] [Commented] (IGNITE-11030) Cache page corruption after a page being rotated having partition ID=0
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761771#comment-16761771
]
Dmitriy Pavlov commented on IGNITE-11030:
-
Please note ticket fix containing 2 commits
https://github.com/apache/ignite/commit/ec488539933f1cafa0756c7d2bd22b48f0c1e16b
https://github.com/apache/ignite/commit/a486278646cfb40f1b5a37da00c0282dad4872ba
2nd is test failure fix. Test was added in first commit
> Cache page corruption after a page being rotated having partition ID=0
> --
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> - 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
[jira] [Updated] (IGNITE-11213) A number of suites failed because of maven-surefire-plugin NPE for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11213:
Fix Version/s: 2.8
> 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
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> See, for example, Logging Run Config failure at
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=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] [Updated] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11233:
Ignite Flags: (was: Docs Required)
> 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
>Priority: Critical
>
> _Javadoc_ [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch=ignite-11213&tab=buildTypeStatusDiv
> SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
> RDD* [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
> JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
> https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=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/te
[jira] [Updated] (IGNITE-11233) Ignite Build for Java 11 does not reuse ignite-tools from Build Apache Ignite for some configurations, Compilation error
[
https://issues.apache.org/jira/browse/IGNITE-11233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11233:
Description:
_Javadoc_ [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Javadoc&branch=ignite-11213&tab=buildTypeStatusDiv
SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
RDD* [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=buildTypeStatusDiv
Platform .NET (NuGet)* [ tests 0 Exit Code ]
https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=3007897&_focus=904
{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
org.apache.ignite.too
[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&branch=ignite-11213&tab=buildTypeStatusDiv
SPI (URI Deploy) [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_SpiUriDeploy&branch=ignite-11213&tab=buildTypeStatusDiv
RDD* [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_Rdd&branch=ignite-11213&tab=buildTypeStatusDiv
JCache TCK 1.1 [ tests 0 Exit Code , Compilation Error ]
https://ci.ignite.apache.org/viewType.html?buildTypeId=IgniteTests24Java8_JCacheTck11&branch=ignite-11213&tab=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] lo
[jira] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB & RMI dependencies
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761681#comment-16761681
]
Dmitriy Pavlov commented on IGNITE-11191:
-
No, I've checked results with JDK11, but locally I have 8, so there is minimal
risk of failure.
Thank you for review.
> Fix Hibernate integration by providing JAXB & RMI dependencies
> --
>
> Key: IGNITE-11191
> URL: https://issues.apache.org/jira/browse/IGNITE-11191
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Commented] (IGNITE-11213) A number of suites failed because of maven-surefire-plugin NPE for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761657#comment-16761657
]
Dmitriy Pavlov commented on IGNITE-11213:
-
[~vveider], could you please take a look at PR
https://github.com/apache/ignite/pull/6041
? Mentioned run now contains a number of compilation errors instead of just
exit codes, so plugin update seems to be not harmful.
> 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
>Assignee: Dmitriy Pavlov
>Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> See, for example, Logging Run Config failure at
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=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] [Commented] (IGNITE-11216) Ignite.sh fails on Mac OS and Linux - Java 11
[
https://issues.apache.org/jira/browse/IGNITE-11216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761649#comment-16761649
]
Dmitriy Pavlov commented on IGNITE-11216:
-
[~vveider] WDYT if this issue can be fixed by [IGNITE-11153] change?
> Ignite.sh fails on Mac OS and Linux - Java 11
> -
>
> Key: IGNITE-11216
> URL: https://issues.apache.org/jira/browse/IGNITE-11216
> Project: Ignite
> Issue Type: Task
>Affects Versions: 2.7
>Reporter: Denis Magda
>Priority: Blocker
>
> Ignite.sh fails on Mac OS Mojave with the following JDK version:
> java version "11.0.2" 2019-01-15 LTS
> Java(TM) SE Runtime Environment 18.9 (build 11.0.2+9-LTS)
> Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.2+9-LTS, mixed mode)
> The same issue is reproduced on Linux and the workaround is discussed here:
> https://issues.apache.org/jira/browse/IGNITE-3
> The exception is as follows:
> {noformat}
> /Users/dmagda/Downloads/apache-ignite-2.7.0-bin/bin/include/functions.sh:
> line 40: [: -eq: unary operator expected
> ./ignite.sh: line 152: [: -eq: unary operator expected
> ./ignite.sh: line 157: [: -gt: unary operator expected
> ./ignite.sh: line 170: [: -eq: unary operator expected
> WARNING: An illegal reflective access operation has occurred
> WARNING: Illegal reflective access by
> org.apache.ignite.internal.util.GridUnsafe$2
> (file:/Users/dmagda/Downloads/apache-ignite-2.7.0-bin/libs/ignite-core-2.7.0.jar)
> to field java.nio.Buffer.address
> WARNING: Please consider reporting this to the maintainers of
> org.apache.ignite.internal.util.GridUnsafe$2
> WARNING: Use --illegal-access=warn to enable warnings of further illegal
> reflective access operations
> WARNING: All illegal access operations will be denied in a future release
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:795)
> at
> org.apache.ignite.lang.IgniteProductVersion.fromString(IgniteProductVersion.java:305)
> at
> org.apache.ignite.internal.IgniteVersionUtils.(IgniteVersionUtils.java:71)
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.(CommandLineStartup.java:99)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class
> is unavailable.
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
> at
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
> ... 4 more
> Caused by: java.lang.IllegalAccessException: class
> org.apache.ignite.internal.util.GridUnsafe cannot access class
> jdk.internal.misc.SharedSecrets (in module java.base) because module
> java.base does not export jdk.internal.misc to unnamed module @4f83df68
> at
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
> at java.base/java.lang.reflect.Method.invoke(Method.java:558)
> at
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
> ... 5 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (IGNITE-11205) Cache (Restarts) 1 flaky tests
[ https://issues.apache.org/jira/browse/IGNITE-11205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761646#comment-16761646 ] Dmitriy Pavlov commented on IGNITE-11205: - Feel free to reopen once you can provide details. > Cache (Restarts) 1 flaky tests > -- > > Key: IGNITE-11205 > URL: https://issues.apache.org/jira/browse/IGNITE-11205 > Project: Ignite > Issue Type: Improvement >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB & RMI dependencies
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761644#comment-16761644
]
Dmitriy Pavlov commented on IGNITE-11191:
-
[~tledkov-gridgain], could you please review PR
https://github.com/apache/ignite/pull/6029 ?
> Fix Hibernate integration by providing JAXB & RMI dependencies
> --
>
> Key: IGNITE-11191
> URL: https://issues.apache.org/jira/browse/IGNITE-11191
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Resolved] (IGNITE-11205) Cache (Restarts) 1 flaky tests
[ https://issues.apache.org/jira/browse/IGNITE-11205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-11205. - Resolution: Invalid > Cache (Restarts) 1 flaky tests > -- > > Key: IGNITE-11205 > URL: https://issues.apache.org/jira/browse/IGNITE-11205 > Project: Ignite > Issue Type: Improvement >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB & RMI dependencies
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16761643#comment-16761643
]
Dmitriy Pavlov commented on IGNITE-11191:
-
Hibernate tests were fixed by these 3 changes.
> Fix Hibernate integration by providing JAXB & RMI dependencies
> --
>
> Key: IGNITE-11191
> URL: https://issues.apache.org/jira/browse/IGNITE-11191
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Commented] (IGNITE-11213) A number of suites failed because of maven-surefire-plugin NPE for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760969#comment-16760969
]
Dmitriy Pavlov commented on IGNITE-11213:
-
https://ci.ignite.apache.org/viewQueued.html?itemId=3007922&tab=queuedBuildOverviewTab&branch_IgniteTests24Java8=ignite-11213
> 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
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> See, for example, Logging Run Config failure at
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=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] [Updated] (IGNITE-11213) A number of suites failed because of maven-surefire-plugin NPE for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11213:
Ignite Flags: (was: Docs Required)
> 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
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> See, for example, Logging Run Config failure at
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=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] [Updated] (IGNITE-11196) A number of suites failed because of maven-enforcer-plugin failure for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11196:
Summary: A number of suites failed because of maven-enforcer-plugin failure
for Java 11 build (was: A number of suited failed because of
maven-enforcer-plugin failure for Java 11 build)
> A number of suites 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
>Priority: Major
> Fix For: 2.8
>
>
> 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&logTab=tree&filter=debug&expand=all&buildId=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] [Assigned] (IGNITE-11213) A number of suites failed because of maven-surefire-plugin NPE for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11213?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov reassigned IGNITE-11213:
---
Assignee: Dmitriy Pavlov
> 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
>Assignee: Dmitriy Pavlov
>Priority: Major
>
> See, for example, Logging Run Config failure at
> https://ci.ignite.apache.org/viewLog.html?tab=buildLog&logTab=tree&filter=debug&expand=all&buildId=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-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&logTab=tree&filter=debug&expand=all&buildId=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] [Commented] (IGNITE-11205) Cache (Restarts) 1 flaky tests
[ https://issues.apache.org/jira/browse/IGNITE-11205?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760876#comment-16760876 ] Dmitriy Pavlov commented on IGNITE-11205: - [~mstepachev], please fill ticket description. For test failures, you may provide a stack trace of failure(s), links to TeamCity and any other data, which may be helpful in test fix. Issues without description are discouraged by How To Contribute, and, almost always, are not clear for community members. > Cache (Restarts) 1 flaky tests > -- > > Key: IGNITE-11205 > URL: https://issues.apache.org/jira/browse/IGNITE-11205 > Project: Ignite > Issue Type: Improvement >Reporter: Stepachev Maksim >Assignee: Stepachev Maksim >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (IGNITE-11191) Fix Hibernate integration by providing JAXB & RMI dependencies
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11191:
Summary: Fix Hibernate integration by providing JAXB & RMI dependencies
(was: Fix Hibernate integration by providing JAXB dependency during compile)
> Fix Hibernate integration by providing JAXB & RMI dependencies
> --
>
> Key: IGNITE-11191
> URL: https://issues.apache.org/jira/browse/IGNITE-11191
> Project: Ignite
> Issue Type: Bug
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760861#comment-16760861
]
Dmitriy Pavlov commented on IGNITE-11191:
-
https://ci.ignite.apache.org/viewQueued.html?itemId=3007063&tab=queuedBuildOverviewTab&branch_IgniteTests24Java8=ignite-11191
> 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
>Priority: Major
> Fix For: 2.8
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Commented] (IGNITE-11189) Support Java 11 for Apache Ignite
[ https://issues.apache.org/jira/browse/IGNITE-11189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760858#comment-16760858 ] Dmitriy Pavlov commented on IGNITE-11189: - https://blog.codefx.org/java/java-11-migration-guide/ > 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 >Priority: Major > > 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] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760791#comment-16760791
]
Dmitriy Pavlov commented on IGNITE-11191:
-
After providing missing JAXB impl, new failure is
{noformat}
java.lang.NoClassDefFoundError: javax/rmi/PortableRemoteObject
at java.base/java.lang.ClassLoader.defineClass1(Native Method)
at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1016)
at
java.base/java.security.SecureClassLoader.defineClass(SecureClassLoader.java:174)
at
java.base/java.net.URLClassLoader.defineClass(URLClassLoader.java:550)
at java.base/java.net.URLClassLoader$1.run(URLClassLoader.java:458)
at java.base/java.net.URLClassLoader$1.run(URLClassLoader.java:452)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:451)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at
org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:100)
at org.objectweb.jotm.Jotm.(Jotm.java:145)
at
org.apache.ignite.cache.hibernate.HibernateL2CacheTransactionalSelfTest.beforeTestsStarted(HibernateL2CacheTransactionalSelfTest.java:78)
at
org.apache.ignite.testframework.junits.GridAbstractTest.beforeFirstTest(GridAbstractTest.java:631)
at
org.apache.ignite.testframework.junits.GridAbstractTest.lambda$clsRule$1(GridAbstractTest.java:272)
at
org.apache.ignite.testframework.junits.GridAbstractTestWithAssumption.handleAssumption(GridAbstractTestWithAssumption.java:37)
at
org.apache.ignite.testframework.junits.GridAbstractTest.clsRule(GridAbstractTest.java:281)
at
org.apache.ignite.testframework.junits.GridAbstractTest.access$700(GridAbstractTest.java:151)
at
org.apache.ignite.testframework.junits.GridAbstractTest$ClassRuleWrapper.apply(GridAbstractTest.java:2524)
at
org.apache.ignite.testframework.junits.GridAbstractTest$ClassRuleWrapper.access$600(GridAbstractTest.java:2507)
at
org.apache.ignite.testframework.junits.GridAbstractTest$ClassRuleWrapper$1.evaluate(GridAbstractTest.java:2515)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.junit.runners.Suite.runChild(Suite.java:127)
at org.junit.runners.Suite.runChild(Suite.java:26)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:369)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeWithRerun(JUnit4Provider.java:275)
at
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:239)
at
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:160)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at
org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray2(ReflectionUtils.java:206)
at
org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:160)
at
org.apache.maven.surefire.booter.ProviderFactory.invokeProvider(ProviderFactory.java:83)
at
org.apache.maven.plugin.surefire.InPluginVMSurefireStarter.runSuitesInProcess(InPluginVMSurefireStarter.java:84)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1107)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
at
org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:137)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:210)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:156)
at
org.apache.mave
[jira] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760712#comment-16760712
]
Dmitriy Pavlov commented on IGNITE-11191:
-
After providing API dependency new failure is about missing of implementation:
{noformat}
... 12 more
Caused by: java.lang.ClassNotFoundException: com.sun.xml.bind.v2.ContextFactory
at java.base/java.net.URLClassLoader.findClass(URLClassLoader.java:471)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:588)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)
at
org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:100)
at javax.xml.bind.ContextFinder.newInstance(ContextFinder.java:192)
... 16 more
{noformat}
> 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
>Priority: Major
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Updated] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11191:
Fix Version/s: 2.8
> 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
>Priority: Major
> Fix For: 2.8
>
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Commented] (IGNITE-11196) A number of suited failed because of maven-enforcer-plugin failure for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760711#comment-16760711
]
Dmitriy Pavlov commented on IGNITE-11196:
-
This fix affected 4 suites. The new exception is compilation error (related to
tools/change of API for Java Doclets).
Merged to master.
https://gitbox.apache.org/repos/asf?p=ignite.git;a=commit;h=8cba313c9961b16e358834216e9992310f285985
[~vveider] thank you for finding out a reason. WDYT about reopening this ticket
for further research? or do you prefer to create a new one?
> 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
>Priority: Major
> Fix For: 2.8
>
>
> 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&logTab=tree&filter=debug&expand=all&buildId=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] [Updated] (IGNITE-11196) A number of suited failed because of maven-enforcer-plugin failure for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11196:
Fix Version/s: 2.8
> 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
>Priority: Major
> Fix For: 2.8
>
>
> 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&logTab=tree&filter=debug&expand=all&buildId=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] [Commented] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16760201#comment-16760201
]
Dmitriy Pavlov commented on IGNITE-11191:
-
https://ci.ignite.apache.org/viewQueued.html?itemId=2999419&tab=queuedBuildOverviewTab&branch_IgniteTests24Java8=ignite-11191
> 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
>Priority: Major
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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] [Updated] (IGNITE-11191) Fix Hibernate integration by providing JAXB dependency during compile
[
https://issues.apache.org/jira/browse/IGNITE-11191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11191:
Ignite Flags: (was: Docs Required)
> 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
>Priority: Major
>
> https://ci.ignite.apache.org/viewLog.html?buildId=2973733&tab=buildResultsDiv&buildTypeId=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-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] [Commented] (IGNITE-11104) Remove Java 7 and AI 1.x leftovers from IgniteSystemProperties & IgniteProductVersion
[ https://issues.apache.org/jira/browse/IGNITE-11104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759950#comment-16759950 ] Dmitriy Pavlov commented on IGNITE-11104: - LGTM, [~ilyak], could you please merge the change? Thank you for making the code more clear. > Remove Java 7 and AI 1.x leftovers from IgniteSystemProperties & > IgniteProductVersion > - > > Key: IGNITE-11104 > URL: https://issues.apache.org/jira/browse/IGNITE-11104 > Project: Ignite > Issue Type: Improvement > Components: general >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > IGNITE_FORCE_START_JAVA7 can no longer do anything useful, for example. > Should remove it right away since it's noop. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11196) A number of suited failed because of maven-enforcer-plugin failure for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759914#comment-16759914
]
Dmitriy Pavlov commented on IGNITE-11196:
-
TC with fix was started:
https://ci.ignite.apache.org/viewQueued.html?itemId=2996903&tab=queuedBuildOverviewTab&branch_IgniteTests24Java8=ignite-11155
> 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
>Priority: Major
>
> 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&logTab=tree&filter=debug&expand=all&buildId=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-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&logTab=tree&filter=debug&expand=all&buildId=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&buildTypeId=IgniteTests24Java8_PlatformCWinX64Release&tab=buildResultsDiv&branch_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] [Updated] (IGNITE-11195) Platform C++ tests failed to find JVM for Java 11 build
[
https://issues.apache.org/jira/browse/IGNITE-11195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11195:
Ignite Flags: (was: Docs Required)
> 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
>Priority: Major
>
> 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&buildTypeId=IgniteTests24Java8_PlatformCWinX64Release&tab=buildResultsDiv&branch_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-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&tab=buildResultsDiv&buildTypeId=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-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&tab=buildResultsDiv&buildTypeId=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] [Commented] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759836#comment-16759836
]
Dmitriy Pavlov commented on IGNITE-11153:
-
[~vveider], [~agoncharuk], I still need assistance here. I'm not an expert in
sh scripts.
Of course, I can prepare a PR. - It will be more likely to have bugs in it than
PR prepared by an expert.
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> 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-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] [Updated] (IGNITE-11153) Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules for java.xml.bind
[
https://issues.apache.org/jira/browse/IGNITE-11153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11153:
Summary: Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd
--add-modules for java.xml.bind (was: Support Java 11 for control.sh)
> Support Java 11 for control.sh & ignitevisorcmd.sh: remove odd --add-modules
> for java.xml.bind
> --
>
> Key: IGNITE-11153
> URL: https://issues.apache.org/jira/browse/IGNITE-11153
> Project: Ignite
> Issue Type: Task
>Reporter: Dmitriy Pavlov
>Priority: Major
>
> 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] [Resolved] (IGNITE-11140) Check and fix Ignite examples for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov resolved IGNITE-11140. - Resolution: Fixed Fixed in master, all changes were related not to Java 11, but to compilation itself. See short description how to run examples using Java 9+ here: https://github.com/apache/ignite/tree/master/examples#running-examples-on-jdk-91011 > 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 >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Apache Ignite has a nightly release builds > https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&branch_Releases_NightlyRelease=%3Cdefault%3E&tab=buildTypeStatusDiv > 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-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] [Updated] (IGNITE-11105) [TC Bot] Support Teamcity servers aliases
[ https://issues.apache.org/jira/browse/IGNITE-11105?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11105: Ignite Flags: (was: Docs Required) > [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 >Priority: Minor > Time Spent: 20m > Remaining Estimate: 0h > > 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] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758947#comment-16758947
]
Dmitriy Pavlov commented on IGNITE-11155:
-
Need to check trace
{noformat}
Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class is
unavailable.
at
org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1453)
at
org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:112)
... 90 more
Caused by: java.lang.IllegalAccessException: class
org.apache.ignite.internal.util.GridUnsafe cannot access class
jdk.internal.misc.SharedSecrets (in module java.base) because module java.base
does not export jdk.internal.misc to unnamed module @359f4dee
at
java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
at
java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:591)
at java.base/java.lang.reflect.Method.invoke(Method.java:558)
at
org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1450)
... 91 more{noformat}
> 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
>Priority: Major
>
> 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] [Updated] (IGNITE-11140) Check and fix Ignite examples for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11140: Description: Apache Ignite has a nightly release builds https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&branch_Releases_NightlyRelease=%3Cdefault%3E&tab=buildTypeStatusDiv These builds contain examples, as well as releases. It is required to check these release builds for examples compatibility with Java 11 was: 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 > 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 >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Apache Ignite has a nightly release builds > https://ci.ignite.apache.org/viewType.html?buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&branch_Releases_NightlyRelease=%3Cdefault%3E&tab=buildTypeStatusDiv > 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] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Ignite Flags: (was: Docs Required)
> 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
>Priority: Major
>
> 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] [Commented] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757400#comment-16757400
]
Dmitriy Pavlov commented on IGNITE-11155:
-
https://ci.ignite.apache.org/viewLog.html?buildId=2963881&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155
> 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
>Priority: Major
>
> 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] [Comment Edited] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757400#comment-16757400
]
Dmitriy Pavlov edited comment on IGNITE-11155 at 1/31/19 3:57 PM:
--
RunAll using java 11:
https://ci.ignite.apache.org/viewLog.html?buildId=2963881&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155
was (Author: dpavlov):
https://ci.ignite.apache.org/viewLog.html?buildId=2963881&tab=buildResultsDiv&buildTypeId=IgniteTests24Java8_RunAll&branch_IgniteTests24Java8=ignite-11155
> 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
>Priority: Major
>
> 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] [Commented] (IGNITE-11140) Check and fix Ignite examples for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16757191#comment-16757191 ] Dmitriy Pavlov commented on IGNITE-11140: - Alexey, thank you for review. Merged to master. I will resolve the issue after checking our next nightly build. > 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 >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > 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] [Updated] (IGNITE-11030) Cache page corruption after a page being rotated having partition ID=0
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Summary: Cache page corruption after a page being rotated having partition
ID=0 (was: Teamcity Bot cache is in unrecoverable state after bot restart:
need to check reasons)
> Cache page corruption after a page being rotated having partition ID=0
> --
>
> Key: IGNITE-11030
> URL: https://issues.apache.org/jira/browse/IGNITE-11030
> Project: Ignite
> Issue Type: Bug
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> - 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.evaluateSequ
[jira] [Updated] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Description:
Teamcity Bot cache is in unrecoverable state after bot restart: need to check
reasons
- 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
org.apache.ignite.ci.di.MonitoredTaskInterceptor.invoke(MonitoredTaskInterceptor.java:111)
at
org.apache.ignite.ci.di.AutoProfilingInt
[jira] [Updated] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Issue Type: Bug (was: Task)
> 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: Bug
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Teamcity Bot cache is in unrecoverable state after bot restart: need to check
> reasons
> - 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(ForEachOp
[jira] [Updated] (IGNITE-11030) Teamcity Bot cache is in unrecoverable state after bot restart: need to check reasons
[
https://issues.apache.org/jira/browse/IGNITE-11030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11030:
Priority: Blocker (was: Critical)
> 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
> Components: persistence
>Reporter: Dmitriy Pavlov
>Assignee: Dmitriy Pavlov
>Priority: Blocker
> Fix For: 2.8
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> - 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.j
[jira] [Commented] (IGNITE-11140) Check and fix Ignite examples for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756457#comment-16756457 ] Dmitriy Pavlov commented on IGNITE-11140: - To review README please use link https://github.com/apache/ignite/tree/ignite-11140/examples#apache-ignite-examples > 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 >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > 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] [Updated] (IGNITE-11155) Add JVM options analysis to Ignition.start() or handle and comment exceptions
[
https://issues.apache.org/jira/browse/IGNITE-11155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dmitriy Pavlov updated IGNITE-11155:
Description:
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
was:
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
> 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
>Priority: Major
>
> 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] [Updated] (IGNITE-11140) Check and fix Ignite examples for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmitriy Pavlov updated IGNITE-11140: Fix Version/s: 2.8 > 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 >Priority: Major > Fix For: 2.8 > > Time Spent: 10m > Remaining Estimate: 0h > > 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-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] [Commented] (IGNITE-11140) Check and fix Ignite examples for Java 11
[ https://issues.apache.org/jira/browse/IGNITE-11140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16756117#comment-16756117 ] Dmitriy Pavlov commented on IGNITE-11140: - [~agoncharuk] could you please take a look at [PR|https://github.com/apache/ignite/pull/5978] ? I suppose we should merge it first and tomorrow I could re-check results for a new nightly build. > 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 >Priority: Major > Time Spent: 10m > Remaining Estimate: 0h > > 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-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] [Commented] (IGNITE-11133) Refactoring of compatibility framework
[ https://issues.apache.org/jira/browse/IGNITE-11133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755891#comment-16755891 ] Dmitriy Pavlov commented on IGNITE-11133: - Looks like a very huge change. I suggest discussing this with the community using dev .list.. At least compatibility framework maintainers need to share their opinion. > Refactoring of compatibility framework > -- > > Key: IGNITE-11133 > URL: https://issues.apache.org/jira/browse/IGNITE-11133 > Project: Ignite > Issue Type: Improvement >Reporter: Alexey Platonov >Assignee: Alexey Platonov >Priority: Major > Labels: MakeTeamcityGreenAgain > Time Spent: 10m > Remaining Estimate: 0h > > We need to refactor current compatibility framework with the aim of reducing > maven management logic, simplification adding new versions to check. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11084) Change copyrights to 2019
[ https://issues.apache.org/jira/browse/IGNITE-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755886#comment-16755886 ] Dmitriy Pavlov commented on IGNITE-11084: - Merged. Thank you for contribution. *Note*: This issue fix has 2 commits: https://github.com/apache/ignite/commit/01a5a915c3eaa87b5a2df153a44d19b78ea454c8 https://github.com/apache/ignite/commit/6a51f25da75154e0f89fc6c6a0ee84de538fcc6b > Change copyrights to 2019 > - > > Key: IGNITE-11084 > URL: https://issues.apache.org/jira/browse/IGNITE-11084 > Project: Ignite > Issue Type: Task >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.8 > > Time Spent: 40m > Remaining Estimate: 0h > > Every year copyright date should be changed. We can use the build date for it > or local date for cases when Ignite built from the sources, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11084) Change copyrights to 2019
[ https://issues.apache.org/jira/browse/IGNITE-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16755390#comment-16755390 ] Dmitriy Pavlov commented on IGNITE-11084: - I don't know why TC bot is not working, for me, Visa was added ^. Please share failure details (if any) > Change copyrights to 2019 > - > > Key: IGNITE-11084 > URL: https://issues.apache.org/jira/browse/IGNITE-11084 > Project: Ignite > Issue Type: Task >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.8 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Every year copyright date should be changed. We can use the build date for it > or local date for cases when Ignite built from the sources, -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (IGNITE-11084) Change copyrights to 2019
[ https://issues.apache.org/jira/browse/IGNITE-11084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753925#comment-16753925 ] Dmitriy Pavlov commented on IGNITE-11084: - LGTM, merged to master, [~aealeksandrov] thank you for contribution. > Change copyrights to 2019 > - > > Key: IGNITE-11084 > URL: https://issues.apache.org/jira/browse/IGNITE-11084 > Project: Ignite > Issue Type: Task >Reporter: Andrey Aleksandrov >Assignee: Andrey Aleksandrov >Priority: Major > Fix For: 2.8 > > Time Spent: 20m > Remaining Estimate: 0h > > Every year copyright date should be changed. We can use the build date for it > or local date for cases when Ignite built from the sources, -- 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] [Commented] (IGNITE-10879) Create suite of Cassandra Cache Store tests, add to TC
[ https://issues.apache.org/jira/browse/IGNITE-10879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16753890#comment-16753890 ] Dmitriy Pavlov commented on IGNITE-10879: - LGTM, I'm pretty sure MVCC Cache 9 failure is not related, but it is better to double-check it anyway. > Create suite of Cassandra Cache Store tests, add to TC > -- > > Key: IGNITE-10879 > URL: https://issues.apache.org/jira/browse/IGNITE-10879 > Project: Ignite > Issue Type: Sub-task > Components: cassandra >Affects Versions: 2.7 >Reporter: Ilya Kasnacheev >Assignee: Ilya Kasnacheev >Priority: Major > Labels: test > Time Spent: 20m > Remaining Estimate: 0h > > Currently, they're not running in TC at all -- This message was sent by Atlassian JIRA (v7.6.3#76005)
