[
https://issues.apache.org/jira/browse/HADOOP-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Cutting updated HADOOP-1299:
---------------------------------
Resolution: Fixed
Fix Version/s: 0.13.0
Assignee: stack
Status: Resolved (was: Patch Available)
I just committed this. Thanks, Michael!
> Once RPC.stopClient has been called, RPC can not be used again
> --------------------------------------------------------------
>
> Key: HADOOP-1299
> URL: https://issues.apache.org/jira/browse/HADOOP-1299
> Project: Hadoop
> Issue Type: Bug
> Components: ipc
> Reporter: stack
> Assigned To: stack
> Priority: Minor
> Fix For: 0.13.0
>
> Attachments: hadoop1299.patch
>
>
> Calls to RPC.stopClient render RPC subsequently unusable -- at least until a
> reload of RPC class so static initializer has a chance to run again.
> I am trying to write unit tests for a little cluster built atop hadoop RPC
> class. Intent is to spin up the little cluster before each test is run.
> Post unit test, the cluster is torn down. Part of the takedown includes
> invocation of RPC.stopClient to clean up any outstanding connections, etc.
> I've found that when the second unit test runs, RPC Client is horked. The
> 'running' flag is false so Connections can't work and 'Connection Culler' is
> not running.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
