| Profiling Axis/Xerces - Raised java.lang.ArrayIndexOutOfBoundsException: -1 [message #116937] |
Thu, 01 November 2007 14:22 |
Eclipse User |
|
|
|
OS: LINUX SUSE 10.1
ECLIPSE 3.3
TPTP: 4.4.0.2 (stable release)
JVM: jdk 1.5.0_12
Hi everybody,
I am trying to profile some web services invoked by a proper client via
Axis server.
The configuration of Axis was successful: Xerces, needed by Axis, was
carefully built using ant against JVM 1.5.0_12, to avoid any "error in
version number" in .class files; all the remaining jar files provided by
Axis are compliant to java 5.0, instead.
Everything works when I configure and launch Run Mode, whereas the
following exception is raised when I try to launch a profiling
session(for every profiling tool I choose):
java.lang.ArrayIndexOutOfBoundsException
-1
java.lang.ArrayIndexOutOfBoundsException: -1
at
org.eclipse.tptp.trace.ui.provisional.launcher.AbstractProce ssLauncher.getClasspathString(AbstractProcessLauncher.java:2 39)
at
org.eclipse.tptp.trace.ui.provisional.launcher.AbstractProce ssLauncher.preLaunch(AbstractProcessLauncher.java:106)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.launch(TIDelegateHelper.java:306)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TIJ avaLauncherDelegate.launch(TIJavaLauncherDelegate.java:37)
at
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti lity.delegateInit(LauncherUtility.java:1153)
at
org.eclipse.tptp.trace.ui.provisional.launcher.PrimaryLaunch Delegate.run(PrimaryLaunchDelegate.java:196)
at java.lang.Thread.run(Thread.java:619)
The only way to profile is launching the client from the command line:
java -cp .:$AXISCLASSPATH
'-agentlib:JPIBootLoader=JPIAgent:server=controlled;CGProf'
samples.stock.GetQuote -lhttp://localhost:8080/axis/servlet/AxisServlet
-uuser1 -wpass1 XXX
(java points to a jdk 1.5.0_12 executable)
and attaching to it from TPTP workbench. Here another strange behaviour
appears: although I configure "show graphical details", no UML2 diagram,
no Execution flow diagram and no call tree can be shown in the end;
method invocations can be explored only through "Method Invocation
Details" tab. Anyway, this is not the real blocking problem! :-)
My aim is to perform Dynamic Instrumentation, but I won't be able to do
it until the profiling cannot be launched from TPTP workbench
I know that my description is generic, so please ask me any information
you need.
Thanks for your attention,
Alessandro Tucci
|
|
|
Powered by
FUDForum. Page generated in 0.02538 seconds
Home