[ http://jira.jboss.com/jira/browse/JBIDE-1196?page=comments#action_12384889 ] Max Andersen commented on JBIDE-1196: ------------------------------------- Well the reason is that persistence.xml for ears contains: <property name="hibernate.cache.use_query_cache" value="true"/> Any idea why that is actually enabled by default ?! -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1196?page=comments#action_12384977 ] Gavin King commented on JBIDE-1196: ----------------------------------- Well, OK, I will remove that line. But it still does not explain the exception to me... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBIDE-1196?page=comments#action_12384992 ] Max Andersen commented on JBIDE-1196: ------------------------------------- there are no second level cache provider selected so it fallsback to the NoCacheBlaBlahProvider which pukes if any caching becomes enabled - including this flag which forces initialization of the query cache updatetimestampcache to bb ready in case you do query.setCachable(true); I guess inside jbossas caching is automatically setup if you are running JPA since there they enable jbosscache AFAIK. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira