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
Mobile: +49 / 176 / 24 77 09 22
E-Mail: [email protected]
Website: www.LukasLentner.de
IBAN: DE33 7019 0000 0001 1810 17
BIC: GENODEF1M01 (Münchner Bank)
