Re: Docker image for Apache Ignite with Java 11

[Petr Ivanov]

Hi, Igniters!


Fixed in [1]  ()
s390x-jdk11 and x86_64-jdk11 images are uploaded to [2]
Added build configuration [3] to prepare images during release phase.

Images are not tested, though (checked only that x86_64-jdk11 starts)
Also, will greatly appreciate if someone checks the PR.



[1] https://issues.apache.org/jira/browse/IGNITE-17108
[2] https://hub.docker.com/r/apacheignite/ignite/tags
[3] 
https://ci.ignite.apache.org/buildConfiguration/Releases_ApacheIgniteMain_AssembleDockerImages

> On 6 Jun 2022, at 11:48, Stephen Darlington  
> wrote:
> 
> There is a ticket for this: 
> https://issues.apache.org/jira/browse/IGNITE-14031 
> 
> 
>> On 2 Jun 2022, at 09:48, Surinder Mehra > > wrote:
>> 
>> Yeah hope so
>> 
>> On Thu, 2 Jun 2022, 14:06 Айсина Роза, > > wrote:
>> Hey! 
>> 
>> 
>> 
>> Thank you very much - I have already built the image with Java 11 based on 
>> your similar thread. 
>> 
>> 
>> 
>> But I want to address this problem to the community and Ignite developers. 
>> 
>> It is very painful to build custom image as it is required to have run.sh 
>> script that is not included in standard Ignite bundle. 
>> 
>> Currently I copy it directly from GitHub (with ADD command) but it is a 
>> workaround not a solution. 
>> 
>> 
>> 
>> Hope new image versions will be released!
>> 
>> 
>> 
>> Best regards,
>> 
>> Rose. 
>> 
>> From: Surinder Mehra mailto:redni...@gmail.com>>
>> Sent: Thursday, June 2, 2022 9:33:08 AM
>> To: user@ignite.apache.org 
>> Subject: [POTENTIALLY_MALICIOUS] Re: Docker image for Apache Ignite with 
>> Java 11
>>  
>> **ВНИМАНИЕ** Это письмо содержит подозрительное вложение или ссылку. 
>> Открывать только в случае 100% доверия к отправителю письма.
>> 
>> Hey,
>> I had a similar requirement some time back and created my own. Attached 
>> conversation might be useful for you until ignite  publishes their official 
>> docker image with java 11
>> 
>> 
>> FROM adoptopenjdk/openjdk11
>> 
>> # Settings
>> ARG IGNITE_CFG_XML="node-configuration.xml"
>> ARG IGNITE_VERSION="2.11.0"
>> #ARG OPTION_LIBS="ignite-kubernetes,ignite-rest-http"
>> ENV IGNITE_HOME /opt/ignite/apache-ignite
>> #ENV CONFIG_URI config/$IGNITE_CFG_XML
>> # Disabling quiet mode.
>> ENV IGNITE_QUIET=false
>> WORKDIR /opt/ignite
>> 
>> # Add missing software
>> RUN apt-get update &&\
>> apt-get install bash && \
>> apt-get install -y wget && \
>> apt-get install unzip && \
>> wget https://dlcdn.apache.org 
>> //ignite/${IGNITE_VERSION}/apache-ignite-${IGNITE_VERSION}-bin.zip
>>  && \
>> unzip -o apache-ignite-${IGNITE_VERSION}-bin.zip && \
>> mv apache-ignite-${IGNITE_VERSION}-bin apache-ignite && \
>> rm apache-ignite-${IGNITE_VERSION}-bin.zip
>> 
>> # Copy main binary archive
>> #COPY apache-ignite* apache-ignite
>> 
>> # Copy sh files and set permission
>> COPY run.sh $IGNITE_HOME/
>> COPY ./$IGNITE_CFG_XML $IGNITE_HOME/config
>> # Grant permission to copy optional libs
>> RUN chmod 777 ${IGNITE_HOME}/libs
>> 
>> # Grant permission to create work directory
>> RUN chmod 777 ${IGNITE_HOME}
>> 
>> # Grant permission to execute entry point
>> RUN chmod 555 $IGNITE_HOME/run.sh
>> 
>> # Entry point
>> 
>> RUN export JAVA_HOME="$(dirname $(dirname $(readlink -f $(which java"
>> 
>> CMD $IGNITE_HOME/run.sh
>> 
>> # Container port exposure
>> EXPOSE 11211 47100 47500 49112 10800 8080
>> 
>> On Thu, Jun 2, 2022 at 11:47 AM Айсина Роза > > wrote:
>> Hello!
>> 
>> I am looking for docker image with Apache Ignite using Java 11 instead of 
>> Java 8. 
>> I see that in provided Dockerfiles 
>> (https://github.com/apache/ignite/tree/master/deliveries/docker/apache-ignite
>>  
>> )
>> image for x86_64 uses Java 8 but image for s390x uses Java 11.
>> 
>> Can you please build the same x86-images but with Java 11?
>> 
>> It's extremely painful to build them manually :( 
>> And the reason is that all our Java applications use Java 11 or older and
>> it is not possible to join client node with different Java version. 
>> 
>> Thanks in advance!
>> 
>> Best regards, 
>> 
>> Rose. 
>> 
>> Информация данного сообщения содержит коммерческую тайну Общества с 
>> ограниченной ответственностью «ГПМ Дата», ОГРН 1207700499863 (далее – ООО 
>> «ГПМ Дата») и предназначена только для лиц, которым адресовано данное 
>> сообщение. Если Вы получили данное сообщение по ошибке, просим Вас удалить 
>> его и не использовать полученную информацию, составляющую коммерческую тайну 
>> ООО «ГПМ Дата».
>> 
>> В соответствии с действующим законодательством Российской Федерации ООО «ГПМ 
>> Дата» вправе требовать от лиц, получивших доступ к информации, составляющей 
>> коммерческую тайну, в результате действий, совершенных случайно или по 
>> ошибке, охраны конфиде

Re: DEB install gives "The repository 'http://apache.org/dist/ignite/deb apache-ignite InRelease' is not signed"

[Petr Ivanov]

Hi, Diego.


I've filed [1].


For now, please use the following instructions:

sudo apt update
sudo apt install dirmngr gnupg ca-certificates --no-install-recommends -y

sudo bash -c 'cat < /etc/apt/sources.list.d/ignite.list
deb https://apache.jfrog.io/artifactory/ignite-deb/ apache-ignite main
EOF'

sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 
0EE62FB37A00258D
sudo apt update

sudo apt install apache-ignite --no-install-recommends




[1] https://issues.apache.org/jira/browse/IGNITE-15708

> On 7 Oct 2021, at 18:57, privacyfi...@codesandnotes.be wrote:
> 
> Hello,
> 
> I followed the instructions from 
> https://ignite.apache.org/docs/latest/installation/deb-rpm#installing-deb-package
>  to the letter, but as soon as I do "sudo apt update" I get this:
> 
> E: Failed to fetch 
> http://apache.org/dist/ignite/deb/dists/apache-ignite/InRelease Clearsigned 
> file isn't valid, got 'NOSPLIT' (does the network require authentication?)
> E: The repository 'http://apache.org/dist/ignite/deb apache-ignite InRelease' 
> is not signed.
> N: Updating from such a repository can't be done securely, and is therefore 
> disabled by default.
> N: See apt-secure(8) manpage for repository creation and user configuration 
> details.
> 
> Obviously "sudo apt install apache-ignite" doesn't work because it cannot 
> find the apache-ignite package.
> 
> According to https://issues.apache.org/jira/browse/IGNITE-15381 the 
> repository address should be redirected to the JFrog repo.
> 
> Any ideas on how I can fix this?
> 
> Diego
> 

