Also, try the free, but I think a bit immature as yet, btrace (cf dtrace for Java) -- https://btrace.dev.java.net/ i think it matches what you're trying to do.
On Sat, Sep 13, 2008 at 6:06 PM, William Louth (JINSPIRED.COM) <[EMAIL PROTECTED]> wrote: > A product that supports this requirement in a production environment and > that has a 300+ technology specific aspectj extension libraries based on an > open API (not necessarily tied to aop) is JXInsight Diagnostics. > http://www.jinspired.com/products/jxinsight/new-in-5.1.html [Enhanced > JXInsight Diagnostics] > > http://www.jinspired.com/products/jxinsight/diagnostics.pdf > > Kind regards, > > William > > ------------------------------ > > Message: 1 > Date: Sat, 13 Sep 2008 09:15:23 +0000 (GMT) > From: Neo Anderson <[EMAIL PROTECTED]> > Subject: Re: [aspectj-users] debugging without stopping server > To: [email protected], [EMAIL PROTECTED] > Message-ID: <[EMAIL PROTECTED]> > Content-Type: text/plain; charset=utf-8 > > 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 > > _______________________________________________ > 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
