tracker issue : CF-3044024

select a category, or use search below
(searches all categories and all time range)
Title:

Bug 87099:-(Watson Migration Closure)This is one of the errors I recently got running a unit test on my ORM code

| View in Tracker

Status/Resolution/Reason: Closed/Won't Fix/

Reporter/Name(from Bugbase): Mary Jo Sminkey / Mary Jo Sminkey (Mary Jo Sminkey)

Created: 09/15/2011

Components: ORM Support

Versions: 9.0.1

Failure Type: Unspecified

Found In Build/Fixed In Build: 0000 /

Priority/Frequency: Trivial / Unknown

Locale/System: English / Platforms All

Vote Count: 0

Problem:

This is one of the errors I recently got running a unit test on my ORM code. It's extremely cryptic and makes no sense to a ColdFusion developer. These kinds of Hibernate errors are very common with the CF ORM implemenation, and really downgrade its capability as a RAD tool, as I have to first figure out what this error even means (usually searching Hibernate forums) and then try to figure out what in the CF code causes it. We really need more friendly error messages with the ORM to better know where we went wrong, right now it's a huge stumbling block to using ORM in ColdFusion. 
Method:

Just do something that will cause detached session or Hibernate cache issues or any of a myriad of ORM issues that cause CF to throw cryptic Hibernate errors. 
Result:

org.hibernate.cache.CacheException: java.lang.IllegalStateException: The org.hibernate.cache.UpdateTimestampsCache Cache is not alive.
- Collapse Stacktrace
Exception Type: org.hibernate.cache.CacheException | Message: java.lang.IllegalStateException: The org.hibernate.cache.UpdateTimestampsCache Cache is not alive. | Detail: | (error code: ) |

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3044024

External Customer Info:
External Company:  
External Customer Name: Mary Jo Sminkey
External Customer Email: 054227314463B683992015D5
External Test Config: 09/15/2011

Attachments:

Comments:

We cannot catch and wrap all Hibernate errors because that could confuse the user even more. But we have improved the error logging a lot in CF 9.0.1 and CF 10. That should solve most of the usability issues.
Comment by Himavanth R.
20934 | December 04, 2014 04:53:55 AM GMT