Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » Profiling application that requires JVM 1.3
Profiling application that requires JVM 1.3 [message #75301] Tue, 27 June 2006 14:36 Go to next message
Eclipse User
Originally posted by: w.eschebach.vsnlinternational.com

I am pretty new to profiling with tptp, but struggled already
over-proportionally with resolving the following problem: profiling an
application which requires JVM 1.3.

When I do the Run or Debug thing, I can choose which JVM to use. But not
for the Profiling. And implicitely 1.4.2 is used.

If I do the attach thing, I get a serious exception thrown:

Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D460157
Function name=JVM_FindSignal
Library=C:\jdk1.3.1_12\jre\bin\hotspot\jvm.dll

Current Java thread:
at
java.text.resources.LocaleElements_en_US.getContents(LocaleE lements_en_US.java:46)
at java.util.ListResourceBundle.loadLookup(ListResourceBundle.j ava:183)
- locked <2c86978> (a java.text.resources.LocaleElements_en_US)
at
java.util.ListResourceBundle.handleGetObject(ListResourceBun dle.java:120)
at java.util.ResourceBundle.getObject(ResourceBundle.java:371)
at java.text.DateFormatSymbols.initializeData(DateFormatSymbols .java:483)
at java.text.DateFormatSymbols.<init>(DateFormatSymbols.java:99)
at java.text.SimpleDateFormat.<init>(SimpleDateFormat.java:275)
at java.util.Date.toString(Date.java:975)
at java.lang.String.valueOf(String.java:2013)
at java.lang.StringBuffer.append(StringBuffer.java:365)
- locked <2c85ec0> (a java.lang.StringBuffer)
at
com.tycotelecom.ta.tools.ListenToTEMSsECs.push(ListenToTEMSs ECs.java:83)
- locked <2c5a760> (a com.tycotelecom.ta.tools.ListenToTEMSsECs)
at
org.omg.CosEventComm._PushConsumerImplBase._OB_op_push(_Push ConsumerImplBase.java:40)
at
org.omg.CosEventComm._PushConsumerImplBase.invoke(_PushConsu merImplBase.java:108)
at com.ooc.CORBA.BOA._OB_dispatch(BOA.java:1427)
at
com.ooc.CORBA.GIOPServerWorker.dispatchRequest(GIOPServerWor ker.java:443)
at
com.ooc.CORBA.GIOPServerWorkerThreaded.dispatchRequest(GIOPS erverWorkerThreaded.java:252)
- locked <2c5a2a0> (a java.lang.Object)
at com.ooc.CORBA.GIOPServerWorker.execute(GIOPServerWorker.java :290)
at
com.ooc.CORBA.GIOPServerWorkerThreaded.receiverRun(GIOPServe rWorkerThreaded.java:593)
at
com.ooc.CORBA.GIOPServerWorkerThreaded$ReceiverThread.run(GI OPServerWorkerThreaded.java:56)

Dynamic libraries:
0x00400000 - 0x00405000 C:\jdk1.3.1_12\bin\javaw.exe
0x7C900000 - 0x7C9B0000 C:\WINDOWS\system32\ntdll.dll
0x7C800000 - 0x7C8F4000 C:\WINDOWS\system32\kernel32.dll
0x77DD0000 - 0x77E6B000 C:\WINDOWS\system32\ADVAPI32.dll
0x77E70000 - 0x77F01000 C:\WINDOWS\system32\RPCRT4.dll
0x77D40000 - 0x77DD0000 C:\WINDOWS\system32\USER32.dll
0x77F10000 - 0x77F57000 C:\WINDOWS\system32\GDI32.dll
0x77C10000 - 0x77C68000 C:\WINDOWS\system32\MSVCRT.dll
0x6D420000 - 0x6D4FB000 C:\jdk1.3.1_12\jre\bin\hotspot\jvm.dll
0x76B40000 - 0x76B6D000 C:\WINDOWS\system32\WINMM.dll
0x6D220000 - 0x6D227000 C:\jdk1.3.1_12\jre\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 C:\jdk1.3.1_12\jre\bin\verify.dll
0x6D250000 - 0x6D268000 C:\jdk1.3.1_12\jre\bin\java.dll
0x6D3C0000 - 0x6D3CD000 C:\jdk1.3.1_12\jre\bin\zip.dll
0x10000000 - 0x10096000 C:\WINDOWS\system32\piAgent.dll
0x71AB0000 - 0x71AC7000 C:\WINDOWS\system32\WS2_32.dll
0x71AA0000 - 0x71AA8000 C:\WINDOWS\system32\WS2HELP.dll
0x08CC0000 - 0x08CCB000 C:\WINDOWS\system32\hcclco.dll
0x08CD0000 - 0x08CD8000 C:\WINDOWS\system32\hccldt.dll
0x08CE0000 - 0x08CF1000 C:\WINDOWS\system32\hcclsm.dll
0x08D00000 - 0x08D09000 C:\WINDOWS\system32\hccls.dll
0x08D10000 - 0x08D1A000 C:\WINDOWS\system32\hcbnd.dll
0x6D2A0000 - 0x6D2BB000 C:\jdk1.3.1_12\jre\bin\jdwp.dll
0x6D1D0000 - 0x6D1D5000 C:\jdk1.3.1_12\bin\dt_socket.dll
0x0D3C0000 - 0x0D3CE000
C:\RAD6.0\AgentController\plugins\com.ibm.rational.pd.probek it\lib\ProbeAgentExtension.dll
0x71A50000 - 0x71A8F000 C:\WINDOWS\System32\mswsock.dll
0x76F20000 - 0x76F47000 C:\WINDOWS\system32\DNSAPI.dll
0x76FB0000 - 0x76FB8000 C:\WINDOWS\System32\winrnr.dll
0x76F60000 - 0x76F8C000 C:\WINDOWS\system32\WLDAP32.dll
0x76FC0000 - 0x76FC6000 C:\WINDOWS\system32\rasadhlp.dll
0x43000000 - 0x43005000 C:\Program Files\Google\Google Desktop
Search\GoogleDesktopNetwork1.dll
0x77FE0000 - 0x77FF1000 C:\WINDOWS\system32\Secur32.dll
0x662B0000 - 0x66308000 C:\WINDOWS\system32\hnetcfg.dll
0x71A90000 - 0x71A98000 C:\WINDOWS\System32\wshtcpip.dll
0x6D340000 - 0x6D348000 C:\jdk1.3.1_12\jre\bin\net.dll
0x71AD0000 - 0x71AD9000 C:\WINDOWS\system32\WSOCK32.dll
0x76C90000 - 0x76CB8000 C:\WINDOWS\system32\imagehlp.dll
0x59A60000 - 0x59B01000 C:\WINDOWS\system32\DBGHELP.dll
0x77C00000 - 0x77C08000 C:\WINDOWS\system32\VERSION.dll
0x76BF0000 - 0x76BFB000 C:\WINDOWS\system32\PSAPI.DLL

Local Time = Tue Jun 27 14:33:30 2006
Elapsed Time = 175
#
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002BF
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1_12-b03 interpreted mode)
#
# An error report file has been saved as hs_err_pid7092.log.
# Please refer to the file for further information.
#


Any ideas? Help is appreciated very much.

Thanks,
Wilko
Re: Profiling application that requires JVM 1.3 [message #75318 is a reply to message #75301] Tue, 27 June 2006 14:56 Go to previous messageGo to next message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Wilko,

From your message, it seems that the crash happened when you tried to
attach to the runnning application, but it is not clear whether you used
"controlled" or "enabled" mode when launching your Java application under
the profiler.
Please provide more details on this subject. Also, please specify the
exact TPTP and Eclipse workbench versions you used.

As a workaround for this problem: have you tried running the profiler in
"standalone" mode? In this mode, the profiling data is written to a file
which can be then imported to the Eclipse workbench for offline analysis.

For more information on running the profiler in "standalone" mode, please
refer to the following section in the Eclipse documentation: "Monitoring
and Profiling Applications > Profiling an Application > Profiling an
application in stand-alone mode"

Best regards,
Asaf
Re: Profiling application that requires JVM 1.3 [message #75334 is a reply to message #75318] Tue, 27 June 2006 16:55 Go to previous messageGo to next message
Eclipse User
Originally posted by: w.eschebach.vsnlinternational.com

Hi Asaf,

Thank you for you quick reply.

Eclipse version is 3.1.2. TPTP versionis 4.1.0.1.

Right, the crash happens when I attach to the process to be monitored.
Mode was "enabled". I had tried it with "standalone". In that case the
process crashes almost instantly. In fact when the code gets executed that
requires JVM 1.3 (Orbacus; see below). When I use JVM 1.4, unfortunately
the other code that requires JVM 1.3 throws an exception.

Are they any known problems with TPTP and JVM 1.3?

Let me know if you need any further information, of if you want me to do
some more experiments.

Thanks a lot for your help!

Wilko




Output of process with "standalone" setting:

JVM version: 1.3.1_12
JVM vendor: Sun Microsystems Inc.
JVM home: C:\jdk1.3.1_12\jre
Initializing ORB
Initializing BOA

Unexpected Signal : EXCEPTION_ACCESS_VIOLATION occurred at PC=0x6D460131
Function name=JVM_FindSignal
Library=C:\jdk1.3.1_12\jre\bin\hotspot\jvm.dll

Current Java thread:
at
sun.security.util.ManifestEntryVerifier.<init>(ManifestEntryVerifier.java:34)
at java.util.jar.JarFile.initializeVerifier(JarFile.java:237)
at java.util.jar.JarFile.getInputStream(JarFile.java:305)
- locked <2d0f3f0> (a java.util.jar.JarFile)
at sun.misc.JarIndex.getJarIndex(JarIndex.java:90)
at sun.misc.URLClassPath$JarLoader.<init>(URLClassPath.java:463)
at sun.misc.URLClassPath$2.run(URLClassPath.java:253)
at java.security.AccessController.doPrivileged(Native Method)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:242)
at sun.misc.URLClassPath.getLoader(URLClassPath.java:219)
- locked <2c23a50> (a sun.misc.URLClassPath)
at sun.misc.URLClassPath.getResource(URLClassPath.java:132)
at java.net.URLClassLoader$1.run(URLClassLoader.java:187)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:183)
at java.lang.ClassLoader.loadClass(ClassLoader.java:294)
- locked <2c20028> (a sun.misc.Launcher$AppClassLoader)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:288 )
- locked <2c20028> (a sun.misc.Launcher$AppClassLoader)
at java.lang.ClassLoader.loadClass(ClassLoader.java:250)
at java.net.URL.getURLStreamHandler(URL.java:922)
at java.net.URL.<init>(URL.java:473)
at java.net.URL.<init>(URL.java:371)
at java.net.URL.<init>(URL.java:325)
at com.ooc.CORBA.Properties.load(Properties.java:42)
at com.ooc.CORBA.Properties.init(Properties.java:232)
- locked <2ccaac0> (a java.lang.Object)
at com.ooc.CORBA.ORB.set_parameters(ORB.java:495)
at org.omg.CORBA.ORB.init(ORB.java:324)
at
com.tycotelecom.ta.tools.StethoscopeForTEMS.main(Stethoscope ForTEMS.java:108)

