On linux You could send the process a QUIT signal (kill -3 pid) which should produce a stack dump in your logs. If you do this when the problem pops up in production you can at least see what the process is doing. Do this several times in a row to get several dumps and then compare them. Sometimes this gives you a clue about where to look for problems, or a clue about how to cause the problem. Once you can successfully cause the problem, then you can at least think about a solution or a workaround.
Am Donnerstag, 5. Oktober 2006 21:38 schrieb Danny Gibbs: > Hi, > We are experiencing an issue with Magnolia locking up on us. We are > using Magnolia 3.0 RC3. The java process goes to 100% cpu, about once a > week or so. As a result, the website will not respond, and the server > needs to be restarted, which is not good. We don't think it is a > resource issue because we have plenty of ram and we are not receiving > any errors to indicate so. Do you have any hints as to how we can begin > to debug this issue? Since we are not getting any specific errors to > look at we are not sure where to look to figure out this issue. Is > anyone else experiencing this problem, or resolved a similar issue? > > > Thanks for your help, it is much appreciated! > > Danny ---------------------------------------------------------------- for list details see http://www.magnolia.info/en/magnolia/developer.html ----------------------------------------------------------------
