My target is a LTW profiler. In most cases, there are no Aspects in the
Application. The aspects added or removed are the Aspects of the profiler.
But are there potential problems by LTW weaving an compiled time woven
Application ?
Use cases i think :
- active /de-active / modifying the level trace without stopping application
- construct a profiler with heuristic algorithm to detect class/method that
have long duration (in test plateforms)
But if I understand your explanations, for the classes loaded at the start
of the application (or with a JVM option Xnoclassgc), or those that are
never unloaded, the weaving is not possible after re-activing the agent LTW.
Cordialement / Best regards
Jean-Louis Pasturel
_____
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] De la part de Andy Clement
Envoyé : mercredi 15 octobre 2008 20:10
À : aspectj-users@eclipse.org
Objet : Re: [aspectj-users] Activing / de-activing aspectjweaver
agentwithout stopping the JVM
So you want to change what is going to be woven without getting rid of the
classloader (which would cause the lt weaver to be discarded).
I vaguely recall something like this being discussed a long time ago.
Adding new aspects does not seem unreasonable, but it will only
affect classes loaded after the reinitialize. Removing aspects, well you'd
need to be careful and sure that classes loaded post-initialize
won't have problems working with classes loaded earlier that had been woven.
Feel free to open an enhancement request but I'd need to see some good use
cases before adding the capability. I would hate to
get in lots of bug reports because this feature had been used incorrectly...
Andy.
2008/10/15 <[EMAIL PROTECTED]>
Hi all,
Activing / de-activing aspectjweaver LTW agent without stopping the JVM ?
A similar question, but not exactly the same, was asked few days ago.
It seems it is not possible today with the version 1.6.x of Aspectj.
Does the modification of the agent would be heavy to have the features
described below:
- stopping agent aspectjweaver by sending a signal on the pid of the java
process and catching it ( we can do it, for example with the
non-documented classes sun
)
- modifying the aop.xml file configuration ( scope of the concrete aspects,
add new aspects
)
- starting the agent with the new aop.xml by sending the same signal or
another
See JIProf profiler project. It does the start and stop for its agent
(http://sourceforge.net/projects/jiprof/)
Does it only a dream ? ;-)
Cordialement / Best regards
Jean-Louis Pasturel
<mailto:[EMAIL PROTECTED]>
[EMAIL PROTECTED]
*********************************
This message and any attachments (the "message") are confidential and
intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed
or falsified.
If you are not the intended addressee of this message, please cancel it
immediately and inform the sender.
********************************
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users
*********************************
This message and any attachments (the "message") are confidential and intended
solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or
falsified.
If you are not the intended addressee of this message, please cancel it
immediately and inform the sender.
********************************
_______________________________________________
aspectj-users mailing list
aspectj-users@eclipse.org
https://dev.eclipse.org/mailman/listinfo/aspectj-users