Dynamic libraries:
0x00400000 - 0x00405000 C:\jdk1.3.1_12\bin\javaw.exe
0x7C900000 - 0x7C9B0000 C:\WINDOWS\system32\ntdll.dll
0x7C800000 - 0x7C8F4000 C:\WINDOWS\system32\kernel32.dll
0x77DD0000 - 0x77E6B000 C:\WINDOWS\system32\ADVAPI32.dll
0x77E70000 - 0x77F01000 C:\WINDOWS\system32\RPCRT4.dll
0x77D40000 - 0x77DD0000 C:\WINDOWS\system32\USER32.dll
0x77F10000 - 0x77F57000 C:\WINDOWS\system32\GDI32.dll
0x77C10000 - 0x77C68000 C:\WINDOWS\system32\MSVCRT.dll
0x6D420000 - 0x6D4FB000 C:\jdk1.3.1_12\jre\bin\hotspot\jvm.dll
0x76B40000 - 0x76B6D000 C:\WINDOWS\system32\WINMM.dll
0x6D220000 - 0x6D227000 C:\jdk1.3.1_12\jre\bin\hpi.dll
0x6D3B0000 - 0x6D3BD000 C:\jdk1.3.1_12\jre\bin\verify.dll
0x6D250000 - 0x6D268000 C:\jdk1.3.1_12\jre\bin\java.dll
0x6D3C0000 - 0x6D3CD000 C:\jdk1.3.1_12\jre\bin\zip.dll
0x10000000 - 0x10096000 C:\WINDOWS\system32\piAgent.dll
0x71AB0000 - 0x71AC7000 C:\WINDOWS\system32\WS2_32.dll
0x71AA0000 - 0x71AA8000 C:\WINDOWS\system32\WS2HELP.dll
0x08CC0000 - 0x08CCB000 C:\WINDOWS\system32\hcclco.dll
0x08CD0000 - 0x08CD8000 C:\WINDOWS\system32\hccldt.dll
0x08CE0000 - 0x08CF1000 C:\WINDOWS\system32\hcclsm.dll
0x08D00000 - 0x08D09000 C:\WINDOWS\system32\hccls.dll
0x08D10000 - 0x08D1A000 C:\WINDOWS\system32\hcbnd.dll
0x6D2A0000 - 0x6D2BB000 C:\jdk1.3.1_12\jre\bin\jdwp.dll
0x6D1D0000 - 0x6D1D5000 C:\jdk1.3.1_12\bin\dt_socket.dll
0x71A50000 - 0x71A8F000 C:\WINDOWS\System32\mswsock.dll
0x76F20000 - 0x76F47000 C:\WINDOWS\system32\DNSAPI.dll
0x76FB0000 - 0x76FB8000 C:\WINDOWS\System32\winrnr.dll
0x76F60000 - 0x76F8C000 C:\WINDOWS\system32\WLDAP32.dll
0x76FC0000 - 0x76FC6000 C:\WINDOWS\system32\rasadhlp.dll
0x43000000 - 0x43005000 C:\Program Files\Google\Google Desktop
Search\GoogleDesktopNetwork1.dll
0x77FE0000 - 0x77FF1000 C:\WINDOWS\system32\Secur32.dll
0x662B0000 - 0x66308000 C:\WINDOWS\system32\hnetcfg.dll
0x71A90000 - 0x71A98000 C:\WINDOWS\System32\wshtcpip.dll
0x76C90000 - 0x76CB8000 C:\WINDOWS\system32\imagehlp.dll
0x59A60000 - 0x59B01000 C:\WINDOWS\system32\DBGHELP.dll
0x77C00000 - 0x77C08000 C:\WINDOWS\system32\VERSION.dll
0x76BF0000 - 0x76BFB000 C:\WINDOWS\system32\PSAPI.DLL

