On Jan 21, 2006, at 7:06 PM, Nathan Bubna wrote:
you're right. that's really bizarre. if it were breaking after 42 servlet mappings, i would just blame it on Douglas Adams :), but at 43, i haven't a clue. is there anything happening in your logs? file handle issues? memory issues?
Doh. I stepped through the Velocity source and all was revealed. There was another servlet with <load-on-startup> set in web.xml.
Under the magic number, Tomcat was loading my initialization servlet first, and its custom loadConfiguration() properties were used when RuntimeInstance.init() was called for the first time. Above the magic number, Tomcat was loading my initialization servlet second, so RuntimeInstance.init() had already run once without the custom loadConfiguration() properties.
Operator error. Thanks for all the responses. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
