Multiple people are reporting problems on the forum with JNDI lookups on the Hibernate service (HARs). In the logs the service appears to bind correctly, but then a JNDI lookup returns null, and in the debug logs the SessionFactoryObjectFactory lookup shows an empty container of session factories:

2005-05-27 18:59:57,104 DEBUG [org.hibernate.impl.SessionFactoryObjectFactory] JNDI lookup: hibernate/LocMasterFactory
2005-05-27 18:59:57,104 DEBUG [org.hibernate.impl.SessionFactoryObjectFactory] lookup: uid=ff808081042091fb01042095d4c20002
2005-05-27 18:59:57,104 WARN [org.hibernate.impl.SessionFactoryObjectFactory] Not found: ff808081042091fb01042095d4c20002
2005-05-27 19:05:29,763 DEBUG [org.hibernate.impl.SessionFactoryObjectFactory] {}

What's even stranger for me is that when I deploy a separate, single JSP to a different context it can resolve the session factory fine. At first I thought it was an issue with the classloading changes in 4.0.2 (for J2EE 1.4 compliance), but when I reverted those config changes it didn't fix the problem. It appears that there may be more than one instance of SessionFactoryObjectFactory in play.