Local Time = Tue Jun 27 16:49:14 2006
Elapsed Time = 6
#
# HotSpot Virtual Machine Error : EXCEPTION_ACCESS_VIOLATION
# Error ID : 4F530E43505002BF
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.3.1_12-b03 interpreted mode)
#
# An error report file has been saved as hs_err_pid7528.log.
# Please refer to the file for further information.
#
Re: Profiling application that requires JVM 1.3 [message #75368 is a reply to message #75334] Wed, 28 June 2006 02:51 Go to previous messageGo to next message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Wilko,

This seems like a specific issue with the Sun JVM 1.3. I searched the
Eclipse bug system and found some similar issues reported for Java 1.4,
but I am not sure whether these issues are related. As a last resort, you
may want to try launching your Java application in interpreted mode by
adding the -Xint option to the Java command line. This may help, but don't
count on it :(

Anyway, I suggest you open a Bugzilla for this issue. This way, your
problem report will find its way to the right people in the TPTP project
and may be addressed in future releases. Note, however, that Java 1.3 is
quite old and I am not sure the TPTP team will find it beneficial to
invest time in resolving problems which are specific to Java 1.3.

To open a Bugzilla, go to https://bugs.eclipse.org/bugs/, click the
"Report a new Bug" link and then click the TPTP link. Make sure to specify
the correct TPTP version and to include as much information as you can in
the Description field. Also, attach the Sun crash log or include the crash
information as part of the description.

Sorry for not being able to come up with a more practical solution to your
problem.

Best regards,
Asaf
Re: Profiling application that requires JVM 1.3 [message #75418 is a reply to message #75334] Wed, 28 June 2006 10:32 Go to previous messageGo to next message
Eclipse User
Originally posted by: nmehrega.ca.ibm.com

This is a multipart message in MIME format.
--=_alternative 004FF1018525719B_=
Content-Type: text/plain; charset="US-ASCII"

Can you check your PATH environment variable and make sure you don't have
another copy of piAgent.dll or other RAC DLLs in your PATH? Sometimes
when you have multiple versions of these DLLs in your PATH, they will
conflict and throw an exception.

Also, which version of TPTP/Hyades are you using? You might want to
consider downgrading to Hyades 1.3:
http://www.eclipse.org/tptp/home/downloads/drops/1.3.0_20040 422_2239.html
which was tested with JVM 1.3.

You can't change your JVM for a specific profiling launch configuration,
but you can change it for all launch configurations by selecting Window ->
Preferences -> Java -> Installed JREs and selecting your JRE there.

Navid Mehregani
--=_alternative 004FF1018525719B_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=2 face="sans-serif">Can you check your PATH environment
variable and make sure you don't have another copy of piAgent.dll or other
RAC DLLs in your PATH? &nbsp;Sometimes when you have multiple versions
of these DLLs in your PATH, they will conflict and throw an exception.</font>
<br>
<br><font size=2 face="sans-serif">Also, which version of TPTP/Hyades are
you using? &nbsp;You might want to consider downgrading to Hyades 1.3:
http://www.eclipse.org/tptp/home/downloads/drops/1.3.0_20040 422_2239.html
which was tested with JVM 1.3. &nbsp;</font>
<br>
<br><font size=2 face="sans-serif">You can't change your JVM for a specific
profiling launch configuration, but you can change it for all launch configurations
by selecting Window -&gt; Preferences -&gt; Java -&gt; Installed JREs and
selecting your JRE there.</font>
<br>
<br><font size=2 face="sans-serif">Navid Mehregani</font>
--=_alternative 004FF1018525719B_=--
Re: Profiling application that requires JVM 1.3 [message #75569 is a reply to message #75368] Thu, 29 June 2006 11:31 Go to previous messageGo to next message
Eclipse User
Originally posted by: w.eschebach.vsnlinternational.com

Asaf,

The -Xint option didn't have much of an impact on my problem (just slowed
down the execution a bit).

Ok, I will open a bug report.

I have tried to port my application to use JRE 1.4 but that hasn't worked
out yet. Next thing is to try out what Navid suggests.

Thanks again for your efforts,
Wilko
Re: Profiling application that requires JVM 1.3 [message #75603 is a reply to message #75418] Thu, 29 June 2006 11:50 Go to previous messageGo to next message
Eclipse User
Originally posted by: w.eschebach.vsnlinternational.com

The PATH variable looks good. Not much in it that can cause trouble. I had
discovered that another RAService was running (started by WebSphere RAD
which I recently installed on my machine; uses IBM JRE), but also after
shutting that down and starting the RAServer that comes with TPTP I got
the same results.

I tried your suggestion to change the JRE for Eclipse through the
Preferences but my application sill crashes. When I looking at the
RAServer config setup it tells you that JRE 1.4 or greater is required.

The TPTP/Hyades version I use is 4.1. Using 1.3 looks like a good idea. I
have already downloaded almost all the packages, but have trouble to find
where to download Eclipse 2.1 (since Hyades 1.3 doesn't support Eclipse
3.x). Would you know?

Thanks a lot for your help,
Wilko
Re: Profiling application that requires JVM 1.3 [message #75671 is a reply to message #75603] Thu, 29 June 2006 14:30 Go to previous messageGo to next message
Eclipse User
Originally posted by: w.eschebach.vsnlinternational.com

Ok, I found the Eclipse 2.1 download area. Was not as obvious as with the
other component downloads.

Wilko
Re: Profiling application that requires JVM 1.3 [message #76061 is a reply to message #75603] Sun, 02 July 2006 12:02 Go to previous messageGo to next message
Eclipse User
Originally posted by: nmehrega.ca.ibm.com

This is a multipart message in MIME format.
--=_alternative 005822418525719F_=
Content-Type: text/plain; charset="US-ASCII"

>I had discovered that another RAService was running (started by WebSphere
RAD ...

This is probably your problem. The DLLs of your IBM RAC is conflicting
with the TPTP RAC, which causes your JVM to crash. This is a known
problem. Can you check c:\windows\system32 for piAgent.dll or do a search
for piAgent.dll in your windows directory. If it's there, you have a
problem. You need to Uninstall the IBM RAC probably and make sure the RAC
DLLs are removed from your windows directory before you try out the TPTP
RAC.

Navid Mehregani
--=_alternative 005822418525719F_=
Content-Type: text/html; charset="US-ASCII"


<br><tt><font size=2>&gt;I had discovered that another RAService was running
(started by WebSphere RAD ...</font></tt>
<br>
<br><font size=2 face="sans-serif">This is probably your problem. &nbsp;The
DLLs of your IBM RAC is conflicting with the TPTP RAC, which causes your
JVM to crash. &nbsp;This is a known problem. &nbsp;Can you check c:\windows\system32
for piAgent.dll or do a search for piAgent.dll in your windows directory.
&nbsp;If it's there, you have a problem. &nbsp;You need to Uninstall the
IBM RAC probably and make sure the RAC DLLs are removed from your windows
directory before you try out the TPTP RAC.</font>
<br>
<br><font size=2 face="sans-serif">Navid Mehregani</font>
--=_alternative 005822418525719F_=--
Re: Profiling application that requires JVM 1.3 [message #76324 is a reply to message #76061] Wed, 05 July 2006 09:09 Go to previous message
Eclipse User
Originally posted by: w.eschebach.vsnlinternational.com

I installed my application and TPTP on a fresh machine that has never seen
IBM RAD and things like that. The problem still occurs. I guess TPTP 4.1
simply is not able to handle JRE 1.3.

I still have to try out Hyades 1.3.

Wilko
Previous Topic:JMX Attribute logging or statistical agent controller...
Next Topic:Sources
Goto Forum:
  


Current Time: Sat Aug 30 00:31:48 EDT 2014

Powered by FUDForum. Page generated in 0.05633 seconds