[jbosstools-dev] Question on ASTools profiling

[Snjezana Peco]

On 11/7/2013 1:15 PM, Max Rydahl Andersen wrote:
> On Thu, Nov 07, 2013 at 01:06:42AM +0100, Snjezana Peco wrote:
>> We have used Eclipse TPTP project (see http://www.eclipse.org/tptp/) to
>> profile a JBoss AS server. Now the project is archived
>> (http://www.eclipse.org/tptp/home/project_info/devplans/EclipseTPTPProjectPlan2010.htm). 
>>
>>
>> Google has announced the RAT project that should replace TPTP
>> (http://www.eclipse.org/proposals/tools.rat/ &
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=375133).
>
> Don't think that was related to Google - all listed on it is from 
> OnPositive Technologies.
>

The RAT project had to be based on the Instantations CodePro AnalytiX 
(https://developers.google.com/java-dev-tools/download-codepro).
Google's intention  was to donate the project. OnPositive Technologies 
intended to offer commercial support.
Nothing happened.
See
http://googlecode.blogspot.com/2010/12/windowbuilder-becomes-new-open-source.html

>> The project has never been started.
>>
>> What we can do is the following:
>>
>> - try to integrate Java VisualVM or Jubula
>> - remove profiling code from JBT
>
>> I will check if it is possible to integrate Java VisualVM or Jubula.
>
> We need to seperate a few things here first.
>
> 1. What is needed to enable use of Eclipse Profile mode against our 
> servers.
> 2. What specific ones that could be made to utilize #1.
>
> IMO #2 is *not* a requirement for us to do - it can/should be possible 
> to do for
> others than us. It should be possible to enable by any profiler you 
> have isntalled in eclipse.
>
> For #1 I believe the server adapter simply just need to state it 
> supports profiling
> and allow that Profiler plugins will hook into the normal launch 
> configuration phase.
>
> Isn't that how Yourkit and other profilers hook into eclipse launches 
> without having the launchers
> knowing about the specific profiler?
>
> And that is why the WTP call 
> ServerProfilerDelegate.configureProfilling is needed.
>
> To allow *any* Profiler to enable it by modifiying the standard javavm 
> launch flags (like -agent) to
> enable their profiler.
>

Right. WTP enables us to add profile mode.
Not sure whether some open source profiling tool now implements it. TPTP 
was doing it before for WTP servers; we added support for JBoss Tools 
servers.
In my opinion, it would be good to add this feature again.

Snjeza

> /max
>
>> Snjeza
>>
>> On 11/6/2013 3:43 PM, Rob Stryker wrote:
>>> This is mostly a question for Snjezana, but anyone else who knows feel
>>> free to chime in:
>>>
>>> I noticed in AbstractJBossStartLaunchConfiguration is the following
>>> block of code:
>>>
>>>         if (ILaunchManager.PROFILE_MODE.equals(mode)) {
>>>             try {
>>> ServerProfilerDelegate.configureProfiling(launch, vm,
>>> runConfig, monitor);
>>>
>>> I'm attempting the beginnings of trying to refactor a lot of the
>>> ASTools launching behavior, and I need to know what kind of changes
>>> these profile delegates will make to the launch. I'm not sure I have
>>> the proper environment up, but, if you could tell me how to test it
>>> and use it, I'd be super grateful.
>>>
>>> It's always a bit dangerous when touching or moving code that you're
>>> not familiar with how it works.
>>>
>>> This block of code is also a bit inconvenient since it happens after
>>> 95% of the launch code but before the vmrunner.run(etc), so it
>>> requires us to basically copy a superclass's entire 300 line method in
>>> order to sneak the profiling bit in before the launch is run.
>>>
>>> Anyway, any advice on how this works, what kinda changes it can make
>>> to the launch, or how to set up my env to test it, would be very 
>>> helpful.
>>>
>>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev