Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Test and Performance Tools Platform (TPTP) » init JPIBootLoader
init JPIBootLoader [message #101051] Fri, 15 June 2007 20:50 Go to next message
Dave Thomas is currently offline Dave Thomas
Messages: 3
Registered: July 2009
Junior Member
Hi,
I'm new to profiling with tptp and I'm trying the TPTP-4.4.0-200706110100
(allInOne) with WST 2.0RC1 (25 May 2007).

As if through some freak accident I have the new agent controller
(4.4.0-200706110100) also playing nice with TPTP. I say this because it
took me a day of reading about it all, getting a few different agents,
switching JDKS (JDK 1.5.0_12 runtime won't workwith the agent on JRE
1.5.0_06).

I can test hosts and now from the monitor tab I can test the availability
of > JRE 1.5 profiling :)

1. I'm able to profile java applications OK but when I try to profile my
Tomcat 6 web app (using WST) I get:
Error occurred during initialization of VM
agent library failed to init: JPIBootLoader

2. As a workaround I've found I can run the server add the following VM
argument:
-agentlib:JPIBootLoader=JPIAgent:server=enabled;HeapProf:all ocsites=true
(or CGProf)
...and attach an agent (via profile...attach agent). I see it processing
megabytes of data but I see I'm not collecting any data.

3. I'm probably trying to do something I shouldn't be trying to do but if
I try to start tomcat in Debug instead of Run I get
ERROR: JDWP unable to get necessary JVMTI capabilities.
["debugInit.c",L279]

TIA