Re: Ignite test takes several days

[Petr Ivanov]

All components are tied.

Create PR with your patch and run this build [1] using your patch number as 
branch in Changes tab.



[1] 
https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll?mode=builds

> On 9 Sep 2020, at 06:51, Cong Guo  wrote:
> 
> Hi, all
> 
> Thank you for your reply. As mentioned earlier, I want to test ignite-core 
> with a new patch, so -DskipTests is not an option for me. What test suite 
> should I use if I just want to test ignite-core?
> 
> 
> 
> On Tue, Sep 8, 2020 at 5:33 AM Petr Ivanov  <mailto:mr.wei...@gmail.com>> wrote:
> Also, -DskipTests flag can be used to avoid running tests while building 
> Apache Ignite.
> 
>> On 8 Sep 2020, at 12:19, Ilya Kasnacheev > <mailto:ilya.kasnach...@gmail.com>> wrote:
>> 
>> Hello!
>> 
>> You should never try to run all Ignite tests. They are not supposed to be 
>> run in that way. You should always build with -DskipTests.
>> 
>> If you really want to run Ignite tests, you should run this test suite 
>> against your PR: 
>> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects
>>  
>> <https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects>
>> This is the only meaningful way.
>> Then you can use MTCGA to check your test results: 
>> https://mtcga.gridgain.com/ <https://mtcga.gridgain.com/>
>> 
>> Obviously, you need to create account in Apache Ignite CI.
>> 
>> Regards,
>> -- 
>> Ilya Kasnacheev
>> 
>> 
>> чт, 27 авг. 2020 г. в 16:33, Cong Guo > <mailto:nadbpwa...@gmail.com>>:
>> Hi,
>> 
>> I try to build the ignite-core on my workstation. I use the original 
>> ignite-2.8.1 source package. The test, specifically 
>> GridCacheWriteBehindStoreLoadTest, has been running for several days. Is it 
>> normal? I run "mvn clean package" directly. Should I configure anything in 
>> advance? Thank you.  
> 

Re: Ignite test takes several days

[Petr Ivanov]

Also, -DskipTests flag can be used to avoid running tests while building Apache 
Ignite.

> On 8 Sep 2020, at 12:19, Ilya Kasnacheev  wrote:
> 
> Hello!
> 
> You should never try to run all Ignite tests. They are not supposed to be run 
> in that way. You should always build with -DskipTests.
> 
> If you really want to run Ignite tests, you should run this test suite 
> against your PR: 
> https://ci.ignite.apache.org/buildConfiguration/IgniteTests24Java8_RunAll#all-projects
>  
> 
> This is the only meaningful way.
> Then you can use MTCGA to check your test results: 
> https://mtcga.gridgain.com/ 
> 
> Obviously, you need to create account in Apache Ignite CI.
> 
> Regards,
> -- 
> Ilya Kasnacheev
> 
> 
> чт, 27 авг. 2020 г. в 16:33, Cong Guo  >:
> Hi,
> 
> I try to build the ignite-core on my workstation. I use the original 
> ignite-2.8.1 source package. The test, specifically 
> GridCacheWriteBehindStoreLoadTest, has been running for several days. Is it 
> normal? I run "mvn clean package" directly. Should I configure anything in 
> advance? Thank you.  

Re: apache-ignite_2.8.0-1_all.deb package has older version of openjdk as dependency

[Petr Ivanov]

Iliya, thanks for the review/merge.


Rakshita, you can use patch on 2.8.1 branch/tag and rebuild deb that will 
suites you or indeed wait for 2.9.0 if it will be included.



> On 7 Sep 2020, at 18:57, Ilya Kasnacheev  wrote:
> 
> Thank you for the fix!
> 
> + alex
> I wonder if it can be included in 2.9. It's an one-liner in package build 
> script. I'll do it if you acknowledge.
> 
> Regards,
> -- 
> Ilya Kasnacheev
> 
> 
> пн, 7 сент. 2020 г. в 17:29, Petr Ivanov  <mailto:mr.wei...@gmail.com>>:
> Thanks!
> 
> 
> Applied your suggestions.
> 
>> On 7 Sep 2020, at 16:45, Ilya Kasnacheev > <mailto:ilya.kasnach...@gmail.com>> wrote:
>> 
>> Hello!
>> 
>> I have replied in the PR.
>> 
>> Regards,
>> -- 
>> Ilya Kasnacheev
>> 
>> 
>> чт, 27 авг. 2020 г. в 17:26, Petr Ivanov > <mailto:mr.wei...@gmail.com>>:
>> https://issues.apache.org/jira/browse/IGNITE-13388 
>> <https://issues.apache.org/jira/browse/IGNITE-13388> is ready for review.
>> Iliya, can you help with it?
>> 
>> 
>> 
>>> On 27 Aug 2020, at 12:26, Petr Ivanov >> <mailto:mr.wei...@gmail.com>> wrote:
>>> 
>>> Hi!
>>> 
>>> 
>>> As a temporary workaround, please see this article [1].
>>> Meanwhile, I will try to figure out how to create more generalised JDK 
>>> dependency.
>>> 
>>> 
>>> 
>>> [1] 
>>> https://stackoverflow.com/questions/57031649/how-to-install-openjdk-8-jdk-on-debian-10-buster
>>>  
>>> <https://stackoverflow.com/questions/57031649/how-to-install-openjdk-8-jdk-on-debian-10-buster>
>>> 
>>> 
>>>> On 6 May 2020, at 07:27, rakshita04 >>> <mailto:rakshita.chaudh...@siemens.com>> wrote:
>>>> 
>>>> Hi Team,
>>>> 
>>>> We are using apache-ignite for our C++ application based on debian
>>>> 10(buster). We tried using apache-ignite_2.8.0-1_all.deb package but it
>>>> depends on openjdk-8 which is older version and not available for debian 10
>>>> buster. I have below questions-
>>>> 1. Why older version of openjdk is used in deb package?
>>>> 2. Is there any possibility of new released version of deb package with
>>>> source apache-ignite_2.8.0 with newer openjdk version?
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
>>>> <http://apache-ignite-users.70518.x6.nabble.com/>
>>> 
>> 
> 

Re: apache-ignite_2.8.0-1_all.deb package has older version of openjdk as dependency

[Petr Ivanov]

Thanks!


Applied your suggestions.

> On 7 Sep 2020, at 16:45, Ilya Kasnacheev  wrote:
> 
> Hello!
> 
> I have replied in the PR.
> 
> Regards,
> -- 
> Ilya Kasnacheev
> 
> 
> чт, 27 авг. 2020 г. в 17:26, Petr Ivanov  <mailto:mr.wei...@gmail.com>>:
> https://issues.apache.org/jira/browse/IGNITE-13388 
> <https://issues.apache.org/jira/browse/IGNITE-13388> is ready for review.
> Iliya, can you help with it?
> 
> 
> 
>> On 27 Aug 2020, at 12:26, Petr Ivanov > <mailto:mr.wei...@gmail.com>> wrote:
>> 
>> Hi!
>> 
>> 
>> As a temporary workaround, please see this article [1].
>> Meanwhile, I will try to figure out how to create more generalised JDK 
>> dependency.
>> 
>> 
>> 
>> [1] 
>> https://stackoverflow.com/questions/57031649/how-to-install-openjdk-8-jdk-on-debian-10-buster
>>  
>> <https://stackoverflow.com/questions/57031649/how-to-install-openjdk-8-jdk-on-debian-10-buster>
>> 
>> 
>>> On 6 May 2020, at 07:27, rakshita04 >> <mailto:rakshita.chaudh...@siemens.com>> wrote:
>>> 
>>> Hi Team,
>>> 
>>> We are using apache-ignite for our C++ application based on debian
>>> 10(buster). We tried using apache-ignite_2.8.0-1_all.deb package but it
>>> depends on openjdk-8 which is older version and not available for debian 10
>>> buster. I have below questions-
>>> 1. Why older version of openjdk is used in deb package?
>>> 2. Is there any possibility of new released version of deb package with
>>> source apache-ignite_2.8.0 with newer openjdk version?
>>> 
>>> 
>>> 
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
>>> <http://apache-ignite-users.70518.x6.nabble.com/>
>> 
> 

