Indirect exceptions

Aug 26, 2009 at 2:59 PM

I've also had the problem where MemCacheD blows up saying the provider's constructor threw an exception.  In my case, it turned out "localhost" was resolving to an IPv6 address on Windows Server 2008 by default instead of IPv4, so MemCacheD's socket API calls or the like didn't know what to do.

But my problem is: why do we get such an indirect exception?  I spent all day trying to decpher what was going wrong, but the exception itself provided no useful detail about the actual problem.  Is there a flaw in how the provider is reporting problems through exceptions?  Would it be possible to improve upon what it does now?