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.
Summary: | RMI server makes IDE die | ||
---|---|---|---|
Product: | platform | Reporter: | johnzoet <johnzoet> |
Component: | Execution | Assignee: | David Strupl <dstrupl> |
Status: | VERIFIED WONTFIX | ||
Severity: | blocker | Keywords: | JDK_SPECIFIC |
Priority: | P3 | ||
Version: | 3.x | ||
Hardware: | PC | ||
OS: | Linux | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: | Source files for RMI server Pi and RMI client OutputPi |
Description
johnzoet
2003-03-10 08:31:59 UTC
Created attachment 9321 [details]
Source files for RMI server Pi and RMI client OutputPi
I cannot reproduce this bug. I tried execute server and client part of your program. Did you use the RMI module in netbeans. The readme.txt file describes execution of PI aplication ,rmiregistry from commandline. Can you add steps of reproduction in ide? The JVM crashed or this is a deaddlock. I If the bug is deadclock, please attach thread dump (CTRL + '\' in console ). After executing RMI server Pi in the IDE the IDE shuts down almost instantly, in a fraction of a second. My operating system is SuSE 8.1 Everything else is working fine in the IDE, so it must be something specific to the RMI server. I could easily reproduce the problem today as follows: - start remiregistry - execute RMI server Pi(OK) - execute RMI client OutputPi (OK) - stop Pi - stop rmiregistry - execute Pi (IDE shuts down instantly) problem in JVM. Local Time = Tue Mar 11 15:33:27 2003 Elapsed Time = 2032 # # HotSpot Virtual Machine Error : 11 # Error ID : 4F530E43505002E6 # Please report this error at # http://java.sun.com/cgi-bin/bugreport.cgi # # Java VM: Java HotSpot(TM) Client VM (1.4.1-b21 mixed mode) # # An error report file has been saved as hs_err_pid4785.log. # Please refer to the file for further information. # See to #4830423 in bugparade on www.javasoft.com. The bug database cannot find bug number 4830423 The URL for the bug database is: http://developer.java.sun.com/developer/bugParade/ Problem does not happen anymore in JVM 1.4.1_02 and 1.4.2 |