> > > ><<<>>> if at the end of it > > i find its a bug in JRun or the JRE then haven't i been doing someone > > elses job for them? > > There is no guarantee that this is caused by a bug outside of your > application. > Besides the "not my job" phase is never the answer you want to give to your > boss.
lol, yes, i only use that phrase when someone suggests i make a cup of tea or walk the dogs. The reason i suspect its a problem outside my code is the variety of spurious errors that are reported, which suggests to me that JRun is getting it knickers in a twist, and then failing on random pages. I can't think of any other reason why a request to index.cfm?something=123 will succeed with no problems, then, when the server is about to go down, it fails, but only for some requests. If the table or dB were locked then it woulod fail for all requests. In fact, if something "logical" were happening then it woud fail for all subsequent requests. But in the space of a few minutes it will succeed for some and fail for otheres. Then the service restarts itself. > > > Isn't there any other kind of logging, i could try? > > There is logging of CF, JRun, Garbage Collection, Web Server Connector, etc... > There is logging all over the place. The problem is, some of them log so much > information it can be overwhelming. yep, thats where we are now, logging everything we can find, and getting a little bogged down. (i cracked a joke in a stability meeting the other day about not being able to see the wood for the logs - didn't fix the servers but it lightened the mood :) The CF logging i can handle, normally, but in this case its either "lying", of giving NULL pointer exceptions with an empty stack trace. We dump out a load of stuff to the cfusion-out.log (using -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintHeapAtGC in the JVM.config) but i'm struggling to make much sense out of it: i don't know what "normal" or "unhappy" look like. Anyone know of a dummys guide to reading that sort of stuff, or interested in casting an eye over what i'm getting? And when you mention JRun logging, we're doing the metrics (see earlier post for a couple of lines of that). Is there any other JRun logging we could/should be doing? >Therefore, you should narrow your search > down first. I'm looking everywhere i can think of - narrowing down the search is what i'd really really like to do, but once i move away from the cf logs and into the java ones i get kind of lost.. > > Not that your app has this problem, but I've seen bad code that puts a system > in deadlock before. See the "Nesting Locks and Avoiding Deadlocks" section of > this livedoc and double check your app: > http://livedocs.macromedia.com/coldfusion/5.0/Developing_ColdFusion_Applications/appFramework10.htm > Should be pretty safe with locking: the application start up is in a couple of cfifs with an exclusive lock inbetween, all cfx_tag calls are cflocked with an exclusive named lock, and just about all the obsolete locks left over from cf5 have been removed. Cheers Bert ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Find out how CFTicket can increase your company's customer support efficiency by 100% http://www.houseoffusion.com/banners/view.cfm?bannerid=49 Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5096 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
