is the class that implements the WebStart launcher. Note that this should not be the name of the class you actually want to profile. ="/Applications/Utilities/Java/Java Web Start.app/Contents/MacOS" -Djnlpx.splashport=-1 -Djnlpx.heapsize=NULL,NULL -Djnlpx.jvm=/System/Library/Frameworks/amework/Versions/1.4.2/ Home/bin/java -Djnlpx.remove=true ="file:/Applications/Utilities/Java/Java Web Start.app/Contents/MacOS/javaws.policy" -DtrustProxy=true ="/Applications/Utilities/Java/Java Web Start.app/Contents/MacOS" ="/Users/ your_user_id/Library/Caches/Java Web Start"ĥ) Enter the name of the WebStart launcher application class in the “Main class or executable JAR” field: Just watch out for line-breaks - there shouldn’t be any. JProfiler only gives you a single line in which to enter all of this, so it will probably be easiest if you make any changes in your favorite text editor, then paste the results into the “VM arguments” fields. If you are using a version of the Java runtime other than 1.4.2, make sure that the jnlpx.jvm property points to the correct java executable. Note that you will, at least, need to change your_user_id to the name of the account that you are logged in as. Java Web Start.app/Contents/MacOS/javaws.policy" Djnlpx.jvm=/System/Library/Frameworks/amework/Versions/1.4.2/ To set these, something like the following should be entered in the “VM arguments” field: “Apple 1.4.2_05”.ģ) The concept of a working directory is typically not meaningful for WebStart applications, so you can leave this set to “”.Ĥ) The WebStart launcher application relies on a set of system properties that tell it about the local installation and specify other execution parameters. Here are the steps:ġ) Choose “New Session” from the “Session” menu, give the session a name, and choose “Local” for the “Session type”.Ģ) Choose the Java VM that your WebStart application should run under, e.g. WebStart is just another Java application, so we can tell JProfiler to launch WebStart as a local application, with the appropriate command line arguments and jars in the classpath to make it download and run the app we actually want to profile. Speculated rationale aside, a simple work-around is possible. The documentation suggests that this functionality is available on other platforms, so perhaps the omission is due to perceived uncertainties of Apple’s approach to enforcing a single (per-JDK version) installation of the Java runtime. (E.g., menus do not follow Mac conventions and buttons have mnemonics.) A more significant issue is that, at least as of version 4.2.1, there appears to be no way to configure a session for profiling a Web Start application. JProfiler works great under OSX, though purists could probably still find a number of - mostly minor - UI elements that are un-Mac-like. Once a system reaches a certain size, and particularly for systems that have to run for long periods of time, a tool like JProfiler can pay for itself in the space of a single squashed bug. EJ Technology’s JProfiler is an indispensable tool for tracking down memory leaks and performance bottlenecks.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |