JDK-4720528 : (spec) ActivationSystem.activeGroup spec should be relaxed
  • Type: Enhancement
  • Component: core-libs
  • Sub-Component: java.rmi
  • Affected Version: 1.4.0
  • Priority: P4
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2002-07-25
  • Updated: 2017-05-16
  • Resolved: 2003-08-13
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
Other
5.0 tigerFixed
Description
The spec for ActivationSystem.activeGroup seems to require that it throw ActivationException if a previous activeGroup call has been received for the same group. If the activeGroup call appears to succeed from rmid's perspective, but fail (reply is lost) from the group's perspective, the spec prevents the group from making another activeGroup call with the same arguments. This seems to work against reliability. It seems like it should be acceptable to call activeGroup more than once as long as the instantiator and incarnation are the same.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: tiger FIXED IN: tiger INTEGRATED IN: tiger tiger-b15 VERIFIED IN: tiger
2004-06-14

PUBLIC COMMENTS The spec for ActivationSystem.activeGroup seems to require that it throw ActivationException if a previous activeGroup call has been received for the same group. If the activeGroup call appears to succeed from rmid's perspective, but fail (reply is lost) from the group's perspective, the spec prevents the group from making another activeGroup call with the same arguments. This seems to work against reliability. It seems like it should be acceptable to call activeGroup more than once as long as the instantiator and incarnation are the same.
2004-06-10

EVALUATION Agreed. It is quite reasonable for the ActivationSystem.activeGroup call to be idempontent (that is simply succeed and return the ActivationMonitor if the group incarnation and the group instantiator are "the same"). The spec should be loosened to allow this behavior and the implementation should be updated (in Tiger). A side-effect of this change would allow callers (who have permission to make local calls) to obtain the activation monitor for a group if they know the current instantiator and incarnation. This doesn't seem to pose any problem though. ###@###.### 2002-07-25
2002-07-25