Franco Po created IGNITE-15343:
----------------------------------
Summary: NullPointerException occurs when restarting ignite client
application
Key: IGNITE-15343
URL: https://issues.apache.org/jira/browse/IGNITE-15343
Project: Ignite
Issue Type: Bug
Reporter: Franco Po
Attachments: failed_startup-ignite_info.1st.attempt.log,
failed_startup-ignite_info.2nd.attempt.log, successful_startup-ignite_info.log
I upgraded one of my API backend applications from Apache Ignite 2.6 to
GridGain Community Edition 8.8.5 successfully in live environment a couple of
months ago. The entire setup is 2 instances of this ignite client application
plus a cluster of 2 ignite server instances. A planned maintenance needed to
restart the ignite client application. However, it couldn't be started again
due to a sequence of below exceptions (see
failed_startup-ignite_info.1st.attempt.log,
failed_startup-ignite_info.2nd.attempt.log for full log):
1. java.io.IOException: Failed to get acknowledge for message:
TcpDiscoveryClientMetricsUpdateMessage [super=TcpDiscoveryAbstractMessage
[sndNodeId=null, id=fef7e5e5b71-b588bb65-6fe8-4aff-8f17-4a9e8733369b,
verifierNodeId=null, topVer=0, pendingIdx=0, failedNodes=null, isClient=true]]
2. java.net.SocketException: Socket is closed
3. java.lang.NullPointerException: null
4. org.apache.ignite.IgniteCheckedException: Node stopped
I could restart same ignite client applications running in hot standby
environment where the ignite server contains no active data (see
successful_startup-ignite_info.log).
If anyone can provide insight as to how I can resolve this, that would be
greatly appreciated.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
