Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » Test and Performance Tools Platform (TPTP) » Profiling JBOSS problem
Profiling JBOSS problem [message #3298] Wed, 22 December 2004 02:59
Curtis d'Entremont is currently offline Curtis d'EntremontFriend
Messages: 42
Registered: July 2009
Continuation from this thread on

I believe the route you're taking will only get you statistical data about
the server. To profile your J2EE apps in the same way as J2SE apps, you
have to take a slightly longer route. Profiling applications running
inside application servers can be a little tricky in some ways - because
they usually all run in the same JVM, profiling one means profiling all of
them and also the server itself (unless you filter these out).

Here's what you need to do. Find out how to configure JBoss to add the
"-XrunpiAgent:server=enabled" JVM argument when it starts its JVM. I don't
know where this is, but I would start by looking for any server
configuration files. Once you've added this, start the server up again
(make sure the agent controller is running). This will cause the JVMPI
agent to register itself with the agent controller. Next you have to
attach to this agent in the workbench. This is done in the profiling
launch configuration dialog (Profile button on the main toolbar in the
Profiling and Logging perspective). Create a new Attach - Java Process and
enter the host where the server is running. Find the agent that
corresponds to your server (there'll probably only be one), set the
profiling options, and you should be all set to go.

Let me know if you run into any problems.



J2EE application running inside.


One quick clarification - were you trying to collect statistical data
about your JBoss server, or did you want to profile the J2EE applications
running inside it?



I tried to profile JBoss application but without success.
There is no problem with standard Java app, but launching JBoss profiling
(Trace Agent) terminates just after start without error.
The log of RAServer is below.
I tried also to start StatCon before - it works, shows some diagram, but  
effect of profiling is the same.
I played a little bit and changed the JMX JBoss port in profiling wizard
to something 'stupid' - the effect of starting Trace Agent is exactly the
same, also no error in log. Why?
I use version 3.2.0_20041217_2108.
Any advice?
Previous Topic:TPTP Mailing Lists and Newsgroups Transition
Next Topic:Starting profiling against Tomcat gives transport-error
Goto Forum:

Current Time: Fri Aug 19 20:48:44 GMT 2022

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

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

Back to the top