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

Difference between revisions of "Profiling Problems in 4.4 Squiggly"

Line 1: Line 1:
 
 
In order to keep to the minimal install we are using the IAC binaries
 
In order to keep to the minimal install we are using the IAC binaries
 
This is the minimal script used to start the application
 
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 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 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 PATH=%PATH%;%JAVA_PROFILER_HOME%;%TPTP_AC_HOME%\bin'''
  
set JVM=C:\WINDOWS\system32/java.exe
+
'''set JVM=C:\WINDOWS\system32/java.exe'''
  
set AGENT=-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf:execdetails=true
+
'''set AGENT=-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf:execdetails=true'''
  
set PARMS=
+
'''set PARMS='''
  
set CLASSPATH=.
+
'''set CLASSPATH=.'''
  
%JVM% %AGENT% %PARMS% -jar batik-squiggle.jar'''
+
'''%JVM% %AGENT% %PARMS% -jar batik-squiggle.jar'''
 
----
 
----
 
The first problem is that came up
 
The first problem is that came up
 
----
 
----
'''Could not start Agent Controller.
+
'''Could not start Agent Controller.'''
  
Empty serviceconfig.xml file
+
'''Empty serviceconfig.xml file'''
  
Make sure you have created a valid serviceconfig.xml file by running the SetConfig script.'''
+
'''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.
 
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.
Line 31: Line 30:
 
When attempting to run setconfig this message is returned
 
When attempting to run setconfig this message is returned
 
----
 
----
'''ERROR: The Java Runtime in use does not contain a suitable JAXP feature
+
'''ERROR: The Java Runtime in use does not contain a suitable JAXP feature'''
  
RESOLUTION: Use a JRE which supports the JAXP feature'''
+
'''RESOLUTION: Use a JRE which supports the JAXP feature'''
 
----
 
----
 
This occurs because the JRE being used is a SUN 1.6 release.
 
This occurs because the JRE being used is a SUN 1.6 release.

Revision as of 20:30, 30 November 2007

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