Only reason I could think of is :
the name by which the jdbc resource is bound (jdbc/komodo_G3) is somehow overwritten by Hibernate or application.
There will be a jdbc-related-object bound to JNDI using the name jdbc/komodo_G3.
Somehow this is overwritten by Hibernate's SessionFactoryImpl in JNDI
with name "jdbc/komodo_G3".
Can you check whether you bind / use a JNDI name that is same
as the jdbc resource that is created ?
Can you change the jdbc-resource name, jdbc-resource-reference (if any) to a different name and see how it goes ?
[Message sent by forum member 'jr158900' (jr158900)]
http://forums.java.net/jive/thread.jspa?messageID=253755