[jira] [Work logged] (CURATOR-575) TestingServer shut down can cause NullPointerException

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CURATOR-575?focusedWorklogId=450758&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-450758 ]

ASF GitHub Bot logged work on CURATOR-575:
------------------------------------------

                Author: ASF GitHub Bot
            Created on: 25/Jun/20 01:16
            Start Date: 25/Jun/20 01:16
    Worklog Time Spent: 10m 
      Work Description: Randgalt opened a new pull request #368:
URL: https://github.com/apache/curator/pull/368


   TestingServer shutdown can cause an NPE due to FileTxnSnapLog being closed in a different thread


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 450758)
    Remaining Estimate: 0h
            Time Spent: 10m

> TestingServer shut down can cause NullPointerException
> ------------------------------------------------------
>
>                 Key: CURATOR-575
>                 URL: https://issues.apache.org/jira/browse/CURATOR-575
>             Project: Apache Curator
>          Issue Type: Bug
>          Components: Tests
>    Affects Versions: 5.0.0
>            Reporter: Jordan Zimmerman
>            Assignee: Jordan Zimmerman
>            Priority: Minor
>             Fix For: 5.1.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> There is a race in TestingServer that is identified in ZOOKEEPER-3803. The {{FileTxnSnapLog}} is closed in a different thread than the {{ZooKeeperServer}} is shutdown in. It can cause a {{NullPointerException}}. This doesn't hurt any behavior but's an irritant and could potentially cause problems later. It should be fixed.



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