Re: graalvm native images work on recent 2.16.0-SNAPSHOT builds with jdk21

[Scott Feldstein]

Hi Alex,
Glad to hear you've been able to get it working on 2.15 with jdk11/17.  I
had tried to get it working at different points in time without success.
In the past it had been discussed on the ignite user groups and I didn't
see anyone having much luck, plus there is a line item in the Ignite 3.x
wiki
<https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+3.0#ApacheIgnite3.0-GraalVMNativeImageSupport>
around
some graalvm native-image work.  In rereading the wiki, perhaps I
misinterpreted it?

Either way, I was discussing this with a coworker and he pointed out that
he had gotten it to work with jdk17 using my example.  It turned out that I
was using the 17-graal (oracle distro from sdkman <https://sdkman.io/>)
when I encountered these issues (see below). It actually does work for me
using the 17-graalce when I run it locally (even with Ignite 2.15).  After
facing these problems with 17-graal, it looked like we needed jdk21.

Here is the exception i was seeing with the jdk 17 oracle distro (17-graal
in sdkman):

Fatal error: unhandled exception in isolate 0x10780:
com.oracle.svm.core.jdk.UnsupportedFeatureError: Code that was
considered unreachable by closed-world analysis was reached.
at com.oracle.svm.core.util.VMError.unsupportedFeature(VMError.java:92)
at 
com.oracle.svm.core.snippets.SnippetRuntime.unsupportedFeature(SnippetRuntime.java:173)
at 
java.util.concurrent.locks.AbstractQueuedSynchronizer.release(AbstractQueuedSynchronizer.java:1007)
at java.util.concurrent.locks.ReentrantLock.unlock(ReentrantLock.java:494)
at 
com.oracle.svm.core.jdk.NativeLibrarySupport.addLibrary(NativeLibrarySupport.java:215)
at 
com.oracle.svm.core.jdk.NativeLibrarySupport.loadLibrary0(NativeLibrarySupport.java:160)
at 
com.oracle.svm.core.jdk.NativeLibrarySupport.loadLibraryRelative(NativeLibrarySupport.java:105)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:50)
at java.lang.Runtime.loadLibrary0(Runtime.java:818)
at java.lang.System.loadLibrary(System.java:1989)
at 
com.oracle.svm.core.jdk.JNIPlatformNativeLibrarySupport.loadJavaLibrary(JNIPlatformNativeLibrarySupport.java:44)
at 
com.oracle.svm.core.posix.PosixNativeLibrarySupport.loadJavaLibrary(PosixNativeLibraryFeature.java:117)
at 
com.oracle.svm.core.posix.PosixNativeLibrarySupport.initializeBuiltinLibraries(PosixNativeLibraryFeature.java:98)
at 
com.oracle.svm.core.graal.snippets.CEntryPointSnippets.initializeIsolate(CEntryPointSnippets.java:346)
at 
com.oracle.svm.core.JavaMainWrapper$EnterCreateIsolateWithCArgumentsPrologue.enter(JavaMainWrapper.java:387)




On Mon, Oct 9, 2023 at 3:45 AM Alex Plehanov 
wrote:

> Hello Scott,
>
> What kind of issues do you have with jdk17?
> I've tested graalvm native images with Ignite 2.15 some time ago
> (right after 2.15 was released) on jdk11 and jdk17 and it works on my
> examples.
>
> пн, 9 окт. 2023 г. в 11:24, Stephen Darlington :
> >
> > That's great news, thanks for sharing!
> >
> > On Sun, 8 Oct 2023 at 19:30, Scott Feldstein  wrote:
> >
> > > Hi All, I just wanted to let the community know in case folks weren't
> aware
> > > - it looks like Graalvm native images work on Ignite 2.16.0-SNAPSHOT
> builds
> > > with jdk21.  The fixes that appear responsible are IGNITE-19652
> > > <https://issues.apache.org/jira/browse/IGNITE-19652> and IGNITE-20532
> > > <https://issues.apache.org/jira/browse/IGNITE-20532>.  Unfortunately I
> > > can't get jdk17 to work properly as graalvm on that version appears to
> have
> > > limitations.  Graalvm native-image associated with jdk21 seems to
> alleviate
> > > those issues.
> > >
> > > If anyone is interested in my poc see
> > > https://github.com/scottmf/graalvm-ignite
> > >
> > > Scott
> > >
>

