Only other thing that immediately comes to mind is that it looks like that may be a network drive so perhaps something's going on on that network device or the network itself.
If the directory should pretty much always exist, I'd run that code in your onApplicationStart() or find another way to only check it when the application first starts up. That way it's only running once. Fewer of these errors, and touching the filesystem less often is always a good thing for performance. -Cameron On Wed, Dec 7, 2011 at 12:12 PM, Shannon Rhodes <[email protected]>wrote: > Very unlikely, the directory definitely exists, since it's our main > repository for documents...we aren't creating it all the time, it's just a > best practice that we're checking for existence. > > >Could this same code be run concurrently by two threads/users? One thread > >could be int he process of creating the Dir when another does it's > >dirExists() check. You may want to toss a named lock around it to make > >sure only one process is messing with the directory at once. I'd use > >hash(dirpath) as the name of the lock to make it a clean unique URL with > no > >special characters.. > > > >-Cameron > > > >On Tue, Dec 6, 2011 at 4:56 PM, Shannon Rhodes <[email protected] > >wrote: > > > >> > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:348998 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
