Yes, basically the feature I want is to capture the message/ error whilst system is still running. For instance, we have a legacy system based on rmi, which uses store procedure to perform insert, update, delete actions against database. The bitter problem I encountered is each time when there is an error, usually it only throws error like 'ORA-xxxx something goes wrong' with stack trace. Even I have source and can see exactly what lines the code are at when error occurred, nothing I can do to solve the problem because I do not know what parameters passed in whilst execution (logs sometime just do not help too much and we can not modify the source code; or sometimes it is urgent, but we still can not shutdown the server.) So if I am able to monitor the exactly value used whilst the system goes wrong, that definitively would help me a lot.
But due to I am new to AOP, the more document I read, the more confused I am. Originally I thought aspectj's load-time weaving is what I want. However, after reading some document, it seems like the load-time weaving is different from run-time/ online weaving (aspectwerkz) and dynamic AOP (JBoss AOP), which is the feature that aspectj does not support. So I switch to learn aspectwerkz. Interestingly, in the mailing list, I saw someone says that since the aspectj and aspectwerkz are merged. Users should use aspectj 5 instead of using aspectwerkz for such feature. I believe I might misunderstand something, but I can't distinguish based on my limited knowledge on AOP. Would you or anyone please to give me a bit more explain about this? I appreciate any help. Thank you very much. --- On Wed, 10/9/08, Andrew Eisenberg <[EMAIL PROTECTED]> wrote: > From: Andrew Eisenberg <[EMAIL PROTECTED]> > Subject: Re: [aspectj-users] debugging without stopping server > To: [EMAIL PROTECTED], [email protected] > Date: Wednesday, 10 September, 2008, 3:32 PM > Are you saying that you want to use AspectJ to monitor an > application > and notify you when there is a failure? You cannot use > AspectJ to > debug your application. You can, however, use AspectJ to > help gather > state about your application at the time of the failure. > > There is a first failure data capture (FFDC) pattern that > you can use. > http://blog.springsource.com/main/2008/01/07/capturing-failures-and-system-state-part-i/ > > As for adding aspects to an already running system on a > server > (without stopping it), that might be difficult depending on > the kind > of server that you are running. OSGi based servers are > built to allow > this kind of thing to happen. > > On Wed, Sep 10, 2008 at 2:01 AM, Neo Anderson > <[EMAIL PROTECTED]> wrote: > > Is it possible for aspectj to debug application or > project running on the server without stopping the service? > > > > For instance, suppose I have an application providing > service and the application also talks to the backend > database. Sometime it might throw error (not server crash), > but we can not stop it. I check the doc and it looks like > load-time weaving can be used for this purpose, but I have > no idea how to do that. Would anyone please provide senario > or any good tutorial/ example about this? > > > > Thanks in advice, > > > > > > > > _______________________________________________ > > aspectj-users mailing list > > [email protected] > > https://dev.eclipse.org/mailman/listinfo/aspectj-users > > _______________________________________________ aspectj-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/aspectj-users
