Hi, what is date of the fixed version?
Thankx Lukas ---- Lukas Lentner, B. Sc. St.-Cajetan-Straße 13 81669 München Deutschland Fon: +49 / 89 / 71 67 44 96 Mobile: +49 / 176 / 24 77 09 22 E-Mail: kont...@lukaslentner.de Website: www.LukasLentner.de IBAN: DE33 7019 0000 0001 1810 17 BIC: GENODEF1M01 (Münchner Bank) Von: Dmitry Pavlov [mailto:dpavlov....@gmail.com] Gesendet: Mittwoch, 24. Mai 2017 20:23 An: user@ignite.apache.org Betreff: Re: Ignite and Memory Info Denis, To my mind it could be fixed, there should be not so much code to change. Best Regards, Dmitriy Pavlov ср, 24 мая 2017 г. в 21:13, Denis Magda <dma...@apache.org<mailto:dma...@apache.org>>: Dmitriy, Can this be fixed in 2.1? It looks like a serious bug to me. — Denis On May 24, 2017, at 10:59 AM, Lukas Lentner <kont...@lukaslentner.de<mailto:kont...@lukaslentner.de>> wrote: Is there any possible workaround? It pretty much makes me unable to use ignite right now… It is a real dealbreaker ;-)) ---- Lukas Lentner, B. Sc. St.-Cajetan-Straße 13 81669 München Deutschland Fon: +49 / 89 / 71 67 44 96<tel:+49%2089%2071674496> Mobile: +49 / 176 / 24 77 09 22<tel:+49%20176%2024770922> E-Mail: kont...@lukaslentner.de<mailto:kont...@lukaslentner.de> Website: www.LukasLentner.de<http://www.lukaslentner.de/> IBAN: DE33 7019 0000 0001 1810 17 BIC: GENODEF1M01 (Münchner Bank) Von: Dmitry Pavlov [mailto:dpavlov....@gmail.com] Gesendet: Mittwoch, 24. Mai 2017 19:35 An: user@ignite.apache.org<mailto:user@ignite.apache.org> Betreff: Re: Ignite and Memory Info Hi Lukas, I have created improvement https://issues.apache.org/jira/browse/IGNITE-5288 to consider this suggestion in future versions. Best Regards, Dmitry Pavlov ср, 24 мая 2017 г. в 15:39, Lukas Lentner <kont...@lukaslentner.de<mailto:kont...@lukaslentner.de>>: Hi, When using Ignite 1.7 together with Excelsior JET Ahead-Of-Time Compiler we get this error on various occasions: java.lang.IllegalArgumentException: committed = 5274103808 should be < max = 5274095616 at java.lang.management.MemoryUsage.<init>(Unknown Source) at sun.management.MemoryImpl.<unknown>(Unknown Source) at sun.management.MemoryImpl.getHeapMemoryUsage(Unknown Source) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$6.getHeapMemoryCommitted(GridDiscoveryManager.java:778) at org.apache.ignite.internal.managers.discovery.GridDiscoveryManager$7.metrics(GridDiscoveryManager.java:878) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processHeartbeatMessage(ServerImpl.java:4651) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2325) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.processMessage(ServerImpl.java:2135) at org.apache.ignite.spi.discovery.tcp.ServerImpl$MessageWorkerAdapter.body(ServerImpl.java:6123) at org.apache.ignite.spi.discovery.tcp.ServerImpl$RingMessageWorker.body(ServerImpl.java:2222) at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62) For me it looks like, that the commited and the max memory numbers are not consistent and getHeapMemoryUsage() throws a IllegalArgumentEx about it. I found this error on various other software issue tracker as netbeans, … and my impression is, that it is common. So GridDiscoveryManager should think about the possibility to get such error and not kill the whole process because of it. What do you think? Do you have the same error sometimes? Bye Lukas ---- Lukas Lentner, B. Sc. St.-Cajetan-Straße 13 81669 München Deutschland Fon: +49 / 89 / 71 67 44 96<tel:+49%2089%2071674496> Mobile: +49 / 176 / 24 77 09 22<tel:+49%20176%2024770922> E-Mail: kont...@lukaslentner.de<mailto:kont...@lukaslentner.de> Website: www.LukasLentner.de<http://www.lukaslentner.de/> IBAN: DE33 7019 0000 0001 1810 17 BIC: GENODEF1M01 (Münchner Bank)
