The metadata load does happen async in another thread, so getting struck seems like some kind of timing issue. Can you take thread dump in that case and provide us with that?
Unfortunately we do not have a thread dump, our customer only gave us the log files. We only know that some maintenance activity was being carried out on their database servers when this problem occurred.
Later when JBoss was restarted it came up successfully.
Assuming TEIID11010 occurs only when something is logically wrong and needs to be rectified manually,
we are evaluating a solution to programatically terminate jboss in case TEIID11010 occurs during metadata loading.
Is our approach recommended or is it a bad idea?
Terminating the EAP seems little harsh, but I do not know your case, how critical that. Ideally you want to figure out what the that ca.datacom.db.DBSQLException is why it is happening and why does it halt the EAP boot up? As I said, since it is async only that service needs to be in error state everything else *should* work. But apparently this is making whole VM suspended. So, I say more debugging is needed.