This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 33684 - RMI Registry node selection problem
Summary: RMI Registry node selection problem
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: rmi (show other bugs)
Version: -S1S-
Hardware: PC All
: P4 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-16 12:42 UTC by Marek Fukala
Modified: 2009-12-21 07:09 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Fukala 2003-05-16 12:42:32 UTC
[Nevada RC3, #030512, jdk1.4.1_02, winXP]
1) set RMI Registry refresh time setting to a
short time (500 milliseconds or less)
2) start local registry
3) stop local registry
=> The local registry node indicates correctly,
that the registry is not running, but flashes in
the refresh interval. Its behaviour prevents you
to select the node - when you select it the node
is in a "moment" (refresh interval) deselected. So
it makes hard to  delete it for example.
Comment 1 Marek Fukala 2003-05-17 10:42:09 UTC
Downgraded - the problem appears only under relatively complicated
circumstances.
Comment 2 Marek Fukala 2003-05-17 10:57:50 UTC
The problem is little bit wider. 
It happens if a registry node is created for a registry and then the
registry is stopped. In this case the node is deselected whenever the
refresh time passes.
Comment 3 Marek Fukala 2003-05-17 10:59:34 UTC
If the user set the refresh time too short - then it is hard to for
example delete the node. 
A workaround is to set longer refresh time.
Comment 4 Quality Engineering 2009-12-21 07:09:52 UTC
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team