Home » Archived » Test and Performance Tools Platform (TPTP) » Profiling Jboss 4.0.3SP1 with TPTP 4.4 from europe build
| Profiling Jboss 4.0.3SP1 with TPTP 4.4 from europe build [message #103842] |
Mon, 09 July 2007 16:26  |
Eclipse User |
|
|
|
Originally posted by: Thomas.Wiesner.ebcot.de
Hello,
i've different problems to profile our application in described jboss
environment with jdk 1.5.0_11 and 1.5.0_12 (both from sun). i've tried
both, starting (profile) jboss with a serverdefinition in WTP and attaching
to a installed agentcontroller.
Machine 1 (Linux 2.6.18.8-0.1-default, intel core duo, 2GB RAM):
First jboss profiling within WTP doesn't start appserver successfully. I've
to kill the process in background.
Second starting the appserver with agentcontroller (server=enabled) seems to
be ok, but if i start to attach to the agent from eclipse 3.3 the appserver
hangs after a few minutes without any errors or exceptions. So i didn't
reach the interessting part of my application for profiling. It doesn't
matter if i switch the agentcontroller to server=standalone and filter the
only interessting packages.
Machine 2 (Linux 2.6.16.21-0.8-smp, intel quad core 64bit, 4GB RAM):
On this machine the jvm crashes directly at the beginning of starting the
jboss.
Any ideas to profile my application with TPTP in jboss on one of those
machines ?
Thanks in advance,
Thomas
#
# An unexpected error has been detected by HotSpot Virtual Machine:
#
# SIGSEGV (0xb) at pc=0x00002aaaaf3c5bd9, pid=9136, tid=1098389824
#
# Java VM: Java HotSpot(TM) 64-Bit Server VM (1.5.0_12-b04 mixed mode)
# Problematic frame:
# J java.util.Properties$LineReader.readLine()I
#
--------------- T H R E A D ---------------
Current thread (0x00002aaad81d9260): JavaThread "main" [_thread_in_Java,
id=9151]
siginfo:si_signo=11, si_errno=0, si_code=1, si_addr=0x00002aaa89883000
[...]
Stack: [0x0000000041681000,0x0000000041782000), sp=0x0000000041780370,
free space=1020k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native
code)
J java.util.Properties$LineReader.readLine()I
[error occurred during error reporting, step 120, id 0xb]
--------------- P R O C E S S ---------------
Java Threads: ( => current thread )
0x00002aaad81e27e0 JavaThread "DestroyJavaVM" [_thread_blocked, id=9136]
=>0x00002aaad81d9260 JavaThread "main" [_thread_in_Java, id=9151]
0x00002aaad80f6920 JavaThread "Low Memory Detector" daemon
[_thread_blocked, id=9149]
0x00002aaad80f7d10 JavaThread "CompilerThread1" daemon [_thread_blocked,
id=9148]
0x00002aaad80954d0 JavaThread "CompilerThread0" daemon [_thread_blocked,
id=9147]
0x00002aaad7ffc000 JavaThread "AdapterThread" daemon [_thread_blocked,
id=9146]
0x00002aaad8096730 JavaThread "Signal Dispatcher" daemon [_thread_blocked,
id=9145]
0x00002aaad7c41b60 JavaThread "Finalizer" daemon [_thread_in_native,
id=9144]
0x00002aaad7c772d0 JavaThread "Reference Handler" daemon
[_thread_in_native, id=9143]
Other Threads:
0x00002aaad7ce78f0 VMThread [id=9142]
0x00002aaad80f2490 WatcherThread [id=9150]
VM state:not at safepoint (normal execution)
VM Mutex/Monitor currently owned by a thread: None
Heap
PSYoungGen total 76480K, used 3936K [0x00002aaaccd90000,
0x00002aaad22e0000, 0x00002aaad7830000)
eden space 65600K, 6% used
[0x00002aaaccd90000,0x00002aaacd1680f0,0x00002aaad0da0000)
from space 10880K, 0% used
[0x00002aaad1840000,0x00002aaad1840000,0x00002aaad22e0000)
to space 10880K, 0% used
[0x00002aaad0da0000,0x00002aaad0da0000,0x00002aaad1840000)
PSOldGen total 174784K, used 0K [0x00002aaab7830000,
0x00002aaac22e0000, 0x00002aaaccd90000)
object space 174784K, 0% used
[0x00002aaab7830000,0x00002aaab7830000,0x00002aaac22e0000)
PSPermGen total 21248K, used 2999K [0x00002aaab2430000,
0x00002aaab38f0000, 0x00002aaab7830000)
object space 21248K, 14% used
[0x00002aaab2430000,0x00002aaab271dc50,0x00002aaab38f0000)
Dynamic libraries:
40000000-4000e000 r-xp 00000000 09:01
1167379 /usr/local/jdk1.5.0_12/bin/java
4010d000-40110000 rwxp 0000d000 09:01
1167379 /usr/local/jdk1.5.0_12/bin/java
40110000-40173000 rwxp 40110000 00:00 0
[...]
92268 /srv/appserver/jboss-4.0.3SP1/client/getopt.jar
2aaaaaad4000-2aaaaaade000 r-xp 00000000 09:01
1198609 /srv/agent-controller/plugins/org.eclipse.tptp.javaprofiler/ libHeapAdaptor.so
2aaaaaade000-2aaaaabdd000 ---p 0000a000 09:01
1198609 /srv/agent-controller/plugins/org.eclipse.tptp.javaprofiler/ libHeapAdaptor.so
2aaaaabdd000-2aaaaabde000 rwxp 00009000 09:01
1198609 /srv/agent-controller/plugins/org.eclipse.tptp.javaprofiler/ libHeapAdaptor.so
2aaaaabde000-2aaaaac54000 r-xp 00000000 09:01
1198613 /srv/agent-controller/plugins/org.eclipse.tptp.javaprofiler/ libJIE.so
2aaaaac54000-2aaaaad54000 ---p 00076000 09:01
1198613 /srv/agent-controller/plugins/org.eclipse.tptp.javaprofiler/ libJIE.so
2aaaaad54000-2aaaaad5a000 rwxp 00076000 09:01
1198613 /srv/agent-controller/plugins/org.eclipse.tptp.javaprofiler/ libJIE.so
[...]
[stack]
ffffffffff600000-ffffffffffe00000 ---p 00000000 00:00 0
[vdso]
VM Arguments:
jvm_args: -Xms256m -Xmx512m -Xss1024k -agentlib:JPIBootLoader=JPIAgent:server=enabled;HeapProf -Dlisa.appserver.vendor=jboss -Dlisa.appserver.url=localhost:1999 -Dprogram.name=lisa-4_3-profile.sh -Djava.endorsed.dirs=/srv/appserver/jboss-4.0.3SP1/lib/endor sed
java_command: org.jboss.Main
Launcher Type: SUN_STANDARD
Environment Variables:
JAVA_HOME=/usr/local/jdk1.5.0_12
JRE_HOME=/usr/lib/jvm/java/jre
PATH=/sbin:/usr/sbin:/usr/local/sbin:/opt/gnome/sbin:/root/b in:/usr/local/bin:/usr/bin:/usr/X11R6/bin:/bin:/usr/games:/o pt/gnome/bin:/usr/lib/mit/bin:/usr/lib/mit/sbin
LD_LIBRARY_PATH=/usr/local/jdk1.5.0_12/jre/lib/amd64/server: /usr/local/jdk1.5.0_12/jre/lib/amd64:/usr/local/jdk1.5.0_12/ jre/../lib/amd64::/srv/agent-controller/plugins/org.eclipse. tptp.javaprofiler:/srv/agent-controller/lib
SHELL=/bin/bash
HOSTTYPE=x86_64
OSTYPE=linux
MACHTYPE=x86_64-suse-linux
Signal Handlers:
SIGSEGV: [libjvm.so+0x661c00], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGBUS: [libjvm.so+0x661c00], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGFPE: [libjvm.so+0x568b50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGPIPE: [libjvm.so+0x568b50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGILL: [libjvm.so+0x568b50], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGUSR1: SIG_DFL, sa_mask[0]=0x00000000, sa_flags=0x00000000
SIGUSR2: [libjvm.so+0x56aa00], sa_mask[0]=0x00000000, sa_flags=0x14000004
SIGHUP: [libjvm.so+0x56a4d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGINT: [libjvm.so+0x56a4d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGQUIT: [libjvm.so+0x56a4d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
SIGTERM: [libjvm.so+0x56a4d0], sa_mask[0]=0x7ffbfeff, sa_flags=0x14000004
--------------- S Y S T E M ---------------
OS:SUSE Linux Enterprise Server 10 (x86_64)
VERSION = 10
uname:Linux 2.6.16.21-0.8-smp #1 SMP Mon Jul 3 18:25:39 UTC 2006 x86_64
libc:glibc 2.4 NPTL 2.4
rlimit: STACK 8192k, CORE 0k, NPROC 49152, NOFILE 1024, AS infinity
load average:0.11 0.19 0.30
CPU:total 4 em64t ht
Memory: 4k page, physical 4031312k(781340k free), swap 2072056k(2071912k
free)
vm_info: Java HotSpot(TM) 64-Bit Server VM (1.5.0_12-b04) for linux-amd64,
built on May 2 2007 01:49:59 by java_re with gcc 3.2.2 (SuSE Linux)
|
|
| |
| Re: Profiling Jboss 4.0.3SP1 with TPTP 4.4 from europe build [message #103980 is a reply to message #103901] |
Tue, 10 July 2007 09:26  |
| Eclipse User |
|
|
|
Originally posted by: Thomas.Wiesner.ebcot.de
Hi Asaf,
Asaf Yaffe wrote:
> Thomas,
>
>>
>> Second starting the appserver with agentcontroller (server=enabled) seems
>> to be ok, but if i start to attach to the agent from eclipse 3.3 the
>> appserver hangs after a few minutes without any errors or exceptions. So
>> i didn't reach the interessting part of my application for profiling. It
>> doesn't matter if i switch the agentcontroller to server=standalone and
>> filter the only interessting packages.
>
> When running in "standalone" mode, is a file named trace.trcxml file
> created in the working directory (probably the JBoss directory)? Does it
> keep growing? Any data in there? Note that you can specify the trace
> output file name by using the "file=" argument
>
(-agentlib:JPIBootLoader=JPIAgent:server=standalone,file=/tm p/trace.trcxml;HeapProf
> ...)
In "standalone" mode the file is created, but from the moment the jboss is
stucking the trace file doesn't grow. In each test run it grows to a size
of nearly 300 megs.
Any ideas ?
Thanks Thomas
> Thanks,
> Asaf
>
|
|
| |
Goto Forum:
Current Time: Fri Apr 19 00:03:37 GMT 2024
Powered by FUDForum. Page generated in 0.01369 seconds |
] 
Search
Help
Register
Login
Home
