05360: | Network Disconnect does not disconnect cleanly |
Category: Integration
Status: ClosedSeverity: MEDIUM
Reported against release: 0.8
Fixed in release: 0.9.2
PROBLEM:While all platforms are running Openwings, and one platform is
diconnected from the rest, the platform does not continue normal
Openwings behavior. (ie, cannot install components) ANALYSIS:This problem report was retested on the build for the official
Openwings 0.9.1 release and is no longer an issue. The move to Jini 1.2
in the 0.9 release took care of much of the problems associated with
losing a network connection. Improvements made to the installer
implementation for the 0.9.1 release probably took care of the rest of
the problem.
The basic issue is how callbacks are handled. Both Jini and the
installer allow users to register callbacks for notification of certain
events. Previously, callbacks were done sequentially, meaning that a
broken connection could result in some callbacks being blocked. More
recent versions of Jini and the installer perform callbacks in parallel
threads to avoid this problem. (Other Openwings services were designed
with multithreaded callbacks to begin with.) |
