Issue with link resolver if broker DB is inaccessible

Question

I am facing some fundamental issue with the Tridion "Link resolver" module; hopes I get some quick help from experts here. Please let me explain the problem statement. Platform we are using: SDL Tridion - 2011 SP1 DLL- “6.1.0.348” version of “Tridion.ContentDelivery.dll” Issue:
Link resolver functionality is working perfectly for my website but If in any case say the DB broker got inaccessible (via deadlock or other reason) then “tridion:ComponentLink " control throws an un-handled exception while resolving the link. Due to which the whole page got crash. Below are the snippets of my published page

Query: As this is Tridion default control hence we don’t have much control over it , what should we do to handle these type of exception?

Thanks

Answer 1

That's kind of expected behaviour.... Component linking works by looking up information about what pages components are used on and with what templates (for priority). This is done at the time of serving the link, as pages containing the required component may have been published or unpublished since the linking page was rendered. From the wording of your question I assume you are publishing your pages (as ASPX?) and binaries to a filesystem based storage and other data types to a database.

If your configuration is as mentioned above, then I suppose you could switch your storage configuration to use filesystem based storage for everything instead of the database... Then you wouldn't need a broker database at all. You'd need to measure the performance impact of making such a change and be aware that a database is mandatory if you want to publish taxonomies. This would also require a potentially significant amount of republishing!

As Nuno points out in the comments, Tridion's Content Delivery caching could also add value here (though only for those links to objects which have already been resolved and are thus in the cache). See the online documentation section about Content Delivery caching.