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 147095 - java.io.IOException: Problem with a required JFluid installation directory or file C:/Programs/NetBeans 6.1/profiler3/lib/deployed/jdk16/windows/profilerinterface.dll Original message: File does not e
Summary: java.io.IOException: Problem with a required JFluid installation directory or...
Status: CLOSED INVALID
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 6.x
Hardware: All Windows Vista
: P3 blocker (vote)
Assignee: issues@profiler
URL: http://statistics.netbeans.org/except...
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-12 14:30 UTC by Marian Mirilovic
Modified: 2009-12-03 03:25 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter: 89752

Attachments
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 Marian Mirilovic 2008-09-12 14:30:38 UTC 
Build: NetBeans IDE 6.1 (Build 200805300101)
VM: Java HotSpot(TM) Client VM, 10.0-b23, Java(TM) SE Runtime Environment, 1.6.0_07-b06
OS: Windows Vista, 6.0, x86
User comments: Launched Netbeans normally.
STACKTRACE: (first 10 lines)
java.io.IOException: Problem with a required JFluid installation directory or file C:/Programs/NetBeans
6.1/profiler3/lib/deployed/jdk16/windows/profilerinterface.dll
Original message: File does not exist.
        at org.netbeans.lib.profiler.ProfilerEngineSettings.initialize(ProfilerEngineSettings.java:468)
        at org.netbeans.modules.profiler.NetBeansProfiler.<init>(NetBeansProfiler.java:542)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:0)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
        at java.lang.reflect.Constructor.newInstance(Constructor.java:513)
        at java.lang.Class.newInstance0(Class.java:355)
        at java.lang.Class.newInstance(Class.java:308)
        at sun.misc.Service$LazyIterator.next(Service.java:271)
        at org.netbeans.lib.profiler.common.Profiler.getDefault(Profiler.java:123)
Comment 1 Jiri Sedlacek 2008-09-12 14:44:08 UTC 
Cannot reproduce. This looks like a broken installation. The user should check if the C:/Programs/NetBeans
6.1/profiler3/lib/deployed/jdk16/windows/profilerinterface.dll file exists, check its size and eventually reinstall the
IDE to check if it helps. If not, we need at least the IDE logfile. Based just on the stacktrace we won't be able to do
anything with this issue.
Comment 2 akamiya 2009-02-10 19:34:06 UTC 
I am seeing the same problem. The file does exist (32KB) but contains no version info. What should be the correct size?
And which logs would help?
Comment 3 akamiya 2009-02-10 19:39:55 UTC 
Oops, I was looking at the 6.1 installation I had. I was having the same problem with my 6.5 installation, and when I
looked into the:

C:\Program Files\NetBeans 6.5\profiler3\lib\deployed\jdk16\windows

the DLL and MAP file that were in the 6.1 installation did not exist. (They do exist in the jdk15 tree.) I copied over
the DLL and MAP file from the 6.1 installation and the problem disappeared.

I am running NetBeans 6.5 on Windows XP Pro.
Comment 4 Jiri Sedlacek 2009-02-10 19:49:57 UTC 
akamiya could you please describe the steps leading to the problem?

 - Which distribution of the IDE have you downloaded and installed (zip/installer, Java SE, Java EE, All...)?
 - Have you updated your IDE using the Tools | Plugins before the problem appeared?
 - Did the IDE worked fine some time or the exception is always thrown since the installation?

By IDE logfile I mean what you get by invoking View | IDE Log, on filesystem it's <netbeans_userdir\var\log\messages.log>.
Comment 5 Tomas Hurka 2009-02-10 20:09:30 UTC 
Probably duplicate of issue #157860
Comment 6 matusdekanek 2009-09-18 11:51:16 UTC 
missing additional information for a few months -> resolving invalid. Also, probably is a duplicate of another issue.
Comment 7 Marian Mirilovic 2009-12-03 03:25:15 UTC 
v/c