Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Profiling Problems in 4.4 Squiggly

Revision as of 20:26, 30 November 2007 by Unnamed Poltroon (Talk) (New page: In order to keep to the minimal install we are using the IAC binaries This is the minimal script used to start the application ---- set TPTP_AC_HOME=D:\IDEs\4403\eclipse\plugins\org.eclips...)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

In order to keep to the minimal install we are using the IAC binaries This is the minimal script used to start the application


set TPTP_AC_HOME=D:\IDEs\4403\eclipse\plugins\org.eclipse.tptp.platform.ac.win_ia32_4.4.1.v200709261752\agent_controller

set JAVA_PROFILER_HOME=D:\IDEs\4403\eclipse\plugins\org.eclipse.tptp.platform.jvmti.runtime_4.4.1.v200709261752\agent_files\win_ia32

set PATH=%PATH%;%JAVA_PROFILER_HOME%;%TPTP_AC_HOME%\bin

set JVM=C:\WINDOWS\system32/java.exe

set AGENT=-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf:execdetails=true

set PARMS=

set CLASSPATH=.

%JVM% %AGENT% %PARMS% -jar batik-squiggle.jar


The first problem is that came up


Could not start Agent Controller.

Empty serviceconfig.xml file

Make sure you have created a valid serviceconfig.xml file by running the SetConfig script.


The file appears to exist but is empty. Note that this Eclipse instance has been used in the past to profile using IAC as an embedded component.

When attempting to run setconfig this message is returned


ERROR: The Java Runtime in use does not contain a suitable JAXP feature

RESOLUTION: Use a JRE which supports the JAXP feature


This occurs because the JRE being used is a SUN 1.6 release.

Back to the top