Re: apache-ignite_2.8.0-1_all.deb package has older version of openjdk as dependency

[Petr Ivanov]

https://issues.apache.org/jira/browse/IGNITE-13388 
<https://issues.apache.org/jira/browse/IGNITE-13388> is ready for review.
Iliya, can you help with it?



> On 27 Aug 2020, at 12:26, Petr Ivanov  wrote:
> 
> Hi!
> 
> 
> As a temporary workaround, please see this article [1].
> Meanwhile, I will try to figure out how to create more generalised JDK 
> dependency.
> 
> 
> 
> [1] 
> https://stackoverflow.com/questions/57031649/how-to-install-openjdk-8-jdk-on-debian-10-buster
> 
> 
>> On 6 May 2020, at 07:27, rakshita04  wrote:
>> 
>> Hi Team,
>> 
>> We are using apache-ignite for our C++ application based on debian
>> 10(buster). We tried using apache-ignite_2.8.0-1_all.deb package but it
>> depends on openjdk-8 which is older version and not available for debian 10
>> buster. I have below questions-
>> 1. Why older version of openjdk is used in deb package?
>> 2. Is there any possibility of new released version of deb package with
>> source apache-ignite_2.8.0 with newer openjdk version?
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
> 

Re: apache-ignite_2.8.0-1_all.deb package has older version of openjdk as dependency

[Petr Ivanov]

Hi!


As a temporary workaround, please see this article [1].
Meanwhile, I will try to figure out how to create more generalised JDK 
dependency.



[1] 
https://stackoverflow.com/questions/57031649/how-to-install-openjdk-8-jdk-on-debian-10-buster


> On 6 May 2020, at 07:27, rakshita04  wrote:
> 
> Hi Team,
> 
> We are using apache-ignite for our C++ application based on debian
> 10(buster). We tried using apache-ignite_2.8.0-1_all.deb package but it
> depends on openjdk-8 which is older version and not available for debian 10
> buster. I have below questions-
> 1. Why older version of openjdk is used in deb package?
> 2. Is there any possibility of new released version of deb package with
> source apache-ignite_2.8.0 with newer openjdk version?
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: apache-ignite_2.8.0-1_all.deb package has older version of openjdk as dependency

[Petr Ivanov]

Hi, Artem,


Can you file and issue with description what exactly do not work and why, 
please?


> On 27 Aug 2020, at 11:55, Artem Budnikov  wrote:
> 
> Looks like this issue wasn't fixed in 2.8.1. The Ignite deb package v. 2.8.1 
> can't be installed on debian 10:
> 
> 
>> $ sudo apt-get install apache-ignite
>> ...
>> The following packages have unmet dependencies:
>>  apache-ignite : Depends: openjdk-8-jdk but it is not installable or
>> oracle-java8-installer but it is not installable
>> E: Unable to correct problems, you have held broken packages.
> 
> 
> Is anyone working on this? I was going to update the Ignite 2.9 installation 
> instruction for Debian, but if the issue is staying with us, I guess I 
> shouldn't bother.
> 
> -Artem
> 
> On 27.05.2020 11:55, Ilya Kasnacheev wrote:
>> Hello!
>> 
>> You can build debian package from apache-ignite source deliverable. There 
>> you can fix the dependency.
>> 
>> Regards,
>> -- 
>> Ilya Kasnacheev
>> 
>> 
>> ср, 27 мая 2020 г. в 11:51, rakshita04 > >:
>> Can we have the newer debian package for apache ignite with newer version of
>> openjdk as dependencies?
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
>> 

Re: build failure for module hibernate 5.3

[Petr Ivanov]

HI!


Try adding this repository to your settings.xml: 
https://repository.ow2.org/nexus/content/repositories/public/ 




> On 11 Aug 2020, at 20:53, Tathagata Roy  
> wrote:
> 
> I am trying to do a poc on using apache ignite as hibernate 2nd level cache, 
> following the example given 
> https://apacheignite-mix.readme.io/v2.1/docs/hibernate-l2-cache#maven-configuration
>  
> .
>  
> Since we are using Hibernate 5.3.7 in Spring Boot, I need to use 
> ignite-hibernate_5.3. Unfortunately this artifact id is not present in any 
> public maven repository, hence as mentioned 
> https://apacheignite.readme.io/docs/maven-setup# 
>  i need to build it locally 
> and push it to my maven repository.
>  
> When I am trying to build using the command  
>  
> mvn clean install -DskipTests -Plgpl -pl modules/hibernate -am
>  
> I am getting the error 
>  
> The following artifacts could not be resolved: 
> org.jacorb:jacorb:jar:2.2.3-jonas-patch-20071018, 
> org.jacorb:jacorb-idl:jar:2.2.3-jonas-patch-20071018
>  
>  
> I am not seeing any reference to the org.jacorb:jacorb , 
> org.jacorb:jacorb-idl in any pom nor is it available in any public 
> repository. This is happening for both 2.8.1 tag and also current SNAPSHOT 
> What should be done to fix it, or is there some public repository where is 
> can get ignite-hibernate_5.3?

Re: Amazon AMI not available in a specific region

[Petr Ivanov]

Dmitriy, can you help?



> On 25 Jun 2020, at 09:43, Petr Ivanov  wrote:
> 
> AMI is not being update with release — it uses Docker inside that receive 
> VERSION as parameters and pulls corresponding image from Docker Hub.
> 
> Concerning image itself, I will try to search which account owns it.
> 
> 
>> On 24 Jun 2020, at 18:31, Denis Magda > <mailto:dma...@apache.org>> wrote:
>> 
>> Ignite dev community,
>> 
>> Could you remind me if we still updating the AWS images for our releases? If 
>> yes, how about expanding a list of supported regions?
>> 
>> -
>> Denis
>> 
>> 
>> On Wed, Jun 24, 2020 at 6:10 AM Gandhi, Karthik > <mailto:karthik.gan...@lazard.com>> wrote:
>> Hi - AWS Apache images are limited to 2 regions (US East 1 and US West 1). 
>> I have a need to Install and configure ignite in US East 2 AWS region. 
>> Appreciate if can copy to this region
>> 
>> -Karthik
> 

Re: Amazon AMI not available in a specific region

[Petr Ivanov]

AMI is not being update with release — it uses Docker inside that receive 
VERSION as parameters and pulls corresponding image from Docker Hub.

Concerning image itself, I will try to search which account owns it.


> On 24 Jun 2020, at 18:31, Denis Magda  wrote:
> 
> Ignite dev community,
> 
> Could you remind me if we still updating the AWS images for our releases? If 
> yes, how about expanding a list of supported regions?
> 
> -
> Denis
> 
> 
> On Wed, Jun 24, 2020 at 6:10 AM Gandhi, Karthik  > wrote:
> Hi - AWS Apache images are limited to 2 regions (US East 1 and US West 1). I 
> have a need to Install and configure ignite in US East 2 AWS region. 
> Appreciate if can copy to this region
> 
> -Karthik