graalvm native images work on recent 2.16.0-SNAPSHOT builds with jdk21

[Scott Feldstein]

Hi All, I just wanted to let the community know in case folks weren't aware
- it looks like Graalvm native images work on Ignite 2.16.0-SNAPSHOT builds
with jdk21.  The fixes that appear responsible are IGNITE-19652
 and IGNITE-20532
.  Unfortunately I
can't get jdk17 to work properly as graalvm on that version appears to have
limitations.  Graalvm native-image associated with jdk21 seems to alleviate
those issues.

If anyone is interested in my poc see
https://github.com/scottmf/graalvm-ignite

Scott

[jira] [Created] (IGNITE-14098) ignite reentrant lock is not in user facing docs

[Scott Feldstein (Jira)]

Scott Feldstein created IGNITE-14098:


 Summary: ignite reentrant lock is not in user facing docs
 Key: IGNITE-14098
 URL: https://issues.apache.org/jira/browse/IGNITE-14098
 Project: Ignite
  Issue Type: Bug
  Components: documentation
Reporter: Scott Feldstein


Hi,

[Ignite Reentrant 
lock|https://ignite.apache.org/releases/latest/javadoc/org/apache/ignite/Ignite.html#reentrantLock-java.lang.String-boolean-boolean-boolean-]
 is not part of the user facing documentation in [https://ignite.apache.org/].  
It would be extremely useful if this were added and included when to use 
reentrant lock vs cache lock vs semaphore



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13406) support for apache camel 3.x

[Scott Feldstein (Jira)]

Scott Feldstein created IGNITE-13406:


 Summary: support for apache camel 3.x
 Key: IGNITE-13406
 URL: https://issues.apache.org/jira/browse/IGNITE-13406
 Project: Ignite
  Issue Type: Improvement
  Components: streaming
Reporter: Scott Feldstein


Currently the stream libs only support camel 2.x.  When camel 3.x is used 
errors come up.

Here is an example:
{code:java}
Caused by: java.lang.NoClassDefFoundError: 
org/apache/camel/util/CamelContextHelper
at 
org.apache.ignite.stream.camel.CamelStreamer.start(CamelStreamer.java:95)
at 
com.example.ignite.CamelKafkaIgniteApplicationTest$Config.camelStreamer(CamelKafkaIgniteApplicationTest.java:158)
at 
com.example.ignite.CamelKafkaIgniteApplicationTest$Config$$EnhancerBySpringCGLIB$$dd8ac36c.CGLIB$camelStreamer$2()
at 
com.example.ignite.CamelKafkaIgniteApplicationTest$Config$$EnhancerBySpringCGLIB$$dd8ac36c$$FastClassBySpringCGLIB$$5a773dea.invoke()
at 
org.springframework.cglib.proxy.MethodProxy.invokeSuper(MethodProxy.java:244)
at 
org.springframework.context.annotation.ConfigurationClassEnhancer$BeanMethodInterceptor.intercept(ConfigurationClassEnhancer.java:331)
at 
com.example.ignite.CamelKafkaIgniteApplicationTest$Config$$EnhancerBySpringCGLIB$$dd8ac36c.camelStreamer()
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at 
org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:154)
... 108 more
Caused by: java.lang.ClassNotFoundException: 
org.apache.camel.util.CamelContextHelper
at java.net.URLClassLoader.findClass(URLClassLoader.java:382)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
... 120 more
 {code}
