Justice
unread,Sep 9, 2009, 8:45:31 AM9/9/09Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to ColdSpring-Users
I am working on some existing code that makes use of a coldspring
beanfactory to handle dependancies. The code gets called many
different ways, some remote methods called, some cfinvoke calls, and
some with createObject. The issue arises when many of these requests
do not share an application scope name (or an application scope at
all). I would like to have only a single instance of the beanfactory,
so I attempted to load it into the server scope.
Everything seemed fine until I was running some test requests using
jmeter, and I tried to run a reload of the beanfactory at the same
time. I have readOnly locks around my method that returns the
beanfactory from the server scope, and my re-init method wraps the re-
create code in an exclusive lock. I got a coldspring error that looks
like:
Cache error, myBean already exists in cache
Can anyone offer some advice on how to structure the create / init /
getBeanFactory code such that the coldspring cache would get cleared
out and the factory re-created in the server scope without causing
beanfactory requests to error out ?