You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Sanjaya <sa...@gmail.com> on 2020/09/11 07:05:50 UTC
Null Pointer exception error caught during grid runnable execution
Hi All,
we are using apache ignite 2.7.6 with pesistence enable inside Azure
Kubernetes cluster in production.
we have 2 pods having persistence enable, The pods have below resources
assgined to it
CPU : 3 core
heap: 3 GB
Peristence : SSD 15 GB
WAL : SSD 5 GB
We are reading / writting throigh JDBC thin clinet. The client are outside
of kubernetes, so they connect through kubernetes LoadBlancer IP.
The loading data part (from PostGres to Ignite) is quite OK, and it runs as
scheduled.
But we are facing below issue(Null pointer exception) when the clients are
trying to connect through jdbc thin client. Once the issue occurres, ignite
triggers a complete restart, so clients are not able to connect that time
and everything goes for toss.
We never faces this issue in lower enviornment. We are stuck with the issue,
request help on thios.
STACK TRACE
============
[05:18:39,803][WARNING][main][GridCacheDatabaseSharedManager] Ignite node
stopped in the middle of checkpoint. Will restore memory state and finish
checkpoint on node start.
[05:18:42,276][SEVERE][client-connector-#40][ClientListenerProcessor]
Runtime error caught during grid runnable execution: GridWorker
[name=message-received-notify, igniteInstanceName=null, finished=false,
heartbeatTs=1599801522271, hashCode=1044207064, interrupted=false,
runner=client-connector-#40]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.nextConnectionId(ClientListenerNioListener.java:306)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.prepareContext(ClientListenerNioListener.java:285)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onHandshake(ClientListenerNioListener.java:223)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:129)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:45)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
RE: Null Pointer exception error caught during grid runnable
execution
Posted by Alexandr Shapkin <le...@gmail.com>.
Hi,
It looks like a known issue when a server node is not fully initialized but
clients are trying to connect to it [1]
I’d suggest you try the latest version (2.8.1) and check if the error will be
gone.
[1] - https://issues.apache.org/jira/browse/IGNITE-11671
**From:**[Sanjaya](mailto:sahoo.skumar@gmail.com)
**Sent:** Friday, September 11, 2020 10:06 AM
**To:**[user@ignite.apache.org](mailto:user@ignite.apache.org)
**Subject:** Null Pointer exception error caught during grid runnable
execution
Hi All,
we are using apache ignite 2.7.6 with pesistence enable inside Azure
Kubernetes cluster in production.
we have 2 pods having persistence enable, The pods have below resources
assgined to it
CPU : 3 core
heap: 3 GB
Peristence : SSD 15 GB
WAL : SSD 5 GB
We are reading / writting throigh JDBC thin clinet. The client are outside
of kubernetes, so they connect through kubernetes LoadBlancer IP.
The loading data part (from PostGres to Ignite) is quite OK, and it runs as
scheduled.
But we are facing below issue(Null pointer exception) when the clients are
trying to connect through jdbc thin client. Once the issue occurres, ignite
triggers a complete restart, so clients are not able to connect that time
and everything goes for toss.
We never faces this issue in lower enviornment. We are stuck with the issue,
request help on thios.
STACK TRACE
============
[05:18:39,803][WARNING][main][GridCacheDatabaseSharedManager] Ignite node
stopped in the middle of checkpoint. Will restore memory state and finish
checkpoint on node start.
[05:18:42,276][SEVERE][client-connector-#40][ClientListenerProcessor]
Runtime error caught during grid runnable execution: GridWorker
[name=message-received-notify, igniteInstanceName=null, finished=false,
heartbeatTs=1599801522271, hashCode=1044207064, interrupted=false,
runner=client-connector-#40]
java.lang.NullPointerException
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.nextConnectionId(ClientListenerNioListener.java:306)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.prepareContext(ClientListenerNioListener.java:285)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onHandshake(ClientListenerNioListener.java:223)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:129)
at
org.apache.ignite.internal.processors.odbc.ClientListenerNioListener.onMessage(ClientListenerNioListener.java:45)
at
org.apache.ignite.internal.util.nio.GridNioFilterChain$TailFilter.onMessageReceived(GridNioFilterChain.java:279)
at
org.apache.ignite.internal.util.nio.GridNioFilterAdapter.proceedMessageReceived(GridNioFilterAdapter.java:109)
at
org.apache.ignite.internal.util.nio.GridNioAsyncNotifyFilter$3.body(GridNioAsyncNotifyFilter.java:97)
at
org.apache.ignite.internal.util.worker.GridWorker.run(GridWorker.java:120)
at
org.apache.ignite.internal.util.worker.GridWorkerPool$1.run(GridWorkerPool.java:70)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
\--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/