Re: apache-ignite_2.8.0-1_all.deb package has older version of openjdk as dependency

[Petr Ivanov]

I guess it can be targeted to 2.8.1 if there any scope space left.


> On 6 May 2020, at 07:27, rakshita04  wrote:
> 
> Hi Team,
> 
> We are using apache-ignite for our C++ application based on debian
> 10(buster). We tried using apache-ignite_2.8.0-1_all.deb package but it
> depends on openjdk-8 which is older version and not available for debian 10
> buster. I have below questions-
> 1. Why older version of openjdk is used in deb package?
> 2. Is there any possibility of new released version of deb package with
> source apache-ignite_2.8.0 with newer openjdk version?
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Spelling and grammar check of subtitles for Ignite videos

[Petr Ivanov]

I would suggest creating separate Apache Ignite Youtube channel with creds 
access from PMCs and upload videos there.

Dmitriy, what do you think?


> On 3 Apr 2020, at 13:58, Maksim Stepachev  wrote:
> 
> Hi, everyone!
> 
> I'm going to translate Russian perfect videos about Apache Ignite in English 
> and dubbing them after that. They will be loaded to my youtube channel. I 
> need to help with grammar checking.
> 
>  If somebody wants to take part, please let me know.
> 
> 

Re: No ignitevisorcmd.sh in Ignite 2.8

[Petr Ivanov]

ignitevisorcmd was moved to docs by design, due to lack of time to configure 
package to install it correctly into system as ignite.sh is being installed 
(PATH, alternatives, etc.)


