[ 
https://issues.apache.org/jira/browse/RATIS-1329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mario Georgiev updated RATIS-1329:
----------------------------------
    Description: 
Build the jar with 
{code:java}
./gradlew uber
 navigate to the build/libs/ and run the uber java -jar <jar-name-uber>
{code}

 Initially thought it only happens on Netty, but switched to GRPC and same 
thing.

Issue is both on Netty && GRPC, you might have to run the jar a few times to 
get the hang up. (attached jstack for both of the reproducible test cases)

Am i doing something incorrect in the code, or its just a bug.

  was:
Build the jar with 
```
./gradlew uber
navigate to the build/libs/ and run the uber jar.
```
Initially thought it only happens on Netty, but switched to GRPC and same thing.

Issue is both on Netty && GRPC, you might have to run the jar a few times to 
get the hang up. (attached jstack for both of the reproducible test cases)

Am i doing something incorrect in the code, or its just a bug.


> Doing RaftServer.close() hangs up the process
> ---------------------------------------------
>
>                 Key: RATIS-1329
>                 URL: https://issues.apache.org/jira/browse/RATIS-1329
>             Project: Ratis
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>            Reporter: Mario Georgiev
>            Priority: Major
>         Attachments: ratis-grpc-hangup-on-close-grpc-jstack.txt, 
> ratis-grpc-hangup-on-close.zip, ratis-netty-hangup-on-close-netty-jstack.txt, 
> ratis-netty-hangup-on-close.zip
>
>
> Build the jar with 
> {code:java}
> ./gradlew uber
>  navigate to the build/libs/ and run the uber java -jar <jar-name-uber>
> {code}
>  Initially thought it only happens on Netty, but switched to GRPC and same 
> thing.
> Issue is both on Netty && GRPC, you might have to run the jar a few times to 
> get the hang up. (attached jstack for both of the reproducible test cases)
> Am i doing something incorrect in the code, or its just a bug.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to