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 223089 - java.rmi.NoSuchObjectException: no such object in table
Summary: java.rmi.NoSuchObjectException: no such object in table
Status: RESOLVED WONTFIX
Alias: None
Product: javame
Classification: Unclassified
Component: ME SDK Integration (show other bugs)
Version: 7.3
Hardware: All All
: P3 normal (vote)
Assignee: alexander.burdukov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-12-01 00:39 UTC by jaska_tl
Modified: 2013-04-18 19:43 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 192903

Attachments
stacktrace (2.47 KB, text/plain)
2012-12-01 00:39 UTC, jaska_tl 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description jaska_tl 2012-12-01 00:39:16 UTC 
This issue was reported manually by jaska_tl.
It already has 1 duplicates 


Build: NetBeans IDE 7.3 Beta (Build 201209272333)
VM: Java HotSpot(TM) Client VM, 23.3-b01, Java(TM) SE Runtime Environment, 1.7.0_07-b10
OS: Windows XP

User Comments:
jaska_tl: exception after installing ned plugins
This might be related to ME xxx and Java 7.xx Proxy bug




Stacktrace: 
java.rmi.NoSuchObjectException: no such object in table
   at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(StreamRemoteCall.java:273)
   at sun.rmi.transport.StreamRemoteCall.executeCall(StreamRemoteCall.java:251)
   at sun.rmi.server.UnicastRef.invoke(UnicastRef.java:160)
   at com.sun.jmx.remote.internal.PRef.invoke(PRef.java:0)
   at javax.management.remote.rmi.RMIConnectionImpl_Stub.invoke(RMIConnectionImpl_Stub.java:0)
   at javax.management.remote.rmi.RMIConnector$RemoteMBeanServerConnection.invoke(RMIConnector.java:1017)
Comment 1 jaska_tl 2012-12-01 00:39:18 UTC 
Created attachment 128684 [details]
stacktrace
Comment 2 David Strupl 2013-04-09 11:22:54 UTC 
Assigning to the new owner of javame modules.
Comment 3 Roman Svitanic 2013-04-18 15:52:29 UTC 
Probably ME SDK Integration issue.
Comment 4 alexander.burdukov 2013-04-18 19:37:41 UTC 
I cannot reproduce this issue, however I see the one potential scenario when it can happen:

On slow PC it is possible that ME SDK plugin starts communications with device manager when it is not completely started yet.

This issue is fixed in ME SDK 3.3 (GA, not Early Access version).

The status is changed to WONTFIX since this bug is in 3rd party product and not
in NB itself