Hi Charlie, Out of interest (while I await a hung server) I've configured FR 2.0.4 on my dev PC and run a couple of calls to the web service whilst I watch them in FR. I was alarmed to see that my single request was costing 32MB of memory (32,438KB)!!!! This snapshot was taken at about the 30th second (the whole request finished after 55s).
Here is the top part of the "Thread Stack Trace": Thread Stack Trace Trace Time: 15:26:34.224 08-Jan-2009 Request ID: 25 Script Name: http://foo Started: 15:26:04.177 08-Jan-2009 Exec Time: 30047ms Memory Used: (6%)32,438KB Memory Free: 472,457KB Thread ID: jrpp-8 Priority: 5 Hashcode: 30900283 "jrpp-8" prio=5 tid=0x03c5f468 nid=0x3c4 runnable [559d000..559fd90] at java.net.SocketInputStream.socketRead0(Native Method) at java.net.SocketInputStream.read(SocketInputStream.java:129) at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA12275) at com.sun.net.ssl.internal.ssl.InputRecord.a(DashoA12275) at com.sun.net.ssl.internal.ssl.InputRecord.read(DashoA12275) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275) - locked <0x158afd20> (a java.lang.Object) at com.sun.net.ssl.internal.ssl.SSLSocketImpl.a(DashoA12275) at com.sun.net.ssl.internal.ssl.AppInputStream.read(DashoA12275) - locked <0x158afc88> (a com.sun.net.ssl.internal.ssl.AppInputStream) at java.io.BufferedInputStream.read1(BufferedInputStream.java:220) at java.io.BufferedInputStream.read(BufferedInputStream.java:277) - locked <0x158afad8> (a java.io.BufferedInputStream) at java.io.FilterInputStream.read(FilterInputStream.java:111) at org.apache.xerces.impl.XMLEntityManager$RewindableInputStream.read (Unknown Source) Cheers Matthew On Jan 8, 12:33 pm, "charlie arehart" <charlie_li...@carehart.org> wrote: > No, you can't with FR get any sort of profile of what lines were slowest > within a request. Only the CF8 Server monitor has the depth of insight to > report that. What I had been referring to is if you can catch the request > WHILE it's running, in which case you can get a stack trace by clicking a > button to the left of the request, while you see it running. > > One other thing: you refer to my earlier suggestion as "browsing to the > WSDL", but to be clear, I wasn't proposing that (though not a bad idea). I > was proposing actually running the web service, by adding the method > attribute and passing in any needed simple arguments. But the fact that you > sometimes can't even get back the WSDL alone is certainly worrisome, and > something to bring to the attention of whoever runs the server being called. > This is just like how an end user would call any of us if our servers > weren't responding to their requests. :-) > > /charlie > > -----Original Message----- > From: cfaussie@googlegroups.com [mailto:cfaus...@googlegroups.com] On Behalf > > Of Matthew > Sent: Wednesday, January 07, 2009 8:04 PM > To: cfaussie > Subject: [cfaussie] Re: JRUN hanging > > I've got Fusion Reactor 2.0.0 (this is the only licence we have) up > and running and am looking at the "Request History". We've not had a > hang yet but I just wanted to get familiar with the tool. I'm looking > at the requests which are taking 45+ seconds and they are all pages > which involve a call to the web service. The pages are not timing out > so I'm not getting error logs showing where the timeout occured > however is there anyway to see which lines of code are the slow bits? > > I'm trying to work out if the call to the web service is the slow bit > or if it's the unpacking and trying to display the data which may be > slow. > > I'll report back what I'm seeing when the next hang happens. > > @Charlie: I've tried your idea of browsing to the WSDL while a hang is > occuring and I've had mixed scenerios. Sometimes it won't come up, > sometimes it comes up but when I try to submit to a method it times > out, sometimes it doesn't time out but it does take ages. > > Anyway, once I get the next hang I'll be able to report back on what I > see. > > Cheers > Matthew > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "cfaussie" group. To post to this group, send email to cfaussie@googlegroups.com To unsubscribe from this group, send email to cfaussie+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/cfaussie?hl=en -~----------~----~----~----~------~----~------~--~---