> On 20 Mar 2020, at 23:55, Stephen Darlington 
>  wrote:
> 
> Ah, apparently it doesn’t work when installed from a package. It’s in the doc 
> directory somewhere. See here for a discussion from when 2.7.5 was current: 
> http://apache-ignite-users.70518.x6.nabble.com/2-7-5-IGNITE-HOME-bin-ignitevisorcmd-sh-is-absent-td28629.html
>  
> 
> 
> Regards,
> Stephen
> 
>> On 20 Mar 2020, at 20:46, João Gonçalves > > wrote:
>> 
>> Thanks for the quick reply
>> 
>> I downloaded the rpm package 
>> https://ignite.apache.org/download.cgi#rpm-package 
>> 
>> 
>> Which one should I use?
>> 
>> 
>> Stephen Darlington > > escreveu no dia sexta, 20/03/2020 
>> à(s) 20:30:
>> Where did you download it from? Did you download the binary or source 
>> version? It’s there in my download:
>> 
>> ~ stephen.darlington$ cd $IGNITE_HOME
>> -ignite-2.8.0-bin stephen.darlington$ ls bin/*sh
>> bin/control.sh   bin/igniterouter.sh bin/sqlline.sh
>> bin/ignite.shbin/ignitevisorcmd.sh
>> apache-ignite-2.8.0-bin stephen.darlington$ 
>> 
>> Regards,
>> Stephen
>> 
>>> On 20 Mar 2020, at 19:19, joaogoncalves >> > wrote:
>>> 
>>> Hi
>>> Recently started working with Ignite on version 2.8.0
>>> 
>>> Can't find ignitevisorcmd.sh, was it removed? According to 
>>> https://apacheignite-tools.readme.io/docs/command-line-interface 
>>> 
>>> >> >   it
>>> should be under IGNITE_HOME/bin
>>> 
>>> I found IGNITE_HOME/bin/include/visorcmd/ignite-visor-console-2.8.0.jar and
>>> tried to run it but got: 
>>> "no main manifest attribute, in ignite-visor-console-2.8.0.jar"
>>> 
>>> Clearly it must run somehow but I can't find any documentation on how to do
>>> it.
>>> 
>>> 
>>> 
>>> --
>>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
>>> 
>> 
>> 
> 
> 

Re: Any idea on the release date of 2.8.0

[Petr Ivanov]

The vote is in progress, if RC1 will be approved as release, the binaries and 
docs will be available shortly after.


> On 2 Mar 2020, at 16:53, scriptnull  wrote:
> 
> Hi,
> 
> Apache Ignite 2.8.0 release contains a feature that I am interested in
> using. Noticed that the rc1 is released in github 4 days back (
> https://github.com/apache/ignite/releases/tag/2.8.0-rc1 ).
> 
> Does anyone have idea of when the actual 2.8.0 release will be available
> from the official site for downloading and also in docker hub?
> 
> Thanks in advance!
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7.5

[Petr Ivanov]

Nope, it is based on 2.7.0 release with mostly fixes and JDK 11 support.


> On 13 May 2019, at 19:07, joseheitor  wrote:
> 
> Hi Dimitry,
> 
> Will version 2.7.5 be based on the current (2.8.0) nightly code-base?
> 
> Jose
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite 2.7.0 and Hadoop Accelerator

[Petr Ivanov]

Hi!

The Hadoop Accelerator binary (!) was dropped in 2.7.0 release.
However, code still exists and you can build it manually (until 3.0 i guess).


> On 29 Jan 2019, at 21:00, Sergio Hernández Martínez  
> wrote:
> 
> Hello Everybody,
> 
> After saw the download page, i have one question.
> 
> In the download page we have binaries for Apache Ignite 2.7.0 but i don't see 
> Hadoop Acelerator binaries for 2.7.0 version.
> 
> IGFS for Hadoop is deprecated?
> 
> Thank you very much!

Re: ignite git repo

[Petr Ivanov]

Repository is move to GitBox
Clone command: git clone http://gitbox.apache.org/repos/ignite.git



> On 17 Jan 2019, at 19:17, Scott Cote  wrote:
> 
> Hello Igniters:
>  
> I’m having trouble cloning the git repo.  Want to build from source and maybe 
> make an add on ….
>  
> Went to the link:  https://ignite.apache.org/download.cgi#git-repository 
>  to get the “git” 
> url/command
> Am issuing the command:   git clone 
> https://git-wip-us.apache.org/repos/asf/ignite 
> 
>  
> But am getting (gitting???):
>  
> $ git clone https://git-wip-us.apache.org/repos/asf/ignite 
> 
> Cloning into 'ignite'...
> fatal: repository 'https://git-wip-us.apache.org/repos/asf/ignite/ 
> ' not found
>  
> Investigating the url and I’m redirected to 
>  
> https://gitbox.apache.org/repos/asf?p=ignite.git 
> 
>  
> So how do I clone?  The instructions are off ….
>  
> Thanks in advance.
>  
> SCott

Re: JDK 11 support

[Petr Ivanov]

Currently, compilation is not supported, efforts are about providing runtime 
compatibility.
I hope full support (compilation + runtime) will be introduced in 2.8 (and not 
later than 3.0).

> On 9 Jan 2019, at 11:27, zaleslaw  wrote:
> 
> I haven't any troubles with running Ignite 2.6 with JDK 8 and Ignite 2.7 with
> JDK 8,9.
> But a few weeks ago it [Ignite 2.6/Ignite 2.7) doesn't compile with JDK 11
> (Oracle).
> 
> 
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: When will Apache Ignite support Java 11?

[Petr Ivanov]

Hi!


Full Java 9+ support is planned for 2.8 at least.
Currently it will work more or less on Java9. Java10/11 work is not guaranteed.

> On 22 Nov 2018, at 21:22, monstereo  wrote:
> 
> Is there any plan to support Java 11 for Apache Ignite?
> 
> If the next version of the Apache Ignite (2.7) will support Java 11, when it
> will be released?
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite running on JDK10?

[Petr Ivanov]

It’s an umbrella ticket, see tickets below. Once more or less stable support 
will be introduced, I will resolve this ticket.


> On 2 Oct 2018, at 18:55, Maxim.Pudov  wrote:
> 
> https://issues.apache.org/jira/browse/IGNITE-8441 is still open. However, fix
> version is 2.7, which is coming soon.
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: JDK 11 support

[Petr Ivanov]

For now seems that JDK 11 is not available yet (EAP is not an option).
I think the best hope of full JDK11 support is JDK8 maintenance drop date 
(around Jan 2019).


> On 10 Sep 2018, at 16:17, ipsxd  wrote:
> 
> For now seems that Ignite cannot start with JDK 11, I assume there is a plan
> to migrate to 11 and if can you specify what the timeline ?
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite Install As Service error

[Petr Ivanov]

That’s normal output of running service.



> On 11 Jul 2018, at 18:29, ApacheUser  wrote:
> 
> Hi ilya,
> 
> I am using Ignite 2.5, The message pasted from "systemctl status
> apache-ign...@default-config.xml "command. I did nt run any command.
> 
> full message:
> 
> ]# systemctl status apache-ign...@default-config.xml
> ● apache-ign...@default-config.xml.service - Apache Ignite In-Memory
> Computing Platform Service
>   Loaded: loaded (/etc/systemd/system/apache-ignite@.service; enabled;
> vendor preset: disabled)
>   Active: active (running) since Mon 2018-07-09 15:36:40 GMT; 2s ago
>  Process: 24867 ExecStart=/usr/share/apache-ignite/bin/service.sh start %i
> (code=exited, status=0/SUCCESS)
>  Process: 24862 ExecStartPre=/usr/bin/env bash
> /usr/share/apache-ignite/bin/service.sh set-firewall (code=exited,
> status=0/SUCCESS)
>  Process: 24858 ExecStartPre=/usr/bin/chown ignite:ignite
> /var/run/apache-ignite (code=exited, status=0/SUCCESS)
>  Process: 24856 ExecStartPre=/usr/bin/mkdir /var/run/apache-ignite
> (code=exited, status=1/FAILURE)
> Main PID: 24869 (ignite.sh)
>   CGroup:
> /system.slice/system-apache\x2dignite.slice/apache-ign...@default-config.xml.service
>   ├─24869 /bin/bash /usr/share/apache-ignite/bin/ignite.sh
> /etc/apache-ignite/default-config.xml
>   └─24958 /usr/bin/java -Xms1g -Xmx1g -server -XX:+AggressiveOpts
> -XX:MaxMetaspaceSize=256m -DIGNITE_QUIET=true
> -DIGNITE_SUCCESS_FILE=/usr/share/apache-ignite/work/ignite...
> 
> 
> 
> 
> Thanks
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite Install As Service error

[Petr Ivanov]

Please see current service implementation (available in packages): 
https://github.com/apache/ignite/blob/master/packaging/rpm/name.service



> On 11 Jul 2018, at 13:20, ilya.kasnacheev  wrote:
> 
> Hello!
> 
> What version of package are you using? Since 2.4 there should be a minus
> sign before mkdir, which will make it non-essential. Also, I don't
> understand why chown is ran before mkdir. Petr, can you chime in by chance?
> 
> Regards,
> 
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite RPM Package Installation error: Failed dependencies: java-1.8.0 is needed by apache-ignite-2.4.0-1.noarch

[Petr Ivanov]

Bhaskar,


That’s right. ${IGNITE_HOME} is right at /usr/share/apache-ignite


> On 15 Jun 2018, at 20:39, bhaskar  wrote:
> 
> Thanks
> 
> what will be the IGNITE_HOME in this case? "/usr/share/apache-ignite/"?
> I am integrating sparj with Ignite, so need to provide $IGNITE_HOME/libs in
> spark-env.sh.
> 
> Thanks
> Bhaskar
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite RPM Package Installation error: Failed dependencies: java-1.8.0 is needed by apache-ignite-2.4.0-1.noarch

[Petr Ivanov]

Correction, Running Ignite as a Stand-Alone Process 
<https://apacheignite.readme.io/docs/getting-started#section-run-ignite-as-a-stand-alone-process>
 documentation section.



> On 13 Jun 2018, at 19:35, Petr Ivanov  wrote:
> 
> Bhaskar,
> 
> 
> To be honest, RPM packages are designed for at least RHEL / CentOS 7 and 
> higher. I’ve never had a chance to test them on 6.9 or earlier.
> Thus, package design also requires systemd service manager (it should be 
> installed by dependency as well), and should be started as follows `systemctl 
> start apache-ign...@default-config.xml`.
> Note:
> systemctl — exactly this command should be used, not service;
> @default-config.xml — after [at] sign you should specify only the name of 
> configuration file in /etc/apache-ignite, not full path to configuration file.
> 
> Also, if problems with systemd will persist or in case of other corresponding 
> difficulties, see Running Ignite as a Service 
> <https://apacheignite.readme.io/docs/getting-started#section-run-ignite-as-a-service>
>  documentation section for alternative ways of running Apache Ignite 
> installed from packages.
> 
> 
> Hope it helps!
> 
> 
> 
>> On 13 Jun 2018, at 19:02, bhaskar > <mailto:bhaskar.thungathu...@gmail.com>> wrote:
>> 
>> Thanks,
>> installed jdk rpm and apache-ignite installation went through, but when I
>> start getting start: unrecognized service error, what is missing here?.I am
>> m using Red Hat Enterprise Linux Server release 6.9 (Santiago)
>> 
>> # service start apache-ignite@/etc/apache-ignite/default-config.xml
>> start: unrecognized service
>> # service start apache-ign...@default-config.xml 
>> <mailto:apache-ign...@default-config.xml>
>> start: unrecognized service
>> #
>> 
>> My use case:
>> want to build apache ignite and spark cluster for sql and spark ML. Spark
>> streaming  loads incremental data into Ignite Cluster. I am able to do this
>> with zero deployment . But now trying to make Ignite Standalone Cluster run
>> in service mode like spark standalone cluster.
>> 
>> Thanks
>> Bhaskar 
>> 
>> 
>> 
>> --
>> Sent from: http://apache-ignite-users.70518.x6.nabble.com/ 
>> <http://apache-ignite-users.70518.x6.nabble.com/>
> 

Re: Ignite RPM Package Installation error: Failed dependencies: java-1.8.0 is needed by apache-ignite-2.4.0-1.noarch

[Petr Ivanov]

Bhaskar,


To be honest, RPM packages are designed for at least RHEL / CentOS 7 and 
higher. I’ve never had a chance to test them on 6.9 or earlier.
Thus, package design also requires systemd service manager (it should be 
installed by dependency as well), and should be started as follows `systemctl 
start apache-ign...@default-config.xml`.
Note:
systemctl — exactly this command should be used, not service;
@default-config.xml — after [at] sign you should specify only the name of 
configuration file in /etc/apache-ignite, not full path to configuration file.

Also, if problems with systemd will persist or in case of other corresponding 
difficulties, see Running Ignite as a Service 

 documentation section for alternative ways of running Apache Ignite installed 
from packages.


Hope it helps!



> On 13 Jun 2018, at 19:02, bhaskar  wrote:
> 
> Thanks,
> installed jdk rpm and apache-ignite installation went through, but when I
> start getting start: unrecognized service error, what is missing here?.I am
> m using Red Hat Enterprise Linux Server release 6.9 (Santiago)
> 
> # service start apache-ignite@/etc/apache-ignite/default-config.xml
> start: unrecognized service
> # service start apache-ign...@default-config.xml
> start: unrecognized service
> #
> 
> My use case:
> want to build apache ignite and spark cluster for sql and spark ML. Spark
> streaming  loads incremental data into Ignite Cluster. I am able to do this
> with zero deployment . But now trying to make Ignite Standalone Cluster run
> in service mode like spark standalone cluster.
> 
> Thanks
> Bhaskar 
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Ignite RPM Package Installation error: Failed dependencies: java-1.8.0 is needed by apache-ignite-2.4.0-1.noarch

[Petr Ivanov]

The main requirement is to install package through yum or rpm that provides 
java-1.8, for example openjdk, or Oracle Java or any other package.
Manual installation will not work due to apache-ignite package’s unawareness of 
this.

Yet, as a last resort, you can manually install apache-ignite with 'rpm -ivh 
apache-ignite --nodeps’ command to overcome dependency requirements.
Use it at your own risk, though.



> On 13 Jun 2018, at 16:31, bhaskar  wrote:
> 
> I am m using Red Hat Enterprise Linux Server release 6.9 (Santiago).
> but the JDK 1.8 is already installed and set JAVA_HOME and PATH. do we need
> to instal *.rpm based JDK?
> Thanks
> Bhaskar
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Agent not able to connect

[Petr Ivanov]

Roman — can you advise?



> On 31 May 2018, at 13:32, Humphrey  wrote:
> 
> I've done the steps you noted but it seems to do the same as the other 2.4
> version.
> 
> web-console-standalone:
> 
> 09:55:33 0|index | All Ignite migrations finished successfully.
> 09:55:33 0|index | Running Ignite Modules migrations...
> 09:55:33 0|index | There are no Ignite Modules migrations to run.
> 09:55:33 0|index | Start listening on 127.0.0.1:3000
> 
> web-agent:
> 
> Agent configuration:
> User's security tokens: fjp3
> URI to Ignite node REST server: http://localhost:8080
> URI to Ignite Console server  : http://172.17.0.3:3000
> Path to agent property file   : default.properties
> Path to JDBC drivers folder   : -n
> Demo mode : enabled
> 
> [2018-05-31 10:26:57,704][INFO ][main][AgentLauncher] Connecting to:
> http://172.17.0.3:3000
> [2018-05-31 10:26:57,855][ERROR][EventThread][AgentLauncher] Failed to
> establish connection to server (connection refused).
> [2018-05-31 10:26:59,062][ERROR][EventThread][AgentLauncher] Failed to
> establish connection to server (connection refused).
> [2018-05-31 10:27:01,219][ERROR][EventThread][AgentLauncher] Failed to
> establish connection to server (connection refused).
> [2018-05-31 10:27:04,697][ERROR][EventThread][AgentLauncher] Failed to
> establish connection to server (connection refused).
> 
> The Pod running the web-console-standalone has IP 172.17.0.3.
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Agent not able to connect

[Petr Ivanov]

This image is delivered within the frames of Apache Ignite Nightly Builds only 
for now.
To pull the image from the link I’ve provided, download corresponding tar.gz 
archive, gunzip it and use ‘docker load < web-agent-*-docker-image.tar’ to add 
it to local registry.



> On 31 May 2018, at 11:57, Humphrey  wrote:
> 
> How do I do a pull from that repository? Currently my docker is only looking
> at dockerhub.
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite nightly release builds

[Petr Ivanov]

Hi, Igniters!


Some more news about Apache Ignite Nightly build:
 - added docker image in form of compressed image tar.gz archive;
 - added DEB and RPM packages.

All latest artifacts as always available here: [1]


Enjoy!


[1] 
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&guest=1




> On 16 Apr 2018, at 11:49, Petr Ivanov  wrote:
> 
> Hi, Igniters!
> 
> 
> I’m glad to inform that starting today Apache Ignite Nightly Builds provide 
> Nuget and Maven stagings at MyGet [1].
> 
> Instructions on connecting to these feeds are here:
>  — Nuget [2]
>  — Maven [3]
> 
> 
> Enjoy.
> 
> 
> [1] https://www.myget.org/gallery/apache-ignite-nightly 
> <https://www.myget.org/gallery/apache-ignite-nightly>
> [2] http://docs.myget.org/docs/walkthrough/getting-started-with-nuget 
> <http://docs.myget.org/docs/walkthrough/getting-started-with-nuget>
> [3] http://docs.myget.org/docs/walkthrough/getting-started-with-maven 
> <http://docs.myget.org/docs/walkthrough/getting-started-with-maven>
> 
>> On 24 Mar 2018, at 11:42, Dmitriy Setrakyan > <mailto:dsetrak...@apache.org>> wrote:
>> 
>> Thanks, Denis. It should be added to the download page, I updated the ticket.
>> 
>> On Sat, Mar 24, 2018 at 5:48 AM, Denis Magda > <mailto:dma...@apache.org>> wrote:
>> Created a JIRA ticket for that:
>> https://issues.apache.org/jira/browse/IGNITE-8040 
>> <https://issues.apache.org/jira/browse/IGNITE-8040>
>> 
>> --
>> Denis
>> 
>> On Fri, Mar 23, 2018 at 1:27 AM, Dmitriy Setrakyan > <mailto:dsetrak...@apache.org>>
>> wrote:
>> 
>> > Awesome! Finally instead of asking our users to build from the master, we
>> > can provide a link to the nightly build instead.
>> >
>> > Denis, can you please add these links to the website?
>> >
>> > D.
>> >
>> > On Thu, Mar 22, 2018 at 1:27 PM, Petr Ivanov > > <mailto:mr.wei...@gmail.com>> wrote:
>> >
>> >> It works, thanks!
>> >>
>> >>
>> >> Here is updated links for Artifacts and Changes respectively with silent
>> >> guest login (can be added to bookmarks):
>> >> * https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces 
>> >> <https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces>
>> >> sful&buildTypeId=Releases_NightlyRelease_RunApacheIgnite
>> >> NightlyRelease&tab=artifacts&guest=1
>> >> * https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces 
>> >> <https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces>
>> >> sful&buildTypeId=Releases_NightlyRelease_RunApacheIgnite
>> >> NightlyRelease&tab=buildChangesDiv&guest=1
>> >>
>> >>
>> >>
>> >> > On 22 Mar 2018, at 13:06, Vitaliy Osipov > >> > <mailto:vosi...@gridgain.com>> wrote:
>> >> >
>> >> > 
>> >>
>> >>
>> >
>> 
> 

Re: Docker deployment with EXTERNAL_LIBS environment variable

[Petr Ivanov]

Hi, Kseniya.


I guess that something wrong with wget in distribution (alpine-linux). I will 
need some testing to investigate further.



> On 17 Apr 2018, at 13:02, Ksenia Vazhdaeva  wrote:
> 
> Hello,
> 
> I am trying to deploy Apache Ignite 2.4.0 in docker using external libs as
> described at https://apacheignite.readme.io/docs/docker-deployment
> 
> /docker run -d --name ignite -v
> /storage/ignite/ignite-server-config.xml:/etc/ignite/ignite-server-config.xml
> \
>-e "CONFIG_URI=file:///etc/ignite/ignite-server-config.xml" -p
> 47500:47500 \
>-e
> "EXTERNAL_LIBS=http://central.maven.org/maven2/org/apache/ignite/ignite-schedule/1.0.0/ignite-schedule-1.0.0.jar";
> \
> apacheignite/ignite:2.4.0/
> 
> Docker container is started but in docker logs there is an error
> 
> /wget: unrecognized option: i
> BusyBox v1.27.2 (2017-12-12 10:41:50 GMT) multi-call binary.
> 
> Usage: wget [-c|--continue] [--spider] [-q|--quiet] [-O|--output-document
> FILE]
>   [--header 'header: value'] [-Y|--proxy on/off] [-P DIR]
>   [-S|--server-response] [-U|--user-agent AGENT] [-T SEC] URL.../
> 
> Thus the external lib is not loaded.
> Could you, please, help me to resolve the problem or provide me with another
> way to add external libraries to Ignite classpath?
> 
> Thanks in advance,
> Ksenia
> 
> 
> 
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: Apache Ignite nightly release builds

[Petr Ivanov]

Hi, Igniters!


I’m glad to inform that starting today Apache Ignite Nightly Builds provide 
Nuget and Maven stagings at MyGet [1].

Instructions on connecting to these feeds are here:
 — Nuget [2]
 — Maven [3]


Enjoy.


[1] https://www.myget.org/gallery/apache-ignite-nightly 
<https://www.myget.org/gallery/apache-ignite-nightly>
[2] http://docs.myget.org/docs/walkthrough/getting-started-with-nuget 
<http://docs.myget.org/docs/walkthrough/getting-started-with-nuget>
[3] http://docs.myget.org/docs/walkthrough/getting-started-with-maven 
<http://docs.myget.org/docs/walkthrough/getting-started-with-maven>

> On 24 Mar 2018, at 11:42, Dmitriy Setrakyan  wrote:
> 
> Thanks, Denis. It should be added to the download page, I updated the ticket.
> 
> On Sat, Mar 24, 2018 at 5:48 AM, Denis Magda  <mailto:dma...@apache.org>> wrote:
> Created a JIRA ticket for that:
> https://issues.apache.org/jira/browse/IGNITE-8040 
> <https://issues.apache.org/jira/browse/IGNITE-8040>
> 
> --
> Denis
> 
> On Fri, Mar 23, 2018 at 1:27 AM, Dmitriy Setrakyan  <mailto:dsetrak...@apache.org>>
> wrote:
> 
> > Awesome! Finally instead of asking our users to build from the master, we
> > can provide a link to the nightly build instead.
> >
> > Denis, can you please add these links to the website?
> >
> > D.
> >
> > On Thu, Mar 22, 2018 at 1:27 PM, Petr Ivanov  > <mailto:mr.wei...@gmail.com>> wrote:
> >
> >> It works, thanks!
> >>
> >>
> >> Here is updated links for Artifacts and Changes respectively with silent
> >> guest login (can be added to bookmarks):
> >> * https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces 
> >> <https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces>
> >> sful&buildTypeId=Releases_NightlyRelease_RunApacheIgnite
> >> NightlyRelease&tab=artifacts&guest=1
> >> * https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces 
> >> <https://ci.ignite.apache.org/viewLog.html?buildId=lastSucces>
> >> sful&buildTypeId=Releases_NightlyRelease_RunApacheIgnite
> >> NightlyRelease&tab=buildChangesDiv&guest=1
> >>
> >>
> >>
> >> > On 22 Mar 2018, at 13:06, Vitaliy Osipov  >> > <mailto:vosi...@gridgain.com>> wrote:
> >> >
> >> > 
> >>
> >>
> >
> 

Re: 2.4.0 with Tomcat 8.5 and Java 9

[Petr Ivanov]

Eric,

Glad it helped!
And no, I guess that won’t be unique only for your environment.

Thanks for sharing your successful run configuration — hope it helps other 
users adopt Ignite to theirs environment as mush as it possible for now.
Also, if possible, please, share with us the results of web session clustering 
testing as they finish — looking forward to good news! 



> On 3 Apr 2018, at 21:03, Eric Ham  wrote:
> 
> Petr,
> 
> Thanks for tip. This is looking very promising as I see Ignite starting in 
> the catalina.out file now. As a note, I added those directives to my 
> bin/setenv.sh script as JAVA_OPTS as opposed to JVM_OPTS as that didn't seem 
> to work. Also, I did have to add the cache-api-1.1.0.jar file to my 
> shared.loader path as I was getting
> 
> java.lang.ClassNotFoundException: javax.cache.configuration.Factory
> 
> I'm not sure if this is unique to my environment or would be required by 
> others using Tomcat with Ignite. Our team will now work through our internal 
> testing to confirm that we can get web session clustering working correctly 
> between multiple Tomcat instances.
> 
> Thanks,
> -Eric 
> 
> On Tue, Apr 3, 2018 at 12:23 AM, Petr Ivanov  <mailto:mr.wei...@gmail.com>> wrote:
> Hi, Eric.
> 
> 
> Try to add to Tomcat’s JVM_OPTS following directives, please:
> --add-exports java.base/jdk.internal.misc=ALL-UNNAMED
> --add-exports java.base/sun.nio.ch <http://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
> 
> 
> 
>> On 2 Apr 2018, at 21:38, Eric Ham > <mailto:ham.e...@gmail.com>> wrote:
>> 
>> Hello,
>> 
>> From the suggestion on my other thread to try a newer Tomcat, I decided to 
>> spin up Tomcat 8.5.29 with Oracle JDK 9.0.4. I'm attempting to use web 
>> session clustering based on the following pages [1] and [2] as I saw the 
>> 2.4.0 release notes say Java 9 is now supported. I copied the following jars 
>> over for Tomcat to load:
>> 
>> ignite-core-2.4.0.jar
>> ignite-log4j-2.4.0.jar
>> ignite-spring-2.4.0.jar
>> ignite-web-2.4.0.jar
>> 
>> However, when I startup Tomcat I get the following error messages (listed 
>> below) in the localhost.2018-04-02.log file. The following 2 lines:
>> 
>> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class 
>> is unavailable.
>> 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 @464a014c
>> 
>> seem related to [3] IGNITE-7352, which says that it should be fixed in 2.4.0 
>> to support Java 9.
>> 
>> Either I'm missing a step or the 7352 fix didn't make it over? Please let me 
>> know what additional information I can provide to help resolve this.
>> 
>> Regards,
>> -Eric
>> 
>> [1] 
>> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/startup/servlet/ServletStartup.html
>>  
>> <https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/startup/servlet/ServletStartup.html>
>> 
>> [2] https://apacheignite-mix.readme.io/docs/web-session-clustering 
>> <https://apacheignite-mix.readme.io/docs/web-session-clustering>
>> 
>> [3] https://issues.apache.org/jira/browse/IGNITE-7352 
>> <https://issues.apache.org/jira/browse/IGNITE-7352>
>> 
>> 02-Apr-2018 11:27:55.914 INFO [localhost-startStop-1] 
>> org.apache.catalina.core.ApplicationContext.log No Spring 
>> WebApplicationInitializer types detected on classpath
>> 02-Apr-2018 11:27:56.739 SEVERE [localhost-startStop-1] 
>> org.apache.catalina.core.ApplicationContext.log StandardWrapper.Throwable
>>  java.lang.ExceptionInInitializerError
>> at 
>> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:759)
>> at 
>> org.apache.ignite.startup.servlet.ServletStartup.init(ServletStartup.java:138)
>> at javax.servlet.GenericServlet.init(GenericServlet.java:158)
>> at 
>> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1144)
>> at 
>> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
>> at 
>> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:983)
>> at 
>> org.a

Re: 2.4.0 with Tomcat 8.5 and Java 9

[Petr Ivanov]

Hi, Eric.


Try to add to Tomcat’s JVM_OPTS following directives, please:
--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



> On 2 Apr 2018, at 21:38, Eric Ham  wrote:
> 
> Hello,
> 
> From the suggestion on my other thread to try a newer Tomcat, I decided to 
> spin up Tomcat 8.5.29 with Oracle JDK 9.0.4. I'm attempting to use web 
> session clustering based on the following pages [1] and [2] as I saw the 
> 2.4.0 release notes say Java 9 is now supported. I copied the following jars 
> over for Tomcat to load:
> 
> ignite-core-2.4.0.jar
> ignite-log4j-2.4.0.jar
> ignite-spring-2.4.0.jar
> ignite-web-2.4.0.jar
> 
> However, when I startup Tomcat I get the following error messages (listed 
> below) in the localhost.2018-04-02.log file. The following 2 lines:
> 
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class 
> is unavailable.
> 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 @464a014c
> 
> seem related to [3] IGNITE-7352, which says that it should be fixed in 2.4.0 
> to support Java 9.
> 
> Either I'm missing a step or the 7352 fix didn't make it over? Please let me 
> know what additional information I can provide to help resolve this.
> 
> Regards,
> -Eric
> 
> [1] 
> https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/startup/servlet/ServletStartup.html
>  
> 
> 
> [2] https://apacheignite-mix.readme.io/docs/web-session-clustering 
> 
> 
> [3] https://issues.apache.org/jira/browse/IGNITE-7352 
> 
> 
> 02-Apr-2018 11:27:55.914 INFO [localhost-startStop-1] 
> org.apache.catalina.core.ApplicationContext.log No Spring 
> WebApplicationInitializer types detected on classpath
> 02-Apr-2018 11:27:56.739 SEVERE [localhost-startStop-1] 
> org.apache.catalina.core.ApplicationContext.log StandardWrapper.Throwable
>  java.lang.ExceptionInInitializerError
> at 
> org.apache.ignite.internal.util.IgniteUtils.(IgniteUtils.java:759)
> at 
> org.apache.ignite.startup.servlet.ServletStartup.init(ServletStartup.java:138)
> at javax.servlet.GenericServlet.init(GenericServlet.java:158)
> at 
> org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1144)
> at 
> org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1091)
> at 
> org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:983)
> at 
> org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:4939)
> at 
> org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5249)
> at 
> org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
> at 
> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:754)
> at 
> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:730)
> at 
> org.apache.catalina.core.StandardHost.addChild(StandardHost.java:734)
> at 
> org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:986)
> at 
> org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1857)
> at 
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: java.lang.RuntimeException: jdk.internal.misc.JavaNioAccess class 
> is unavailable.
> at 
> org.apache.ignite.internal.util.GridUnsafe.javaNioAccessObject(GridUnsafe.java:1459)
> at 
> org.apache.ignite.internal.util.GridUnsafe.(GridUnsafe.java:118)
> ... 19 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 @464a014c
> at 
> java.base/jdk.internal.reflect.Reflection.newIllegalAccessException(Reflection.java:361)
> at 
> java.base/java.lang.reflect.AccessibleObject.checkAccess(AccessibleObject.java:589)
> at java.base/java.lan

Re: Apache Ignite nightly release builds

[Petr Ivanov]

It works, thanks!


Here is updated links for Artifacts and Changes respectively with silent guest 
login (can be added to bookmarks):
* 
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts&guest=1
* 
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=buildChangesDiv&guest=1



> On 22 Mar 2018, at 13:06, Vitaliy Osipov  wrote:
> 
> 

Re: Apache Ignite nightly release builds

[Petr Ivanov]

I’ve added corresponding role to guest access user.

Vitaly, can you open Ignite Apache TC for guest login if no security issues 
exists that prevent from opening it?


> On 22 Mar 2018, at 11:49, Alexey Kuznetsov  wrote:
> 
> +1 to get nightly builds WITHOUT login.
> 
> On Thu, Mar 22, 2018 at 3:38 PM, Dmitriy Setrakyan 
> wrote:
> 
>> Why do we need to ask people to login to get a nightly build? Anyway to
>> open it to public without a login?
>> 
>> 
> 
> -- 
> Alexey Kuznetsov

Re: Step by Step Guide?

[Petr Ivanov]

Hi, Tim!


At what step exactly are you experiencing problems?



> On 22 Mar 2018, at 00:59, Tim Heizer  wrote:
> 
> Is there a step by step guide on setting up an Ignite cluster in AWS. I found 
> the documentation here: https://apacheignite.readme.io/docs/aws-deployment 
>  but I am finding it 
> difficult to fill all the gaps that aren't discussed in the documentation. A 
> clear step by step for all steps and prerequisites would be extremely helpful 
> but I am having a hard time finding one. Thanks!

Re: Apache Ignite nightly release builds

[Petr Ivanov]

OK, I guess I can present renewed Apache Ignite Nightly Releases.

Link to artifacts of the latest successful build: 
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts
 
<https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=artifacts>
REST API link to the same (for programmatic access): 
https://ci.ignite.apache.org/app/rest/builds/buildType:(id:Releases_NightlyRelease_RunApacheIgniteNightlyRelease),status:SUCCESS/artifacts
 
<https://ci.ignite.apache.org/app/rest/builds/buildType:(id:Releases_NightlyRelease_RunApacheIgniteNightlyRelease),status:SUCCESS/artifacts>
Link to changes of the latest successful build: 
https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=buildChangesDiv
 
<https://ci.ignite.apache.org/viewLog.html?buildId=lastSuccessful&buildTypeId=Releases_NightlyRelease_RunApacheIgniteNightlyRelease&tab=buildChangesDiv>

Some disclaimers:
* currently TeamCity will be used as storage for artifacts;
* artifacts will be stored for 2 weeks;
* nightly release builds are for DEVELOPMENT or TEST purposes only — use at 
your own risk (especially on production environment);
* build configuration is still more or less experimental, final tuning will be 
introduced after some usage.

Enjoy!


As always — questions and feedback are more then welcome.



> On 20 Mar 2018, at 15:03, Petr Ivanov  wrote:
> 
> Not yet.
> Project is still under development, I will pass build to community after 
> settling corresponding permissions and receiving QA report.
> 
> Also — it is time to rise a matter about adding nightly build link to out 
> documentation (somewhere here [1]).
> Pavel, could you help?
> 
> 
> [1] https://ignite.apache.org/download.cgi
> 
> 
>> On 20 Mar 2018, at 13:58, Dmitry Pavlov  wrote:
>> 
>> Thank you, Petr,
>> 
>> could you share link to run config?
>> 
>> Sincerely,
>> Dmitriy Pavlov
>> 
>> вт, 20 мар. 2018 г. в 12:17, Petr Ivanov :
>> 
>>> Prepared prototype build, passed for some preliminary testing.
>>> Currently it will provide the following artifacts:
>>> * sources
>>> * fabric binary
>>> * hadoop binary
>>> * maven staging
>>> * nuget staging
>>> 
>>> Will keep community informed about progress.
>>> 
>>> 
>>> 
>>>> On 14 Mar 2018, at 13:13, vveider  wrote:
>>>> 
>>>> Prepared corresponding task [1], will start preparing build in the
>>> nearest
>>>> future.
>>>> 
>>>> 
>>>> [1] https://issues.apache.org/jira/browse/IGNITE-7945
>>>> 
>>>> 
>>>> 
>>>> --
>>>> Sent from: http://apache-ignite-developers.2346864.n4.nabble.com/
>>> 
>>> 
>