Some additional information on this:
While we do have pages outside the framework accessing models via APPLICATION.cbcontroller, these calls are not always the source of the error. Also, it is not consistent to the particular model, nor handler instantiating the model.
On Monday in the middle of the day, without any framework reinits, we started getting this dependency injection error:
The DSL Definition {JAVACAST={null},NAME={QuickBooksDAO},ARGNAME={},DSL={id:id:model.setup.QuickBooksDAO},VALUE={null},REQUIRED={false},SCOPE={variables},REF={null}} did not produce any resulting dependency
The error on Monday was on a coldbox page, and not being called via APPLICATION.cbController. This error would occur every time the user tried to access that page, as if the bad dependency was cached. Our process when this happens is to take that server out of our load balancer, reinit coldbox, and put it back in (hoping we don't get another dependency injection error). Our application is pretty much under steady load all day, so there wouldn't have been an application timeout (our timeout is set to 1 day in application.cfc)
I was able to somewhat reproduce the error using a jmeter load test, but not exactly. While I do get some dependency injection errors while reiniting during the load test, they don't persist, and the DSL does not have the double id:id:model...
Any more ideas?
~James