Maya, > HOORAY. > So the Jconnector was the problem. Don't use 3.1.13! > Thanks so much.
Glad to hear it. > I appreciate the suggestions, and I'll try them, but here's > why I think it is farcry: You just said it was fixed. Now you bring up a new problem saying the first problem wasn't fixed? Sorry if I seem confused here. > when I turn on debugging look at the results! ... Total CF > processiong time: 3453 ms (as compared to 140ms for non > farcry sites) Again, FarCry is not the issue here. Your new problem is because you turned on CF Debugging. CF debugging is unfortunately very poor at doing proper results (because it requires CF to process the results). That's why (as you stated earlier) the FarCry site runs much faster when you turned debugging off. Use any framework-based large application designed in CF and you'll get similar results when CF debugging is turned on. If you'd rather use a small application (such as your small sites you mentioned earlier) then CF debugging may be closer to correct results (but still not always accurate). If you need to run server monitoring on CF sites and want more accurate results it is suggested to run a program than runs in the underlying java layer. There are a few products out there such as SeeFusion (www.seefusion) and FusionReactor (www.fusion-reactor.com) that seem to do a pretty decent job. --- Jeff Coughlin Web Application Developer http://www.jeffcoughlin.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "farcry-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/farcry-dev -~----------~----~----~----~------~----~------~--~---
