United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
JDK-4720528 : (spec) ActivationSystem.activeGroup spec should be relaxed

Details
Type:
Enhancement
Submit Date:
2002-07-25
Status:
Closed
Updated Date:
2003-08-20
Project Name:
JDK
Resolved Date:
2003-08-13
Component:
core-libs
OS:
generic
Sub-Component:
java.rmi
CPU:
generic
Priority:
P4
Resolution:
Fixed
Affected Versions:
1.4.0
Fixed Versions:
5.0 (tiger)

Related Reports

Sub Tasks

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
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
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
CONVERTED DATA

BugTraq+ Release Management Values

COMMIT TO FIX:
tiger

FIXED IN:
tiger

INTEGRATED IN:
tiger
tiger-b15

VERIFIED IN:
tiger


                                     
2004-06-14



Hardware and Software, Engineered to Work Together