The {{org/apache/camel/util/CamelContextHelper}} class has been moved in camel 
3.x per the [camel 3.x migration 
doc|https://camel.apache.org/manual/latest/camel-3-migration-guide.html]



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

[jira] [Created] (IGNITE-13097) Ignite OOMs when from local tests with many Caches

[Scott Feldstein (Jira)]

Scott Feldstein created IGNITE-13097:


 Summary: Ignite OOMs when from local tests with many Caches
 Key: IGNITE-13097
 URL: https://issues.apache.org/jira/browse/IGNITE-13097
 Project: Ignite
  Issue Type: Bug
Reporter: Scott Feldstein


This is the reproduction of a bug that reflects [this user 
post|[http://apache-ignite-users.70518.x6.nabble.com/Random2LruPageEvictionTracker-causing-hanging-in-our-integration-tests-td32239.html]].
  This impacts us in our integration-tests, not in any real environment. 

The reproduction is here -> [https://github.com/scottmf/ignite-oom]

 

My observation is that each {{IgniteCache}} object takes up almost 8MB.  I'm 
pretty sure this is taking up all the off-heap memory.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Re: Hibernate 5.3 merged!

[Scott Feldstein]

Hi Denis, Thanks for the response. spring is indeed Apache 2.0, see
https://github.com/spring-projects/spring-framework/blob/master/src/docs/dist/license.txt

Am I missing something?


On Fri, Dec 21, 2018 at 22:37 Denis Magda  wrote:

> Scott, Ilya,
>
> LGPL license is not compliant with Apache 2.0 and, thus, ASF project can't
> include binaries of LGPL libs to ASF releases:
> https://www.apache.org/legal/resolved.html#category-x
>
> Spring doesn't belong to ASF. It has its own rules and policies.
>
> --
> Denis
>
>
> On Thu, Dec 20, 2018 at 5:04 AM Ilya Kasnacheev  >
> wrote:
>
> > Hello!
> >
> > I don't think we can push it to public repositories in binary form. No
> > change in that regard. As for Spring, I honestly have no idea. Maybe
> > they're dual license?
> >
> > Regards,
> > --
> > Ilya Kasnacheev
> >
> >
> > чт, 20 дек. 2018 г. в 01:32, Scott Feldstein :
> >
> > > Hi Ilya, that’s great news!
> > >
> > > What’s the likelihood of pushing the artifacts to a public maven repo
> > along
> > > with the other ignite artifacts? Are we constrained by the LGPL2
> license?
> > > If so, I wonder how spring works around that with their jpa impl?
> > >
> > > Scott
> > > On Wed, Dec 19, 2018 at 09:03 Ilya Kasnacheev <
> ilya.kasnach...@gmail.com
> > >
> > > wrote:
> > >
> > > > Hello!
> > > >
> > > > I have just checked, and it looks like hibernate-5.3 module works
> > > correctly
> > > > with Hibernate 5.4.0.Final!
> > > >
> > > > It builds without errors and all tests pass. So maybe we can rebrand
> it
> > > as
> > > > hibernate-5.3+ for the duration.
> > > >
> > > > Regards,
> > > > --
> > > > Ilya Kasnacheev
> > > >
> > > >
> > > > ср, 19 дек. 2018 г. в 19:53, Павлухин Иван :
> > > >
> > > > > Good news!
> > > > >
> > > > > I also believe that a lot of users will be happy once it is
> released.
> > > > > Cheers!
> > > > >
> > > > > By the way, I noticed that the latest Hibernate version is 5.4. It
> is
> > > > > compatible with 5.3? Should it be somehow addressed by Ignite
> > > > > developers?
> > > > > ср, 19 дек. 2018 г. в 19:09, Ilya Kasnacheev <
> > > ilya.kasnach...@gmail.com
> > > > >:
> > > > > >
> > > > > > Hello!
> > > > > >
> > > > > > I am proud to announce that I have just merged Hibernate 5.3
> > module,
> > > > > > courtesy Scott Feldstein.
> > > > > >
> > > > > > There were also important fixes which should make TC greener than
> > > ever.
> > > > > >
> > > > > > Since this is a large patch there might be rough edges, please
> > notify
> > > > me
> > > > > if
> > > > > > anything went awry, I will try to follow it up.
> > > > > >
> > > > > > Regards,
> > > > > > --
> > > > > > Ilya Kasnacheev
> > > > >
> > > > >
> > > > >
> > > > > --
> > > > > Best regards,
> > > > > Ivan Pavlukhin
> > > > >
> > > >
> > >
> >
>

Re: Hibernate 5.3 merged!

[Scott Feldstein]

Hi Ilya, that’s great news!

What’s the likelihood of pushing the artifacts to a public maven repo along
with the other ignite artifacts? Are we constrained by the LGPL2 license?
If so, I wonder how spring works around that with their jpa impl?

Scott
On Wed, Dec 19, 2018 at 09:03 Ilya Kasnacheev 
wrote:

> Hello!
>
> I have just checked, and it looks like hibernate-5.3 module works correctly
> with Hibernate 5.4.0.Final!
>
> It builds without errors and all tests pass. So maybe we can rebrand it as
> hibernate-5.3+ for the duration.
>
> Regards,
> --
> Ilya Kasnacheev
>
>
> ср, 19 дек. 2018 г. в 19:53, Павлухин Иван :
>
> > Good news!
> >
> > I also believe that a lot of users will be happy once it is released.
> > Cheers!
> >
> > By the way, I noticed that the latest Hibernate version is 5.4. It is
> > compatible with 5.3? Should it be somehow addressed by Ignite
> > developers?
> > ср, 19 дек. 2018 г. в 19:09, Ilya Kasnacheev  >:
> > >
> > > Hello!
> > >
> > > I am proud to announce that I have just merged Hibernate 5.3 module,
> > > courtesy Scott Feldstein.
> > >
> > > There were also important fixes which should make TC greener than ever.
> > >
> > > Since this is a large patch there might be rough edges, please notify
> me
> > if
> > > anything went awry, I will try to follow it up.
> > >
> > > Regards,
> > > --
> > > Ilya Kasnacheev
> >
> >
> >
> > --
> > Best regards,
> > Ivan Pavlukhin
> >
>

Re: hello

[Scott Feldstein]

Hi Denis,
Thanks!

This is what I'm trying to contribute
  jira: https://issues.apache.org/jira/browse/IGNITE-9893
  pullRequest: https://github.com/apache/ignite/pull/5008

WRT the blog, we actually discussed this at the in-memory conference.  At
the beginning of the year we'll start to make our usage more public
internally and externally if all goes well :)

Scott

On Wed, Oct 24, 2018 at 7:44 PM Denis Magda  wrote:

> Hey Scott,
>
> Great to know, welcome to the community!
>
> What exactly do you like to contribute back? Please start a separate
> discussion with the most meaningful topic.
>
> Also, if you can post a blog post about your architecture at VMWare will be
> glad to mention it on the "Ignite in Production" page:
> https://ignite.apache.org/provenusecases.html
>
> --
> Denis
>
> On Wed, Oct 24, 2018 at 7:39 PM Scott Feldstein 
> wrote:
>
> > Hi Everyone,
> > I'm following the instructions from
> > https://ignite.apache.org/community/contribute.html. I'd like to
> > contribute
> > some of the code I've been working on in order to continue evolving
> Ignite.
> >
> > I've been evangelizing Ignite at VMware and am in the process of locking
> > down our next-gen service architecture.  The plan is to use Ignite as a
> > multi-faceted caching server on steriods!
> >
> > Please feel free to reach out to me and say hi as well :)
> >
> > Scott
> >
>

hello

[Scott Feldstein]

Hi Everyone,
I'm following the instructions from
https://ignite.apache.org/community/contribute.html. I'd like to contribute
some of the code I've been working on in order to continue evolving Ignite.

I've been evangelizing Ignite at VMware and am in the process of locking
down our next-gen service architecture.  The plan is to use Ignite as a
multi-faceted caching server on steriods!

Please feel free to reach out to me and say hi as well :)

Scott

[jira] [Created] (IGNITE-9893) add hibernate-5.2 module

[Scott Feldstein (JIRA)]

Scott Feldstein created IGNITE-9893:
---

 Summary: add hibernate-5.2 module
 Key: IGNITE-9893
 URL: https://issues.apache.org/jira/browse/IGNITE-9893
 Project: Ignite
  Issue Type: New Feature
  Components: hibernate
Reporter: Scott Feldstein


hi,

I have ported hibernate-5.2 to ignite 2.7.0-SNAPSHOT HEAD.

commit: 
[https://github.com/scottmf/ignite/commit/4f2caafb8c433e3f840d14f91c2d83da1052afd9]

All tests pass except CacheHibernateBlobStoreSelfTest.testSimpleMultithreading 
which is carryover from the hibernate-5.1 implementation. There is a bug 
already associated with the failure:

https://issues.apache.org/jira/browse/IGNITE-1757



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (IGNITE-8197) ignite won't start with spring-boot 1.5.11 - h2 property NESTED_JOINS doesn't exist

[Scott Feldstein (JIRA)]

Scott Feldstein created IGNITE-8197:
---

 Summary: ignite won't start with spring-boot 1.5.11 - h2 property 
NESTED_JOINS doesn't exist
 Key: IGNITE-8197
 URL: https://issues.apache.org/jira/browse/IGNITE-8197
 Project: Ignite
  Issue Type: Bug
Reporter: Scott Feldstein


I just upgraded to spring-boot 1.5.11 and am seeing the error below. I think 
this is an issue with the version of h2 associated with spring boot 1.5.11. In 
1.5.10 the h2 version was 1.4.196 and with 1.5.11 it is 1.4.197. The 
NESTED_JOINS property comes from 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing, i assume it 
was deprecated but not sure. When I lock in my h2 version to 1.4.196 by 
overriding the spring-dependencies parent everything works fine
{code:java}
Caused by: org.h2.jdbc.JdbcSQLException: Unsupported connection setting 
"NESTED_JOINS" [90113-197]
at org.h2.message.DbException.getJdbcSQLException(DbException.java:357) 
~[h2-1.4.197.jar:1.4.197]
at org.h2.message.DbException.get(DbException.java:179) 
~[h2-1.4.197.jar:1.4.197]
at org.h2.message.DbException.get(DbException.java:155) 
~[h2-1.4.197.jar:1.4.197]
at org.h2.engine.ConnectionInfo.readSettingsFromURL(ConnectionInfo.java:268) 
~[h2-1.4.197.jar:1.4.197]
at org.h2.engine.ConnectionInfo.(ConnectionInfo.java:76) 
~[h2-1.4.197.jar:1.4.197]
at org.h2.jdbc.JdbcConnection.(JdbcConnection.java:103) 
~[h2-1.4.197.jar:1.4.197]
at org.h2.Driver.connect(Driver.java:69) ~[h2-1.4.197.jar:1.4.197]
at java.sql.DriverManager.getConnection(DriverManager.java:664) ~[?:1.8.0_131]
at java.sql.DriverManager.getConnection(DriverManager.java:270) ~[?:1.8.0_131]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.initialValue(IgniteH2Indexing.java:317)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.initialValue(IgniteH2Indexing.java:288)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at java.lang.ThreadLocal.setInitialValue(ThreadLocal.java:180) ~[?:1.8.0_131]
at java.lang.ThreadLocal.get(ThreadLocal.java:170) ~[?:1.8.0_131]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.get(IgniteH2Indexing.java:290)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing$1.get(IgniteH2Indexing.java:288)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.connectionForThread(IgniteH2Indexing.java:514)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.executeStatement(IgniteH2Indexing.java:582)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.createSchema(IgniteH2Indexing.java:551)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.h2.IgniteH2Indexing.registerCache(IgniteH2Indexing.java:2667)
 ~[ignite-indexing-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.registerCache0(GridQueryProcessor.java:1594)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart0(GridQueryProcessor.java:800)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.query.GridQueryProcessor.onCacheStart(GridQueryProcessor.java:861)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCache(GridCacheProcessor.java:1158)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.prepareCacheStart(GridCacheProcessor.java:1900)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCacheProcessor.startCachesOnLocalJoin(GridCacheProcessor.java:1764)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.initCachesOnLocalJoin(GridDhtPartitionsExchangeFuture.java:744)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.distributed.dht.preloader.GridDhtPartitionsExchangeFuture.init(GridDhtPartitionsExchangeFuture.java:626)
 ~[ignite-core-2.4.0.jar:2.4.0]
at 
org.apache.ignite.internal.processors.cache.GridCachePartitionExchangeManager$ExchangeWorker.body(GridCachePartitionExchangeManager.java:2337)
 ~[ignite-core-2.4.0.jar:2.4.0]
at org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:110) 
~[ignite-core-2.4.0.jar:2.4.0]
at java.lang.Thread.run(Thread.java:748) ~[?:1.8.0_131]{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)