If you're using Transfer, then the problem is almost surely related to the classloader bug mentioned by James. Upgrading to the current version of the JVM (which I think is 1.6_u12) -- or for that matter, anything from 1/6_u10 on up -- should help tremendously.
If you upgrade the JVM, make sure you get the full JDK, not just the JRE, or it won't have what you need. And though CF7 installations are not generally affected by this, because by default CF7 runs with the older 1.5 JVM, if you have updated the JVM to an early (pre-update 10) version of 1.6, it will affect your CF7 installation, too. If you're not using Transfer, then this is not likely the cause. As many have pointed out, M-G and the other frameworks it's usually associated with load a ton of stuff on application startup, and that operation isn't quick. If you're using Reactor, as in Dan's case, the issue might occur if Reactor needs to regenerate all the database-related files it uses. Unlike Transfer, Reactor produces a bunch of cfcs for each table in its configuration anytime it thinks the tables have changed. (Or if it's configured to regenerate them.) The specific CFLOOP timeout you're seeing is something I used to run into a lot with M-G/ColdSpring/Transfer apps before the classloader bug was fixed. -- Thanks, Tom Tom McNeer MediumCool http://www.mediumcool.com 1735 Johnson Road NE Atlanta, GA 30306 404.589.0560 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "model-glue" 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/model-glue?hl=en For more about Model-Glue, check http://www.model-glue.com . -~----------~----~----~----~------~----~------~--~---
