Clusterware OC4J resource marked as OFFLINE

It seems like everybody knows that the localhost address is 127.0.0.1 if you are in IT, but what happens when Oracle does not remember that fact?  Well, you get what we had here in MOS article "ORA.OC4J Resource in Clusterware keeps going OFFLINE" via note ID 2025042.1 where you have to change configuration to hardcode the localhost address because it was not being resolved correctly and failing what looks like a heartbeat check.

R12: How can the TLD Cache prevent OC4J from starting?

When I opened up My Oracle Support document "OAFM OC4J is Not Starting. Error: "time out while waiting for a managed process to start"" from article ID 952583.1 I was looking to get something about the OC4J but instead I found out there is a TLD Cache and how to clear it!  Now to find out what the TLD Cache is, and what it is for!