Thanks for the push

I will be commuting something this afternoon

Any word on when this will be patched in? What makes this a critical issue is that the preReinit interceptions in any code base will no longer fire because the error occurs before that interception is announced. The next request, even with a reinit, will not fire those interceptions, because it goes through the Bootstrap ( since the framework is in an incomplete state ).

In short this is turning out to be a bigger issue than I thought it was, because Java singletons are being orphaned and shutdown routines are not firing.

After checking the lucee code, they don’t use synchronized maps either. So moving to an ordered struct via structNew( 'ordered' ) is the same. So my only choice is to synchronize the map

It wasn’t for the performance gain, it was to have a linked struct which didn’t exist in cfml. It has to be a an ordered map. NOw, I can synchronize it, or use the CFML native ordered struct, but I am not sure if lucee uses a synchronized struct.

This is because the struct that stores the interceptors internally is a Java instance of java.util.LinkedHashMap

And a LinkedHashMap is NOT threadsafe per the javadocs:

ColdBox needs to stop using un-synchronized Java classes. I would recommend ColdBox just start using a plain old CFML struct. Whatever performance gains Luis was getting back in the very very early days of ColdBox are likely to not exist any longer.