- This topic has 12 replies, 7 voices, and was last updated 20 years, 1 month ago by
.
-
Posts
-
I have been playing with the Eclipse Profiler open source plugin to profile a J2EE app.
The profiler lives at
http://eclipsecolorer.sourceforge.net/index_profiler.html
As you can see it is very feature rich for an open source plugin.I got it working to profile OC4J 9.0.3 using the following extra command line options to start the server:
-XrunProfilerDLL:1 -Xbootclasspath/a:jakarta-regexp.jar;profiler_trace.jar;commons-lang.jar -D__PROFILER_PACKAGE_FILTER=__A__com.evermind.server.OC4JServer;__M__sun.;__M__com.sun.;__M__java.;__M__javax.;__M__org.apache.;__M__com.evermind.;__M__oracle.;__M__com.oracle. -D__PROFILER_AUTO_START=0 -D__PROFILER_TIMING_METHOD=0
So basically all it needs is a few more command line options than what MyEclipse is using, but it is really fiddly to set up.
What would be cool would be:
1. Integrate the Eclipse Profiler plugin with MyEclipse
2. Provide an option on the application server Launch preference page to launch in Profiled mode (as well as the current Debug and Run). This would automatically add the correct command line parameters when starting up the server inside eclipse, and switch to the Eclipse Profiler perspective.This would add a serious enterprise level feature set to MyEclipse for a reasonably small amount of work.
Cheers,
Jon Nermut
Sounds cool. I’m kicking your feedback up the chain. We’ll actually our management team read all user feedback.
@ivar wrote:
woo..
+5 !haha.. I was about to promote this plugin suggestion, but I think I’ve already used up all my ‘pluses’… It’s been a year since the profiler plugin was uggested, it would be nice to know how it’s faring on the priority list.
There is another thread on here suggesting using Hyades as the profiler, which would be a better option as it is under active development as is much more standardised.
Jon
Hydes is a much better option because, for instance, http://eclipsecolorer.sourceforge.net/index_profiler.html does not support IBM’s JDK. Thefore, WebSphere Application Server (all versions) won’t work with it. 🙁
p.s. from the readme.txt release notes:
“I know that it does NOT work with IBM JDK 1.3.1, i.e. you will have problems with this profiler and WSAD 5.0. Well, it already has profiler. ;-)”
We use MyEclipseIDE instead of WSAD!!
Vote here
Has anyone had noticed with Eclipse profiler that is might be a bit of a memory hog?? I’ve extended the memory in the command line of Eclipse and I’m still noticing on my JUnit tests that I’m getting an out of memory error. but if i run the same Junit test suite not in the profiler, I do not get that error. MyEclipse Version 3.8.1, Eclipse version 3
No, the Eclipse Profiler plug-in from this website. http://sourceforge.net/projects/eclipsecolorer
