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 48299 - Enable profiling apps running on JDK 1.5
Summary: Enable profiling apps running on JDK 1.5
Status: CLOSED FIXED
Alias: None
Product: profiler
Classification: Unclassified
Component: Base (show other bugs)
Version: 4.x
Hardware: PC Windows ME/2000
: P2 blocker with 1 vote (vote)
Assignee: mishadmitriev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-01 12:56 UTC by iformanek
Modified: 2007-02-12 22:02 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description iformanek 2004-09-01 12:56:38 UTC
Since the modified JVM is 1.4.2-based, it does 
not run code written using the new JDK 1.5 (5.0) 
language features.
Comment 1 mishadmitriev 2004-09-18 01:37:15 UTC
We are now working with Javasoft on incorporating the JFluid 
functionality into mainstream JDK - which will address this issue in 
a natural way. However, the exact JDK release in which it will happen 
is not yet determined.
Comment 2 mishadmitriev 2004-09-18 02:04:19 UTC
See the previous comment
Comment 3 iformanek 2005-01-13 14:08:00 UTC
Will be fixed in 1.0, reopened to track progress for 1.0
Comment 4 mishadmitriev 2005-02-16 00:01:48 UTC
Planned for M7, when hopefully a public release of Mustang (JDK 6.0) 
VM with support for JFluid will become available.
Comment 5 _ gtzabari 2005-02-16 20:01:13 UTC
If M7 is planned for when Mustang goes public I am rather
disappointed. Isn't Mustang due out in like a year?
Comment 6 mishadmitriev 2005-02-16 20:04:03 UTC
No, not at all. Mustang EA releases are being made available to the 
public every 2 weeks at this time. So there is a good chance that 
JFluid support in VM will first become available in a Mustang VM - 
though, again, it will be just an EA release of Mustang.
Comment 7 _ alexlamsl 2005-04-03 01:03:53 UTC
Well - the RFE is claimed to have been integrated into J2SE 5 Update 4.
I wonder when would that mean though - we are still on Update 2 you see.
Comment 8 mishadmitriev 2005-04-03 20:22:27 UTC
The release of JDK 5.0 update 4 is planned for the end of June 2005 (fingers
crossed).
Comment 9 mishadmitriev 2005-04-08 01:31:57 UTC
The work on JDK 5 support in the tool is complete at this point. Further
incremental improvements may be done in future as new features, such as e.g.
improved attach on the fly mechanism, are added in JDK itself.

At this time the only publically available post-1.4 JDK with which JFluid is
going to work is JDK 6 (Mustang) Early Access, starting from Build 26. It can be
downloaded from http://java.sun.com (check the Early Access link on the page).
At this time Mustang is not that different from JDK 5, so you should not have
any problems using it for development-time profiling. The first official
production JDK that will support JFluid is going to be JDK 5.0_04, scheduled for
release in the end of June 2005.
Comment 10 ygor_sk 2005-05-03 12:43:45 UTC
I have one more question concerning JFluid support for JDK 1.5. The support for
JFluid is supposed to be ready in JDK 5.0_04 although currently I am able to
attach profiler to a 1.5.0_02 VM. Does this mean that the support is partly
implemented, but more issues have to solved? 

Microsoft Windows XP [Version 5.1.2600]
Profiler M6

I:\java-igor\MessagePlayer>"C:\Program Files\Java\jre1.5.0_02\bin\java.exe"
-agentpath:C:\Programs\nb-profiler-server\profiler-ea-libs\deployed\jdk15\windows\profilerinterface.dll=C:\Programs\nb-profiler-server\prof
iler-ea-libs,5140 -cp classes ygor.messageplayer.Main config.file.emitter.conf
Agent_OnLoad called...
Agent_OnLoad completed successfully.
JFluid: waiting for connection on port 5140
JFluid: local connection with the tool
...
Comment 11 mishadmitriev 2005-05-03 22:02:31 UTC
Essentially, yes - most of the API used by JFluid was in place before 5.0_04.
But, in 5.0_04 pretty significant internal changes to the implementation of this
API were done to fix some bugs and improve speed/scalability. The fact that
JFluid currently can connect with something older than 5.0_04 is a bug, it will
be fixed in the next milestone release.
Comment 12 ehucka 2006-10-09 12:09:02 UTC
Verification of old issues.
Comment 13 Alexander Kouznetsov 2007-02-12 22:02:46 UTC
Closing old issues.