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 87804 - org.netbeans.mdr.util.MountFailedException
Summary: org.netbeans.mdr.util.MountFailedException
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 5.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: issues@java
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-10-23 20:22 UTC by ttesti
Modified: 2008-02-25 16:18 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
message log (474.51 KB, text/plain)
2006-10-23 20:23 UTC, ttesti
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ttesti 2006-10-23 20:22:40 UTC
I had printed a .java file to microsoft office document image writer when this 
error came up. I shut down NetBeans and restarted this continues to come up. I 
am sending a log file
Comment 1 ttesti 2006-10-23 20:23:56 UTC
Created attachment 35479 [details]
message log
Comment 2 Peter Pis 2006-10-24 14:49:18 UTC
Reassigning to "xml" for evaluation.
Comment 3 Nam Nguyen 2007-01-19 23:25:15 UTC
The first part of the log has retriever CatalogModelException's which is caught
and logged, so just informational (because nature of the background processing
of code completion).

The second part of the log, has the MountFailedException described by the
summary line.  This is the exception that use see "came up".  The cause of the
exception is probably user error (unavailable network mount).  IMO the exception
probably should be (already) relayed to user in some visual otherway, and from
the background nature of hint functionality, the EjbHintsProvider or some code
up the stack should handle the error silently.

Reassign back to ejbcore for further evaluation.
Comment 4 Petr Jiricka 2007-02-13 15:45:34 UTC
This will be fixed by the migration to Retouche.
Comment 5 Tomasz Slota 2007-02-16 08:41:50 UTC
This situation should be handled in lower layer (JMIUtils.getResource() should probably return null), 
reassigning to java core.
Comment 6 Quality Engineering 2007-09-20 12:05:32 UTC
Reorganization of java component
Comment 7 Jan Becicka 2008-02-25 16:18:10 UTC
This issue is not valid in current builds any more. Java support was completely
redesigned in 6.0 time frame. Please use NetBeans 6.0 and later.