Dave
Re: init JPIBootLoader [message #101080 is a reply to message #101051] Mon, 18 June 2007 07:08 Go to previous messageGo to next message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Dave,

>
> 1. I'm able to profile java applications OK but when I try to profile
> my Tomcat 6 web app (using WST) I get:
> Error occurred during initialization of VM
> agent library failed to init: JPIBootLoader
>

I think there are still problems with the Profile on Server feature in
the June 11 build. It seems that these problems were resolved and that
the fix will be incorporated to the next "candidate" build (should be
available this week). See
https://bugs.eclipse.org/bugs/show_bug.cgi?id=186246 for more information.

> 2. As a workaround I've found I can run the server add the following VM
> argument:
> -agentlib:JPIBootLoader=JPIAgent:server=enabled;HeapProf:all ocsites=true
> (or CGProf)
> ..and attach an agent (via profile...attach agent). I see it processing
> megabytes of data but I see I'm not collecting any data.

You can minimize the amount of data generated by the profiler runtime
(HeapProf, CGProf...) by applying filters. See my post here for more
information:
http://dev.eclipse.org/newslists/news.eclipse.tptp/msg03993. html

Also, note that the viewers themselves have some built-in filters which
are sometimes applied by default. Find the "filters" tool-button, open
its menu and select "no filters" and check if you see any results.

>
> 3. I'm probably trying to do something I shouldn't be trying to do but
> if I try to start tomcat in Debug instead of Run I get
> ERROR: JDWP unable to get necessary JVMTI capabilities.
> ["debugInit.c",L279]
>

Mmmmm.. Starting Tomcat in Debug Mode with the profiler (the
-agentlib:... argument) is not a supported use case. It requires the JVM
to launch 2 JVMTI Agents (the debugger and the profiler). Why would you
want to do that?

HTH,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Re: init JPIBootLoader [message #106976 is a reply to message #101080] Wed, 01 August 2007 11:28 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi everybody,
I am experiencing the same kind of trouble reported by Dave Thomas in
the message I'm quoting.

Dave_Thomas mailing lists wrote:
>
> Hi,
> I'm new to profiling with tptp and I'm trying the
> TPTP-4.4.0-200706110100 (allInOne) with WST 2.0RC1 (25 May 2007).
>


Dave_Thomas mailing lists wrote:
>
> when I try to profile
> my Tomcat 6 web app (using WST) I get:
> Error occurred during initialization of VM
> agent library failed to init: JPIBootLoader
>


I'm new to profiling at all! :-) I am using TPTP 4.4.0 all-in-one
stable release on Linux SuSE 10.1

I firstly tried to make IAC work on a JDK 1.6.0, using Tomcat 5.5,
JOnAS v4 and JBoss 4.2 as servers. When I worked against JDK 1.6.0, I
could use
only "JRE 1.5.0 or newer" profiling services. Any server I launched, any
service I chose, the console output was:

Error occurred during initialization of VM
agent library failed to init: JPIBootLoader"

I thought it was due to the fact that tptp 4.4.0 had not been properly
tested against jvm 1.6. Therefore, I tried to use another jvm, that is
JRE 1.5.0_06: also "JDK 1.4" profiling services were available
now (i.e. the ones that could be used in tptp 4.3). When using "JRE 1.5.0
or
newer" profiling services, I still received the mentioned output; instead,
when
using old services, everything worked (for any service, for any server).

I also tried to use the last tptp 4.4.1 development releases avalaible
on 30th July 2007. After checking the installation of the new plugins, I
tried launching profiling services. No difference in tptp's behaviour was
observed.

I read that a bug with a similar effect has been already fixed. Do you
think
this is a new bug or there could be some errors I made?
Thanks for your attention,
Alessandro Tucci
Re: init JPIBootLoader [message #107374 is a reply to message #106976] Thu, 02 August 2007 15:38 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
This seems like a bug on Linux Platform. I tried standalone profile (which
is how server profiling is started) and it's give me the same kind of
error message.

I have opened bug 198693 to track this problem.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=198693
Re: init JPIBootLoader [message #107518 is a reply to message #107374] Fri, 03 August 2007 16:39 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
OS: Linux SuSE 10.1
JVM: jdk 1.5.0_12
ECLIPSE: 3.3.0
TPTP: both 4.4.0 and 4.4.0.2 Mantainance version (AllinOne, no deprecated
technology previews)

Hi Eugene.
>I have opened bug 198693 to track this problem.
>https://bugs.eclipse.org/bugs/show_bug.cgi?id=198693

I read about the bug you opened and I also read Guru's answer:

>Eugene,
>The right command line will be
>java -agentlib:JPIBootLoader=JPIAgent:server=enabled;HeapProf
>PerformanceExample
>
>you have missed the prof to be loaded in the above scenario "HeapProf" for
>Memory Profiling.

Please let me know whether the command works now.

I also tried to install TPTP 4.4.0.2 Mantainance release and I'm
experiencing exactly the same response.
Furthermore, I tried to profile a non-web Java application with jre 1.5 or
newer profiling services: everything worked and the results were really
satisfying, because the improved Memory analisys let me quickly pick out
several memory leaks. It is such a pity that those services are actually
unavailable in "Profile on Server" mode. Anyway, by this it can be stated
that the problem is limited to web-app profiling.

Just for curiosity, I tried to install the Standalone AC.
The installation was successful: I provided jre 1.5.0_12 as jvm, no
security, full access, both tomcat and jboss home dirs (I have both them
exactly to test tptp profile on server :-) ). The AC started
successfully, then. Instead, the sample client connected to the port 10006
but the output was:

unable to get Connected to the Agent Controller on "localhost" at port
number 10006
ERROR: Unable to get agent org.eclipse.tptp.TimeCollector
Press any key to exit...

Let me point out that "SampleClient" worked instead on WinXP 32 bit, jre
1.5.0_8.
Therefore, I right-clicked on the web-app I wanted to profile (the sample
web-app provided in the tutorial), I chose "Open Profile Dialog" and
opened the section "Attach to agent". There were two entries:

localhost:10002
localhost:10006

Both connection tests returned a "connection success"!! Although the
connection worked, there was an error message in the "Agents" section:

error retrieving running agents - see log for details

I could not find that error log: if somebody can tell me which is the
file, I'll will report the error.

Thanks for your attention,
Alessandro Tucci

P.S.: no error is due to sample web app configuration. I setted the proper
compiler compliance (5.0), the proper jvm to be used by IAC and by the
application (1.5.0_12) and the proper versions of the eclipse plugin
requested by the project. Furthermore, I added the file
<<j2ee 5 home dir>>/lib/javaee.jar
as External Jar to compile the servlets.
Re: init JPIBootLoader [message #108029 is a reply to message #107374] Wed, 08 August 2007 20:08 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi Eugene,
I read that the bug you had opened was fixed. I could understand that the
problem on linux platform is that the process is launched without the
proper single quotes, isn't it? Just a question about it: as I previously
wrote, Profile on Server works perfectly when "java profiling - pre jre
1.5" are chosen. Which is the reason of this difference? Is the profiler
called correctly only in the last case? It is just curiosity, answer when
you have nothing else to do! :-)
Thanks,
Alessandro
Re: init JPIBootLoader [message #108476 is a reply to message #108029] Fri, 10 August 2007 20:01 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Alessandro Tucci wrote:

> Hi Eugene,
> I read that the bug you had opened was fixed. I could understand that the
> problem on linux platform is that the process is launched without the
> proper single quotes, isn't it? Just a question about it: as I previously
> wrote, Profile on Server works perfectly when "java profiling - pre jre
> 1.5" are chosen. Which is the reason of this difference? Is the profiler
> called correctly only in the last case? It is just curiosity, answer when
> you have nothing else to do! :-)
> Thanks,
> Alessandro

Hi Alessandro.

The JVM1.4 data collector has a different VM argument command compare with
JVM1.5+ data collector. That explains why JVM1.4 works for you on Linux.
It seems like the Profile on Server code has a bug on Linux Platform. I
have opened bug 199632 which is currently target 4.4.1 to fix the problem.
In the meantime, There is two way you can work around the problem, either
manually input the Environment Variables and VM arguments for profile
server in Run mode, or launch your server process in profile External Java
Application configuration. The later one should be easier and you will
have to get the server startup command from the Server Run configuration.

Please feel free to add yourself to bug 199632 for update on the fix.
Eugene
Re: init JPIBootLoader [message #108613 is a reply to message #108476] Sun, 12 August 2007 13:33 Go to previous messageGo to next message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Eugene Chan wrote:
> Alessandro Tucci wrote:
>
>> Hi Eugene,
>> I read that the bug you had opened was fixed. I could understand that
>> the problem on linux platform is that the process is launched without
>> the proper single quotes, isn't it? Just a question about it: as I
>> previously wrote, Profile on Server works perfectly when "java
>> profiling - pre jre 1.5" are chosen. Which is the reason of this
>> difference? Is the profiler called correctly only in the last case? It
>> is just curiosity, answer when you have nothing else to do! :-)
>> Thanks,
>> Alessandro
>
> Hi Alessandro.
>
> The JVM1.4 data collector has a different VM argument command compare
> with JVM1.5+ data collector. That explains why JVM1.4 works for you on
> Linux. It seems like the Profile on Server code has a bug on Linux
> Platform. I have opened bug 199632 which is currently target 4.4.1 to
> fix the problem. In the meantime, There is two way you can work around
> the problem, either manually input the Environment Variables and VM
> arguments for profile server in Run mode, or launch your server process
> in profile External Java Application configuration. The later one should
> be easier and you will have to get the server startup command from the
> Server Run configuration.
>
> Please feel free to add yourself to bug 199632 for update on the fix.
> Eugene
>

Just a clarification on the single-quote characters required by the Java
1.5+ profiler: the command line syntax for the Java 1.5+ profiler is
using the ';' character to separate certain parts of the command line.
The problem is that the Linux shell interprets the ';' character as a
command terminator. To overcome this behavior, the entire -agentlib
argument must be surrounded with single quotes. This is a Linux-specific
issue and applies only to the new 1.5+ profiler.

Thanks,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Re: init JPIBootLoader [message #108946 is a reply to message #108613] Tue, 14 August 2007 10:50 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi Eugene,
hi Asaf,
thanks for your interest. The quality of "jre 1.5 or newer" profiling
services is much higher than "jre pre-1.5" and it would be quite a pity if
they could not be tested properly against a server. Every workaround
causes a loss of integration, but the one you suggested to me lets me stay
in the IDE at least.
Thanks again,
Alessandro Tucci
Re: init JPIBootLoader [message #109196 is a reply to message #108946] Thu, 16 August 2007 16:58 Go to previous messageGo to next message
Eugene Chan is currently offline Eugene Chan
Messages: 287
Registered: July 2009
Senior Member
Hi Alessandro,

The problem is now fixed in bug 199632
(https://bugs.eclipse.org/bugs/show_bug.cgi?id=199632). The bug turns out
to be a library path missing for Linux platform. The fix is tested on
Linux RHEL40 and Windows XP with both Tomcat 5.5 and 6.0 servers.
The fix will be picked up in the next TPTP 4.4.1 build. It's not yet a GA
release, but it should let you profile the servers without error.

Hope this help
Eugene
Re: init JPIBootLoader [message #113053 is a reply to message #108476] Sat, 22 September 2007 22:40 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
This is a multi-part message in MIME format.
--------------000006070400020602060505
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: 7bit

Hi Eugene,
I tried to use the workaround you suggested to me with no success.
The first was:

> > manually input the Environment Variables and VM
> > arguments for profile server in Run mode

Therefore I created a new configuration in "Apache Tomcat" menu. I wrote
in the "Arguments" tab:

- Program arguments:

start


- VM arguments:

-Dcatalina.base=" /home/atx85/Programmi/Java/IDE/eclipse_mant/workspace/.metad ata/.plugins/org.eclipse.wst.server.core/tmp0 "
-Dcatalina.home="/home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23 "
-Dwtp.deploy=" /home/atx85/Programmi/Java/IDE/eclipse_mant/workspace/.metad ata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps "
-Djava.endorsed.dirs=" /home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23/ common/endorsed "
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.port=9004
'-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf'

(that is, those ones specified in the "standard" apache tomacat 5.5
configuration plus the JVMTI argument)


This configuration leads to the following error at the server startup:

Exception in thread "main" java.lang.NoClassDefFoundError:
'-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf'

Therefore, I tried to put the single quotes only around the semicolon,
to let the parser recognize the "-agentlib" directive. It resulted in a
wrong usage error. The output was:

Bad TIAgent option

@(#)JVMTI Agent version 1.0.0.1
Usage:
-agentlib:JPIBootLoader=JPIAgent[:[help]|[<option>=<value >,
....]];<profiler>
[...]

Therefore, I tried to sorround the whole directive with double quotes or
no quotes at all, i.e.:

"-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf"

and

-agentlib:JPIBootLoader=JPIAgent:server=enabled;CGProf

The server starts, but I cannot find any trace.trcxml file. Therefore, I
tried to specifY it in the directive:


" -agentlib:JPIBootLoader=JPIAgent:server=enabled,file=/home/a tx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23/bin/tra ce.trcxml;CGProf "

and

-agentlib:JPIBootLoader=JPIAgent:server=enabled,file=/home/a tx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23/bin/tra ce.trcxml;CGProf

The server starts; I click on the links of my web app to cause some
method invocations, but the specified file is not created. The startup
output is the following:

22-set-2007 23.55.21 org.apache.catalina.core.AprLifecycleListener
lifecycleEvent
INFO: The Apache Tomcat Native library which allows optimal performance
in production environments was not found on the java.library.path:
/home/atx85/Programmi/Java/vm/jdk1.5.0_12/jre/lib/i386/clien t:/home/atx85/Programmi/Java/vm/jdk1.5.0_12/jre/lib/i386:/ho me/atx85/Programmi/Java/vm/jdk1.5.0_12/jre/../lib/i386:/usr/ java/jdk1.6.0_02/jre/lib/i386/client::/usr/java/jdk1.6.0_02/ jre/lib/i386:::/home/atx85/Programmi/Java/IDE/eclipse/AgentC ontroller/plugins/org.eclipse.tptp.javaprofiler:/home/atx85/ Programmi/Java/IDE/eclipse/AgentController/lib:/usr/local/li b:/opt/wx/2.8/lib:/usr/X11R6/lib:/usr/local/lib:/usr/lib/xul runner-1.8.0.1:/usr/lib/xulrunner-1.8.0.1
22-set-2007 23.55.21 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing Coyote HTTP/1.1 on http-8080
22-set-2007 23.55.21 org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 4121 ms
22-set-2007 23.55.22 org.apache.catalina.core.StandardService start
INFO: Starting service Catalina
22-set-2007 23.55.22 org.apache.catalina.core.StandardEngine start
INFO: Starting Servlet Engine: Apache Tomcat/5.5.23
22-set-2007 23.55.22 org.apache.catalina.core.StandardHost start
INFO: XML validation disabled
22-set-2007 23.55.22 org.apache.catalina.loader.WebappClassLoader
validateJarFile
INFO:
validateJarFile(/home/atx85/Programmi/Java/IDE/eclipse_mant/ workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp 0/wtpwebapps/sample/WEB-INF/lib/javaee.jar)
- jar not loaded. See Servlet Spec 2.3, section 9.7.2. Offending class:
javax/servlet/Servlet.class
22-set-2007 23.55.23 org.apache.coyote.http11.Http11BaseProtocol start
INFO: Starting Coyote HTTP/1.1 on http-8080
22-set-2007 23.55.24 org.apache.jk.common.ChannelSocket init
INFO: JK: ajp13 listening on /0.0.0.0:8009
22-set-2007 23.55.24 org.apache.jk.server.JkMain start
INFO: Jk running ID=0 time=0/125 config=null
22-set-2007 23.55.24 org.apache.catalina.storeconfig.StoreLoader load
INFO: Find registry server-registry.xml at classpath resource
22-set-2007 23.55.24 org.apache.catalina.startup.Catalina start
INFO: Server startup in 3071 ms


Therefore I tried the second way:
..
> > launch your server process
> > in profile External Java Application configuration
> > [...]
> > you will have to get the server startup command from the
> > Server Run configuration

I created the new configuration in the "External Java Application" menu.
In the "Main" tab I wrote:

- Class Name:
org.apache.catalina.startup.Bootstrap
(that is, the class passed to the java command when starting apache
tomcat 5.5)

- Class Path:
/home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23/ bin/bootstrap.jar:/home/atx85/Programmi/Java/vm/jdk1.5.0_12/ lib/tools.jar:/home/atx85/Programmi/WebServer/Tomcat/apache- tomcat-5.5.23/bin/commons-logging-api.jar
(that is, the classpath specified in the apache tomcat configuration)


In the "Arguments" tab I wrote:

- Program Arguments:
start

- VM Arguments:
-Dcatalina.base=" /home/atx85/Programmi/Java/IDE/eclipse_mant/workspace/.metad ata/.plugins/org.eclipse.wst.server.core/tmp0 "
-Dcatalina.home="/home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23 "
-Dwtp.deploy=" /home/atx85/Programmi/Java/IDE/eclipse_mant/workspace/.metad ata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps "
-Djava.endorsed.dirs=" /home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23/ common/endorsed "
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.port=9004

(the same arguments passed in the apache tomcat configuration)

When I click on the "Profile" button, this exception is raised after awhile:

org.eclipse.core.runtime.CoreException
A time-out occurred while attempting to launch the process

org.eclipse.core.runtime.CoreException: A time-out occurred while
attempting to launch the process
at
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti lity.createCoreException(LauncherUtility.java:123)
at
org.eclipse.tptp.trace.ui.internal.launcher.core.LauncherUti lity.createCoreException(LauncherUtility.java:131)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.handleError(TIDelegateHelper.java:592)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.launchProcess(TIDelegateHelper.java:511)
at
org.eclipse.tptp.platform.jvmti.client.internal.launcher.TID elegateHelper.launch(TIDelegateHelper.java:311)
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)

Therefore I tried to create an equivalent configuration in the "Java
Application" menu.
In the "Main" tab I specified no project, whereas I filled the remaining
fields in an equivalent way:

- "Main" tab:
- "Main Class" field:
org.apache.catalina.startup.Bootstrap

- "Arguments" tab
- "Program arguments" field:
start

- "VM Arguments":

-Dcatalina.base=" /home/atx85/Programmi/Java/IDE/eclipse_mant/workspace/.metad ata/.plugins/org.eclipse.wst.server.core/tmp0 "
-Dcatalina.home="/home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23 "
-Dwtp.deploy=" /home/atx85/Programmi/Java/IDE/eclipse_mant/workspace/.metad ata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps "
-Djava.endorsed.dirs=" /home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23/ common/endorsed "
-Dcom.sun.management.jmxremote -Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.port=9004


- "Classpath" tab:
The same as "Apache tomcat" standard configuration.

In this case, the server seems to start after clicking on the "Profile"
button, but after few seconds I obtain this error:

Error: Exception thrown by the agent : java.rmi.server.ExportException:
Port already in use: 9004; nested exception is:
java.net.BindException: Address already in use
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0xb68ef8d8, pid=26193, tid=3084904112
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_12-b04 mixed mode)
# Problematic frame:
# C [libCGProf.so+0xb8d8]
#
# An error report file with more information is saved as hs_err_pid26193.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
#

The mentioned file (hs_err_pid26193.log) is attached.
What I am doing wrong?

Thanks for your interest,
Alessandro Tucci




--------------000006070400020602060505
Content-Type: text/x-log;
name="hs_err_pid26193.log"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline;
filename="hs_err_pid26193.log"

#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=3D0xb68ef8d8, pid=3D26193, tid=3D3084904112
#
# Java VM: Java HotSpot(TM) Client VM (1.5.0_12-b04 mixed mode)
# Problematic frame:
# C [libCGProf.so+0xb8d8]
#

--------------- T H R E A D ---------------

Current thread (0x0807ebb0): JavaThread "main" [_thread_in_native, id=3D=
26193]

siginfo:si_signo=3D11, si_errno=3D0, si_code=3D1, si_addr=3D0x00000004

Registers:
EAX=3D0x00000005, EBX=3D0x00000003, ECX=3D0x00000005, EDX=3D0x00000000
ESP=3D0xbfa89100, EBP=3D0xbfa89128, ESI=3D0x00000000, EDI=3D0x00000000
EIP=3D0xb68ef8d8, CR2=3D0x00000004, EFLAGS=3D0x00010286

Top of Stack: (sp=3D0xbfa89100)
0xbfa89100: 00000002 00000000 00000000 b768c882
0xbfa89110: 00000004 ffffffff bfa89248 00000003
0xbfa89120: 00000000 08cad1d0 bfa89168 b68ef953
0xbfa89130: 00000000 00000003 00000000 00000005
0xbfa89140: 00000007 b7f1c15c 000001da b79e442c
0xbfa89150: 00000000 0807ebb0 bfa89188 00000003
0xbfa89160: 00000000 08c6e298 bfa891a8 b68ef953
0xbfa89170: 08cad1d0 00000003 00000000 00000006=20

Instructions: (pc=3D0xb68ef8d8)
0xb68ef8c8: 5e 5f 5d c3 55 89 e5 57 56 53 83 ec 1c 8b 7d 08
0xb68ef8d8: 8b 57 04 8b 5d 0c 8b 75 10 8b 07 89 d1 31 f1 31=20

Stack: [0xbf894000,0xbfa94000), sp=3D0xbfa89100, free space=3D2004k
Native frames: (J=3Dcompiled Java code, j=3Dinterpreted, Vv=3DVM code, C=3D=
native code)
C [libCGProf.so+0xb8d8]
C [libCGProf.so+0xb953]
C [libCGProf.so+0xb953]
C [libCGProf.so+0xb953]
C [libCGProf.so+0xb953]
C [libCGProf.so+0xb55f]
C [libCGProf.so+0xb121]
C [libJPI.so+0x14066]
C [libJPI.so+0x13c01]
C [libJPI.so+0x186f2]
C [libJPI.so+0x213e1]
V [libjvm.so+0x244ac6]
V [libjvm.so+0x179235]
V [libjvm.so+0x1d336b]
C [libjava.so+0xcc7f] Java_java_lang_Shutdown_halt0+0x1f
j java.lang.Shutdown.halt0(I)V+0
j java.lang.Shutdown.halt(I)V+7
j java.lang.Shutdown.exit(I)V+100
j java.lang.Runtime.exit(I)V+14
j java.lang.System.exit(I)V+4
j sun.management.Agent.error(Ljava/lang/String;Ljava/lang/Stri ng;)V+62
j sun.management.Agent.error(Ljava/lang/String;[Ljava/lang/Str ing;)V+72
j sun.management.Agent.premain(Ljava/lang/String;)V+115
v ~StubRoutines::call_stub
V [libjvm.so+0x17b19c]
V [libjvm.so+0x28fb38]
V [libjvm.so+0x17afcf]
V [libjvm.so+0x2b9fac]
V [libjvm.so+0x2bccba]
V [libjvm.so+0x1ef442]
C [libjava.so+0x137b4] Java_sun_reflect_NativeMethodAccessorImpl_invoke=
0+0x34
j sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/refl ect/Method=
;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+0
j sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Objec t;[Ljava/l=
ang/Object;)Ljava/lang/Object;+87
j sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/O bject;[Lja=
va/lang/Object;)Ljava/lang/Object;+6
j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lan g/Object;)=
Ljava/lang/Object;+111
j sun.management.Agent.startAgent()V+157
v ~StubRoutines::call_stub
V [libjvm.so+0x17b19c]
V [libjvm.so+0x28fb38]
V [libjvm.so+0x17ae42]
V [libjvm.so+0x17aea1]
V [libjvm.so+0x264df5]
V [libjvm.so+0x2fd1cc]
V [libjvm.so+0x1a547c]
C [java+0x32cc]
C [java+0x15a4] calloc+0x39c
C [libc.so.6+0x1587c] __libc_start_main+0xdc

Java frames: (J=3Dcompiled Java code, j=3Dinterpreted, Vv=3DVM code)
j java.lang.Shutdown.halt0(I)V+0
j java.lang.Shutdown.halt(I)V+7
j java.lang.Shutdown.exit(I)V+100
j java.lang.Runtime.exit(I)V+14
j java.lang.System.exit(I)V+4
j sun.management.Agent.error(Ljava/lang/String;Ljava/lang/Stri ng;)V+62
j sun.management.Agent.error(Ljava/lang/String;[Ljava/lang/Str ing;)V+72
j sun.management.Agent.premain(Ljava/lang/String;)V+115
v ~StubRoutines::call_stub
j sun.reflect.NativeMethodAccessorImpl.invoke0(Ljava/lang/refl ect/Method=
;Ljava/lang/Object;[Ljava/lang/Object;)Ljava/lang/Object;+0
j sun.reflect.NativeMethodAccessorImpl.invoke(Ljava/lang/Objec t;[Ljava/l=
ang/Object;)Ljava/lang/Object;+87
j sun.reflect.DelegatingMethodAccessorImpl.invoke(Ljava/lang/O bject;[Lja=
va/lang/Object;)Ljava/lang/Object;+6
j java.lang.reflect.Method.invoke(Ljava/lang/Object;[Ljava/lan g/Object;)=
Ljava/lang/Object;+111
j sun.management.Agent.startAgent()V+157
v ~StubRoutines::call_stub

--------------- P R O C E S S ---------------

Java Threads: ( =3D> current thread )
0x08c92490 JavaThread "RMI TCP Accept-0" daemon [_thread_in_native, id=3D=
26231]
0x08c5b3d0 JavaThread "Timer-0" daemon [_thread_blocked, id=3D26230]
0x082daff0 JavaThread "Low Memory Detector" daemon [_thread_blocked, id=
=3D26223]
0x082babc0 JavaThread "CompilerThread0" daemon [_thread_blocked, id=3D2=
6222]
0x082f7b18 JavaThread "Signal Dispatcher" daemon [_thread_blocked, id=3D=
26221]
0x081adac8 JavaThread "Finalizer" daemon [_thread_blocked, id=3D26216]
0x080dd128 JavaThread "Reference Handler" daemon [_thread_blocked, id=3D=
26215]
=3D>0x0807ebb0 JavaThread "main" [_thread_in_native, id=3D26193]

Other Threads:
0x081946c8 VMThread [id=3D26214]

VM state:not at safepoint (normal execution)

VM Mutex/Monitor currently owned by a thread: None

Heap
def new generation total 576K, used 173K [0xa80c0000, 0xa8160000, 0xa8=
5a0000)
eden space 512K, 21% used [0xa80c0000, 0xa80db700, 0xa8140000)
from space 64K, 100% used [0xa8150000, 0xa8160000, 0xa8160000)
to space 64K, 0% used [0xa8140000, 0xa8140000, 0xa8150000)
tenured generation total 1408K, used 1003K [0xa85a0000, 0xa8700000, 0x=
ac0c0000)
the space 1408K, 71% used [0xa85a0000, 0xa869acb8, 0xa869ae00, 0xa870=
0000)
compacting perm gen total 8192K, used 5461K [0xac0c0000, 0xac8c0000, 0x=
b00c0000)
the space 8192K, 66% used [0xac0c0000, 0xac615468, 0xac615600, 0xac8c=
0000)
No shared spaces configured.

Dynamic libraries:
08048000-08057000 r-xp 00000000 03:07 189141 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/bin/java
08057000-08059000 rwxp 0000e000 03:07 189141 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/bin/java
08059000-08d80000 rwxp 08059000 00:00 0 [heap]
a6aff000-a6b02000 rwxp a6aff000 00:00 0=20
a6b02000-a6b80000 rwxp a6b02000 00:00 0=20
a6b80000-a6b83000 ---p a6b80000 00:00 0=20
a6b83000-a6c01000 rwxp a6b83000 00:00 0=20
a6c01000-a6c04000 ---p a6c01000 00:00 0=20
a6c04000-a6c82000 rwxp a6c04000 00:00 0=20
a6c82000-a6caf000 r-xs 00000000 03:07 160622 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.mx4j.jmx_3.0.2.v2 00706080100/m=
x4j-remote.jar
a6caf000-a6d18000 r-xs 00000000 03:07 160633 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.mx4j.jmx_3.0.2.v2 00706080100/m=
x4j.jar
a6d18000-a6d20000 r-xs 00000000 03:07 160685 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.moni toring.instru=
mentation_4.3.0.v200705070853/cbeModel.jar
a6d20000-a6d2d000 r-xs 00000000 03:07 160699 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.moni toring.instru=
mentation_4.3.0.v200705070853/jmxModel.jar
a6d2d000-a6d33000 r-xs 00000000 03:07 160710 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.opengroup.arm_4.0 .0.v200706020=
100/arm40_java_interfaces.jar
a6d33000-a6d3e000 r-xs 00000000 03:07 160672 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.trac e.arm_4.3.0.v=
200706132116/armModel.jar
a6d3e000-a6d64000 r-xs 00000000 03:07 160669 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.trac e.arm_4.3.0.v=
200706132116/armLibrary.jar
a6d64000-a6d6a000 r-xs 00000000 03:07 160682 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.trac e.arm_4.3.0.v=
200706132116/cbeLogging.jar
a6d6a000-a6d6f000 r-xs 00000000 03:07 204248 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.opengroup.arm/arm 40_java_inter=
faces.jar
a6d6f000-a6d78000 r-xs 00000000 03:07 199437 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.trac e.arm/armMode=
l.jar
a6d78000-a6d9b000 r-xs 00000000 03:07 199289 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.trac e.arm/armLibr=
ary.jar
a6d9b000-a6da0000 r-xs 00000000 03:07 199466 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.trac e.arm/cbeLogg=
ing.jar
a6da0000-a6dc7000 r-xs 00000000 03:07 160227 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.emf.commo n_2.2.2.v2007=
06070004.jar
a6dc7000-a6e7f000 r-xs 00000000 03:07 160228 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.emf.ecore _2.2.3.v20070=
6070004.jar
a6e7f000-a6ea5000 r-xs 00000000 03:07 160374 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.plat form.logging.=
events_4.3.100.v200704140100/tlcbe101.jar
a6ea5000-a6ed6000 r-xs 00000000 03:07 160377 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.plat form.logging.=
events_4.3.100.v200704140100/hlcbe101.jar
a6ed6000-a6edf000 r-xs 00000000 03:07 160376 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.plat form.logging.=
events_4.3.100.v200704140100/tlcore.jar
a6edf000-a6ee1000 r-xs 00000000 03:07 160396 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.lo gging.core_4.=
3.100.v200704140100/config.jar
a6ee1000-a6ee5000 r-xs 00000000 03:07 160395 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.lo gging.core_4.=
3.100.v200704140100/hllog4j.jar
a6ee5000-a6ee9000 r-xs 00000000 03:07 160392 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.lo gging.core_4.=
3.100.v200704140100/hlcore.jar
a6ee9000-a6eed000 r-xs 00000000 03:07 160394 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.lo gging.core_4.=
3.100.v200704140100/hlcommons.jar
a6eed000-a6ef3000 r-xs 00000000 03:07 160393 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.lo gging.core_4.=
3.100.v200704140100/hl14.jar
a6ef3000-a72d0000 r-xs 00000000 03:07 160515 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/com.ibm.icu_3.6.1.v20 070417.jar
a72d0000-a73b3000 r-xs 00000000 03:07 160514 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.osgi_3.3. 0.v20070530.j=
ar
a73b3000-a73ca000 r-xs 00000000 03:07 160229 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.equinox.c ommon_3.3.0.v=
20070426.jar
a73ca000-a73dc000 r-xs 00000000 03:07 160516 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.core.runt ime_3.3.100.v=
20070530.jar
a73dc000-a7415000 r-xs 00000000 03:07 160327 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.ex ecution_4.4.0=
=2Ev200706080100/hexcore.jar
a7415000-a748f000 r-xs 00000000 03:07 160328 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.ex ecution_4.4.0=
=2Ev200706080100/hexl.jar
a748f000-a7499000 r-xs 00000000 03:07 160323 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.hyades.ex ecution_4.4.0=
=2Ev200706080100/hexr.jar
a7499000-a74cf000 r-xs 00000000 03:07 160505 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.plat form.collecti=
on.framework_4.2.100.v200704140100/hcframe.jar
a74cf000-a74d3000 r-xs 00000000 03:07 172304 /home/atx85/Programmi/We=
bServer/Tomcat/apache-tomcat-5.5.23/bin/tomcat-juli.jar
a74d3000-a74da000 r-xs 00000000 03:07 172290 /home/atx85/Programmi/We=
bServer/Tomcat/apache-tomcat-5.5.23/bin/commons-logging-api. jar
a74da000-a74dd000 r-xs 00000000 03:07 172289 /home/atx85/Programmi/We=
bServer/Tomcat/apache-tomcat-5.5.23/bin/commons-daemon.jar
a74dd000-a74e3000 r-xs 00000000 03:07 172285 /home/atx85/Programmi/We=
bServer/Tomcat/apache-tomcat-5.5.23/bin/bootstrap.jar
a74e3000-a7b9b000 r-xs 00000000 03:07 188433 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/lib/tools.jar
a7b9b000-a7c60000 r-xs 00000000 03:07 189114 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/ext/localedata.jar
a7c60000-a7c87000 r-xs 00000000 03:07 188509 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/ext/sunjce_provider.jar
a7c87000-a7cb2000 r-xs 00000000 03:07 188510 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/ext/sunpkcs11.jar
a7cb2000-a7ce7000 r-xs 00000000 03:06 550310 /var/run/nscd/dbv5oGcK (=
deleted)
a7ce7000-a7cf8000 r-xp 00000000 03:07 188475 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libnet.so
a7cf8000-a7cf9000 rwxp 00011000 03:07 188475 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libnet.so
a7cf9000-a7cff000 r-xp 00000000 03:07 188477 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libmanagement.so
a7cff000-a7d00000 rwxp 00005000 03:07 188477 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libmanagement.so
a7d00000-a7d03000 ---p a7d00000 00:00 0=20
a7d03000-a7d81000 rwxp a7d03000 00:00 0=20
a7d81000-a7d84000 ---p a7d81000 00:00 0=20
a7d84000-a7e02000 rwxp a7d84000 00:00 0=20
a7e02000-a7e05000 ---p a7e02000 00:00 0=20
a7e05000-a7e83000 rwxp a7e05000 00:00 0=20
a7e83000-a7e8a000 r-xs 00000000 03:06 99097 /usr/lib/gconv/gconv-mod=
ules.cache
a7e8a000-a7ebd000 r-xp 00000000 03:06 101989 /usr/lib/locale/it_IT.ut=
f8/LC_CTYPE
a7ebd000-a7ec0000 ---p a7ebd000 00:00 0=20
a7ec0000-a7f3e000 rwxp a7ec0000 00:00 0=20
a7f3e000-a7f41000 ---p a7f3e000 00:00 0=20
a7f41000-a7fbf000 rwxp a7f41000 00:00 0=20
a7fbf000-a7fc0000 ---p a7fbf000 00:00 0=20
a7fc0000-a8045000 rwxp a7fc0000 00:00 0=20
a8045000-a8061000 rwxp a8045000 00:00 0=20
a8061000-a8062000 rwxp a8061000 00:00 0=20
a8062000-a807f000 rwxp a8062000 00:00 0=20
a807f000-a8080000 rwxp a807f000 00:00 0=20
a8080000-a8081000 rwxp a8080000 00:00 0=20
a8081000-a8083000 rwxp a8081000 00:00 0=20
a8083000-a809f000 rwxp a8083000 00:00 0=20
a809f000-a80a3000 rwxp a809f000 00:00 0=20
a80a3000-a80bf000 rwxp a80a3000 00:00 0=20
a80bf000-a8160000 rwxp a80bf000 00:00 0=20
a8160000-a85a0000 rwxp a8160000 00:00 0=20
a85a0000-a8700000 rwxp a85a0000 00:00 0=20
a8700000-ac0c0000 rwxp a8700000 00:00 0=20
ac0c0000-ac8c0000 rwxp ac0c0000 00:00 0=20
ac8c0000-b00c0000 rwxp ac8c0000 00:00 0=20
b00c1000-b00c3000 r-xs 00000000 03:07 160375 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.plat form.logging.=
events_4.3.100.v200704140100/config.jar
b00c3000-b00c5000 r-xs 00000000 03:07 188511 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/ext/dnsns.jar
b00c5000-b00c9000 rwxp b00c5000 00:00 0=20
b00c9000-b0145000 rwxp b00c9000 00:00 0=20
b0145000-b020d000 rwxp b0145000 00:00 0=20
b020d000-b2145000 rwxp b020d000 00:00 0=20
b2145000-b29b4000 r-xs 00000000 03:07 189113 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/charsets.jar
b29b4000-b29c9000 r-xs 00000000 03:07 188513 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/jce.jar
b29c9000-b2a4e000 r-xs 00000000 03:07 189054 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/jsse.jar
b2a4e000-b2ab7000 rwxp b2a4e000 00:00 0=20
b2ab7000-b50dc000 r-xs 00000000 03:07 189135 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/rt.jar
b50dc000-b50eb000 r-xp 00000000 03:07 188472 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libzip.so
b50eb000-b50ed000 rwxp 0000e000 03:07 188472 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libzip.so
b50ed000-b510e000 r-xp 00000000 03:07 188470 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libjava.so
b510e000-b5110000 rwxp 00020000 03:07 188470 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libjava.so
b5110000-b511b000 r-xp 00000000 03:07 188469 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libverify.so
b511b000-b511c000 rwxp 0000b000 03:07 188469 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/libverify.so
b511c000-b5124000 rwxs 00000000 03:06 571464 /tmp/hsperfdata_atx85/26=
193
b5124000-b5159000 r-xs 00000000 03:06 550259 /var/run/nscd/passwd
b5159000-b51ba000 r-xp 00000000 03:07 160611 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
IE.so
b51ba000-b51cc000 rwxp 00061000 03:07 160611 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
IE.so
b51cc000-b51d0000 rwxp b51cc000 00:00 0=20
b51d0000-b51da000 r-xp 00000000 03:07 160607 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libC=
GAdaptor.so
b51da000-b51dd000 rwxp 00009000 03:07 160607 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libC=
GAdaptor.so
b51dd000-b52df000 rwxs 00000000 00:08 110919696 /SYSV6d06b847 (deleted)
b52df000-b5300000 rwxs 00000000 00:08 110886927 /SYSV6d06b846 (deleted)
b5300000-b5301000 ---p b5300000 00:00 0=20
b5301000-b5b01000 rwxp b5301000 00:00 0=20
b5b01000-b5b22000 rwxs 00000000 00:08 110886927 /SYSV6d06b846 (deleted)
b5b22000-b5c24000 rwxs 00000000 00:08 106135566 /SYSV6d06ae2f (deleted)
b5c24000-b5c25000 ---p b5c24000 00:00 0=20
b5c25000-b6425000 rwxp b5c25000 00:00 0=20
b6425000-b645f000 r-xp 00000000 03:06 146389 /usr/lib/libstdc++-3-lib=
c6.2-2-2.10.0.so
b645f000-b6470000 rwxp 00039000 03:06 146389 /usr/lib/libstdc++-3-lib=
c6.2-2-2.10.0.so
b6470000-b6472000 rwxp b6470000 00:00 0=20
b6472000-b6474000 r-xp 00000000 03:07 160136 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libhccls.so.4.4.0
b6474000-b6476000 rwxp 00001000 03:07 160136 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libhccls.so.4.4.0
b6476000-b647d000 r-xp 00000000 03:07 160139 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libhcclsm.so.4.4.0
b647d000-b647e000 rwxp 00006000 03:07 160139 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libhcclsm.so.4.4.0
b647e000-b647f000 rwxp b647e000 00:00 0=20
b647f000-b67ce000 r-xp 00000000 03:07 160195 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libxerces-c.so.26
b67ce000-b6884000 rwxp 0034e000 03:07 160195 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libxerces-c.so.26
b6884000-b6886000 rwxp b6884000 00:00 0=20
b6886000-b689a000 r-xp 00000000 03:07 160184 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpConfig.so.4.4.0
b689a000-b689d000 rwxp 00013000 03:07 160184 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpConfig.so.4.4.0
b689d000-b68a0000 rwxp b689d000 00:00 0=20
b68a0000-b68ab000 r-xp 00000000 03:07 160187 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpLogUtils.so.4.4.0
b68ab000-b68ad000 rwxp 0000a000 03:07 160187 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpLogUtils.so.4.4.0
b68ad000-b68c9000 r-xp 00000000 03:07 160190 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpUtils.so.4.4.0
b68c9000-b68cd000 rwxp 0001b000 03:07 160190 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpUtils.so.4.4.0
b68cd000-b68e0000 r-xp 00000000 03:07 160606 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libA=
CCollector.so
b68e0000-b68e4000 rwxp 00012000 03:07 160606 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libA=
CCollector.so
b68e4000-b68fd000 r-xp 00000000 03:07 160608 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libC=
GProf.so
b68fd000-b6902000 rwxp 00018000 03:07 160608 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libC=
GProf.so
b6902000-b75a9000 rwxp b6902000 00:00 0=20
b75a9000-b75dc000 r-xp 00000000 03:07 160612 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
PI.so
b75dc000-b75ea000 rwxp 00032000 03:07 160612 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
PI.so
b75ea000-b75fb000 r-xp 00000000 03:06 87307 /lib/libnsl-2.4.so
b75fb000-b75fd000 rwxp 00010000 03:06 87307 /lib/libnsl-2.4.so
b75fd000-b75ff000 rwxp b75fd000 00:00 0=20
b7600000-b7609000 r-xp 00000000 03:07 160130 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libhcclco.so.4.4.0
b7609000-b760a000 rwxp 00008000 03:07 160130 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libhcclco.so.4.4.0
b760a000-b760e000 r-xp 00000000 03:07 160193 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtransportSupport.so.4. 4.0
b760e000-b760f000 rwxp 00003000 03:07 160193 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtransportSupport.so.4. 4.0
b760f000-b7613000 r-xp 00000000 03:07 160160 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libprocessControlUtil.so. 4.4.0
b7613000-b7614000 rwxp 00003000 03:07 160160 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libprocessControlUtil.so. 4.4.0
b7614000-b762d000 r-xp 00000000 03:07 160613 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
PIAgent.so
b762d000-b7632000 rwxp 00018000 03:07 160613 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
PIAgent.so
b7632000-b7655000 r-xp 00000000 03:06 87304 /lib/libm-2.4.so
b7655000-b7657000 rwxp 00022000 03:06 87304 /lib/libm-2.4.so
b7657000-b79c9000 r-xp 00000000 03:07 188463 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/client/libjvm.so
b79c9000-b79e7000 rwxp 00371000 03:07 188463 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/client/libjvm.so
b79e7000-b7dff000 rwxp b79e7000 00:00 0=20
b7dff000-b7f18000 r-xp 00000000 03:06 87296 /lib/libc-2.4.so
b7f18000-b7f1a000 r-xp 00118000 03:06 87296 /lib/libc-2.4.so
b7f1a000-b7f1c000 rwxp 0011a000 03:06 87296 /lib/libc-2.4.so
b7f1c000-b7f20000 rwxp b7f1c000 00:00 0=20
b7f20000-b7f22000 r-xp 00000000 03:06 87302 /lib/libdl-2.4.so
b7f22000-b7f24000 rwxp 00001000 03:06 87302 /lib/libdl-2.4.so
b7f24000-b7f34000 r-xp 00000000 03:06 87322 /lib/libpthread-2.4.so
b7f34000-b7f36000 rwxp 0000f000 03:06 87322 /lib/libpthread-2.4.so
b7f36000-b7f38000 rwxp b7f36000 00:00 0=20
b7f38000-b7f47000 r-xp 00000000 03:07 160172 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpAgentBase.so.4.4.0
b7f47000-b7f4a000 rwxp 0000e000 03:07 160172 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/lib/libtptpAgentBase.so.4.4.0
b7f4a000-b7f4c000 r-xp 00000000 03:06 127789 /lib/libuuid.so.1.2
b7f4c000-b7f4d000 rwxp 00001000 03:06 127789 /lib/libuuid.so.1.2
b7f4d000-b7f4e000 rwxp b7f4d000 00:00 0=20
b7f4e000-b7f57000 r-xp 00000000 03:07 160615 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libM=
artiniOSA.so
b7f57000-b7f59000 rwxp 00009000 03:07 160615 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libM=
artiniOSA.so
b7f59000-b7f60000 r-xp 00000000 03:07 160614 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
PIBootLoader.so
b7f60000-b7f62000 rwxp 00006000 03:07 160614 /home/atx85/Programmi/Ja=
va/IDE/eclipse/AgentController/plugins/org.eclipse.tptp.java profiler/libJ=
PIBootLoader.so
b7f62000-b7f68000 r-xp 00000000 03:07 188457 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/native_threads/libhpi.so
b7f68000-b7f69000 rwxp 00006000 03:07 188457 /home/atx85/Programmi/Ja=
va/vm/jdk1.5.0_12/jre/lib/i386/native_threads/libhpi.so
b7f69000-b7f6a000 rwxp b7f69000 00:00 0=20
b7f6a000-b7f6b000 r-xp b7f6a000 00:00 0=20
b7f6b000-b7f6c000 rwxp b7f6b000 00:00 0=20
b7f6c000-b7f86000 r-xp 00000000 03:06 87289 /lib/ld-2.4.so
b7f86000-b7f88000 rwxp 00019000 03:06 87289 /lib/ld-2.4.so
bf894000-bf897000 ---p bf894000 00:00 0=20
bf897000-bfa94000 rwxp bf897000 00:00 0 [stack]
ffffe000-fffff000 ---p 00000000 00:00 0 [vdso]

VM Arguments:
jvm_args: -Dcatalina.base=3D"/home/atx85/Programmi/Java/IDE/eclipse_mant/=
workspace/.metadata/.plugins/org.eclipse.wst.server.core/tmp 0 " -Dcatalina=
=2Ehome=3D"/home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23 " -=
Dwtp.deploy=3D"/home/atx85/Programmi/Java/IDE/eclipse_mant/workspace/.met=
adata/.plugins/org.eclipse.wst.server.core/tmp0/wtpwebapps" -Djava.endors=
ed.dirs=3D" /home/atx85/Programmi/WebServer/Tomcat/apache-tomcat-5.5.23/ co=
mmon/endorsed" -Dcom.sun.management.jmxremote -Dcom.sun.management.jmxrem=
ote.ssl=3Dfalse -Dcom.sun.management.jmxremote.authenticate=3Dfalse -Dcom=
=2Esun.management.jmxremote.port=3D9004 -agentlib:JPIBootLoader=3DJPIAgen=
t:server=3Dcontrolled;CGProf:execdetails=3Dtrue
java_command: org.apache.catalina.startup.Bootstrap start=20
Launcher Type: SUN_STANDARD

Environment Variables:
JAVA_HOME=3D/usr/lib/jvm/java
JRE_HOME=3D/usr/lib/jvm/java/jre
PATH=3D/home/atx85/Programmi/Java/vm/jdk1.5.0_12/bin/java:/h ome/atx85/Pro=
grammi/Java/IDE/eclipse/AgentController/plugins/org.eclipse. tptp.javaprof=
iler:/home/atx85/Programmi/Java/IDE/eclipse/AgentController/ bin:/home/atx=
85/Programmi/Java/IDE/eclipse/AgentController/plugins/org.ec lipse.hyades.=
probekit/lib:/home/atx85/Programmi/Java/IDE/eclipse/AgentCon troller/bin:/=
home/atx85/bin:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/ usr/games:/op=
t/gnome/bin:/opt/kde3/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin :/usr/lib/qt3=
/bin:/home/atx85/Programmi/Java/IDE/eclipse/AgentController/ bin:/home/atx=
85/Programmi/WebServer/Tomcat/JONAS_4_8_6/bin/unix:/opt/wx/2 .8/bin
LD_LIBRARY_PATH=3D/home/atx85/Programmi/Java/vm/jdk1.5.0_12/ jre/lib/i386/=
client:/home/atx85/Programmi/Java/vm/jdk1.5.0_12/jre/lib/i38 6:/home/atx85=
/Programmi/Java/vm/jdk1.5.0_12/jre/../lib/i386:/home/atx85/P rogrammi/Java=
/IDE/eclipse/AgentController/lib:/home/atx85/Programmi/Java/ IDE/eclipse/A=
gentController/plugins/org.eclipse.tptp.javaprofiler:/home/a tx85/Programm=
i/Java/IDE/eclipse/AgentController/lib:/home/atx85/Programmi /Java/IDE/ecl=
ipse/AgentController/lib:/home/atx85/Programmi/Java/IDE/ecli pse/AgentCont=
roller/lib:/home/atx85/Programmi/Java/vm/jdk1.5.0_12/jre/lib /i386/server:=
/home/atx85/Programmi/Java/vm/jdk1.5.0_12/jre/lib/i386:/usr/ lib:/usr/java=
/jdk1.6.0_02/jre/lib/i386/client::/usr/java/jdk1.6.0_02/jre/ lib/i386:::/h=
ome/atx85/Programmi/Java/IDE/eclipse/AgentController/plugins /org.eclipse.=
tptp.javaprofiler:/home/atx85/Programmi/Java/IDE/eclipse/Age ntController/=
lib:/usr/local/lib:/opt/wx/2.8/lib:/usr/X11R6/lib:/usr/local /lib:/usr/lib=
/xulrunner-1.8.0.1:/usr/lib/xulrunner-1.8.0.1
SHELL=3D/bin/bash
DISPLAY=3D:0
HOSTTYPE=3Di386
OSTYPE=3Dlinux
MACHTYPE=3Di686-suse-linux

Signal Handlers:
SIGSEGV: [libjvm.so+0x32b1b0], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x1000=
0004
SIGBUS: [libjvm.so+0x32b1b0], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x10000=
004
SIGFPE: [libjvm.so+0x28eb70], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x10000=
004
SIGPIPE: [libjvm.so+0x28eb70], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x1000=
0004
SIGILL: [libjvm.so+0x28eb70], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x10000=
004
SIGUSR1: SIG_DFL, sa_mask[0]=3D0x00000000, sa_flags=3D0x00000000
SIGUSR2: [libjvm.so+0x290fc0], sa_mask[0]=3D0x00000004, sa_flags=3D0x1000=
0004
SIGHUP: [libjvm.so+0x2909f0], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x10000=
004
SIGINT: SIG_IGN, sa_mask[0]=3D0x00000000, sa_flags=3D0x00000000
SIGQUIT: [libjvm.so+0x2909f0], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x1000=
0004
SIGTERM: [libjvm.so+0x2909f0], sa_mask[0]=3D0x7ffbfeff, sa_flags=3D0x1000=
0004


--------------- S Y S T E M ---------------

OS:SUSE LINUX 10.1 (i586)
VERSION =3D 10.1

uname:Linux 2.6.16.13-4-smp #1 SMP Wed May 3 04:53:23 UTC 2006 i686
libc:glibc 2.4 NPTL 2.4=20
rlimit: STACK 8192k, CORE 0k, NPROC 8190, NOFILE 1024, AS infinity
load average:0.42 0.46 0.70

CPU:total 1 (cores per cpu 1, threads per core 1) family 6 model 13 stepp=
ing 8, cmov, cx8, fxsr, mmx, sse, sse2

Memory: 4k page, physical 1035236k(13568k free), swap 1558264k(1558116k f=
ree)

vm_info: Java HotSpot(TM) Client VM (1.5.0_12-b04) for linux-x86, built o=
n May 2 2007 03:26:22 by java_re with gcc 3.2.1-7a (J2SE release)


--------------000006070400020602060505--
Re: init JPIBootLoader: partially resolved - HeapProf starts but Object Allocations view does not sh [message #113868 is a reply to message #113053] Tue, 02 October 2007 16:18 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
Hi Eugene,
I found a way to make JVMPI work against Tomcat 5.5 server.
I added the -agentlib directive to the launch command in catalina.sh.
The directive has been properly sorrounded with single quotes:

"$_RUNJAVA" $JAVA_OPTS $CATALINA_OPTS
-Djava.endorsed.dirs="$JAVA_ENDORSED_DIRS" -classpath "$CLASSPATH"
-Dcatalina.base="$CATALINA_BASE" -Dcatalina.home="$CATALINA_HOME"
-Djava.io.tmpdir="$CATALINA_TMPDIR"
'-agentlib:JPIBootLoader=JPIAgent:server=controlled;HeapProf '
org.apache.catalina.startup.Bootstrap "$@" start >>
"$CATALINA_BASE"/logs/catalina.out 2>&1 &

Everything works when I use CGProf: the profiler starts, therefore I
open the Profile Menu in TPTP, I open "Attach to agent" and I select the
proper agent. The Execution Statisticds view, in the end, shows me
everything I need.
It is not the same when I try to perform Memory Analysis analysis: the
agent is still available, therefore I select it and I start the
profiling session, but there is non data available to display in the
end. I checked the filter, but it is ok; furthermore, it works when I
perform Execution Time Analysis, therefore the error cannot be there.
The option "Track object allocation details" has been checked, too. Do
you have any idea about it?
Thanks for your attention,
Alessandro Tucci
Re: init JPIBootLoader: partially resolved - HeapProf starts but Object Allocations view does not sh [message #113908 is a reply to message #113868] Tue, 02 October 2007 22:16 Go to previous messageGo to next message
Alessandro Tucci is currently offline Alessandro Tucci
Messages: 33
Registered: July 2009
Member
I tried to perform Memory Analysis in the same way I explained in my
last message, but with no filter set.
(that is, INCLUDE * * *)
The package which contains the classes of my web app is named
eclipseworld. After clicking on my web app links, I opened the Object
Allocation Details tab: a lot of classes and packages appeared, as
expected, but NO CLASS beloging to eclipseworld package was displayed! :-(
Maybe I am not understanding what the Heap Profiler is expected to do,
therefore I am not able to work out the right way to launch it. Can
somebody explain me what I am doing wrong?
Thanks for your attention,
Alessandro Tucci
Re: init JPIBootLoader: partially resolved - HeapProf starts but Object Allocations view does not sh [message #115046 is a reply to message #113908] Wed, 10 October 2007 13:44 Go to previous message
Asaf Yaffe is currently offline Asaf Yaffe
Messages: 333
Registered: July 2009
Senior Member
Alessandro Tucci wrote:
> I tried to perform Memory Analysis in the same way I explained in my
> last message, but with no filter set.
> (that is, INCLUDE * * *)
> The package which contains the classes of my web app is named
> eclipseworld. After clicking on my web app links, I opened the Object
> Allocation Details tab: a lot of classes and packages appeared, as
> expected, but NO CLASS beloging to eclipseworld package was displayed! :-(
> Maybe I am not understanding what the Heap Profiler is expected to do,
> therefore I am not able to work out the right way to launch it. Can
> somebody explain me what I am doing wrong?
> Thanks for your attention,
> Alessandro Tucci

The Heap Profiler tracks objects allocated on the Java heap with the
"new" operator. The views show information about the allocated objects,
and where they were allocated. If your application *allocates* objects
of classes defined in the "eclipseworld" package, then you should see
these objects in the views. If not, make sure no filters are set by the
profiler runtime OR in the views themselves.

HTH,
Asaf

--
Asaf Yaffe
Eclipse TPTP Committer, JVMTI Profiler
Previous Topic:Allocation details tab does not show all instances of objects
Next Topic:Connection refused on socket 7 from 0xe8371eac
Goto Forum:
  


Current Time: Tue Oct 21 05:26:28 GMT 2014

Powered by FUDForum. Page generated in 0.02504 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software