< :前の番号
^ :番号順リスト
> :次の番号
P :前の記事（スレッド移動）
N :次の記事（スレッド移動）
|<:前のスレッド
>|:次のスレッド
^ :返事先
_:自分への返事
>:同じ返事先を持つ記事（前）
<:同じ返事先を持つ記事（後）
---:分割してスレッド表示、再表示
| :分割して（縦）スレッド表示、再表示
~ :スレッドのフレーム消去
.:インデックス
..:インデックスのインデックス
Bugs item #11060, was opened at 2007-05-23 00:06
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=11060&group_id=426
Category: Standard Library
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Riley Lynch (rlynch)
Assigned to: Nobody (None)
Summary: DRb won't reliably stop_service
Initial Comment:
Because of the way that DRb caches a DRbServer instance in @primary_server (whether instantiated via DRb::start_service, or in some cases, DRbServer.new), you cannot be sure that your service will be entirely stopped: If the DRbServer is cached in @primary_server, it will continue to serve local requests, even after server.stop_service has been issued.
DRb::stop_service guarantees to clear @primary_server, but at the cost of stopping whatever service has been installed there. (Which depends on the order of instantiation, and which instantiation method was used.)
For now, to avoid surprises, I'm manually clearing this variable after instantiating a service:
server = DRb::DRbServer.new(uri, Front.new)
DRb.primary_server = nil
----------------------------------------------------------------------
You can respond by visiting:
http://rubyforge.org/tracker/?func=detail&atid=1698&aid=11060&group_id=426