[
https://issues.apache.org/jira/browse/IGNITE-3412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Denis Magda updated IGNITE-3412:
--------------------------------
Description:
In some cases calling close on Ignite client instance will lead to deadlock.
The deadlock happens because of the following
Socket writer is waiting for new messages.
{code}
"tcp-client-disco-sock-writer-#2%null%" #100 prio=6 os_prio=0
tid=0x000000005fad2800 nid=0x13bc in Object.wait() [0x0000000067d0e000]
java.lang.Thread.State: WAITING (on object monitor)
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Object.java:502)
at
org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1051)
- locked <0x00000000863da2f8> (a java.lang.Object)
at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
{code}
was:
In some cases calling close on Ignite client instance will lead to deadlock.
See attachment for client threads.
> Client instance hangs on close
> ------------------------------
>
> Key: IGNITE-3412
> URL: https://issues.apache.org/jira/browse/IGNITE-3412
> Project: Ignite
> Issue Type: Bug
> Reporter: Alexei Scherbakov
> Attachments: threadDump.txt
>
>
> In some cases calling close on Ignite client instance will lead to deadlock.
> The deadlock happens because of the following
> Socket writer is waiting for new messages.
> {code}
> "tcp-client-disco-sock-writer-#2%null%" #100 prio=6 os_prio=0
> tid=0x000000005fad2800 nid=0x13bc in Object.wait() [0x0000000067d0e000]
> java.lang.Thread.State: WAITING (on object monitor)
> at java.lang.Object.wait(Native Method)
> at java.lang.Object.wait(Object.java:502)
> at
> org.apache.ignite.spi.discovery.tcp.ClientImpl$SocketWriter.body(ClientImpl.java:1051)
> - locked <0x00000000863da2f8> (a java.lang.Object)
> at org.apache.ignite.spi.IgniteSpiThread.run(IgniteSpiThread.java:62)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
