Home → Bug Reports →

Hibernate transaction error

• Edit

lauren.fraser

13 Nov, 2013 02:52 PM

An error occurred during creation: Could not roll back Hibernate transaction; nested exception is org.hibernate.TransactionException: JDBC rollback failed

I'm getting this error when I try to upload an image file.

I'm also getting some publishing errors.When I try to open the publishing report I get this message:
Nov 13, 2013 8:52 AM
An error occurred: Could not roll back Hibernate transaction; nested exception is org.hibernate.TransactionException: JDBC rollback failed
You may choose to retry the operation. If the problem persists, please contact a system administrator.
The error has been logged to the system console.

1. Support Staff 1 Posted by Tim on 13 Nov, 2013 03:20 PM

   

   Hi Lauren,

   Can you please attach your cascade.log file from today? You can find log files in the application under Administration -> Dashboard -> Logs (if you are an administrator) - or - on the application server itself in the tomcat/logs directory.

   Thanks!

   • Edit

2. 2 Posted by lauren.fraser on 13 Nov, 2013 03:21 PM

   

   Tim,
   here is our log from today.

   • cascade__7_.log 688 Bytes
   • Edit

3. Support Staff 3 Posted by Tim on 13 Nov, 2013 03:33 PM

   

   Thanks! OK, the issues you are running into appear to be due to a disk space problem either on your application server or your database server:
   

   2013-11-13 00:00:05,528 ERROR [JDBCExceptionReporter] I/O Error: There is not enough space on the disk
   

   Can you check both and let me know what you find?
   • Edit

4. 4 Posted by lauren.fraser on 14 Nov, 2013 03:32 PM

   

   Tim,

   One of our network admins said the C drive was out of space and he made some room. It looks like our publish issues are resolved and the Hibernate error is gone for now. Thanks!

   • Edit

5. Support Staff 5 Posted by Tim on 14 Nov, 2013 03:32 PM

   

   Perfect. Thanks for the update, Lauren! Have a good one.

   • Edit

6. Tim closed this discussion on 14 Nov, 2013 03:32 PM.

7. lauren.fraser re-opened this discussion on 15 Nov, 2013 05:24 PM

8. 6 Posted by lauren.fraser on 15 Nov, 2013 05:25 PM

   

   We're getting the same error again today. One of our network admins looked at the servers and had this to say:

   The log file located at C:\Program Files\Cascade Server\tomcat\logs\cascade-stdout.2013-09-20.log

   Seems to be what is taking all of the disk space. It is currently over 5gb and was under that yesterday when I was doing cleanup. Can you update your issue with that and see what we can do with that file?

   • Edit

9. Support Staff 7 Posted by Tim on 15 Nov, 2013 05:29 PM

   

   Hi Lauren,

   Feel free to remove that file (along with any other file in the tomcat/logs directory). A new log file is generated every day so there's no need to have log files that old unless you all need them for record-keeping purposes (although there isn't much in there that is useful for auditing purposes).

   Let me know if you or your sysadmin have any further questions regarding the log files.

   Thanks

   • Edit

10. 8 Posted by lauren.fraser on 05 Dec, 2013 01:54 PM

    

    Tim,
    We were getting the same error that I copied above. Our network admin deleted some log files and we were able to get the error to go away. Here is what he had to say about it:
    "I have deleted the log files again and you should be good to go. Can you issue this w/ support? We are generating a 250mb log file everyday and there is one other that seems to grow out of control to 5gb. That seems like an awful lot of logging. Maybe we can turn something off that is logging that we don’t need? We will have to clear space every 2 weeks the way it is now as we only have 10gb available on the drive."

    Is there any logging that we could turn off. Or any other recommendations you can make?

    • Edit

11. Support Staff 9 Posted by Tim on 05 Dec, 2013 03:00 PM

    

    Hi Lauren,

    250MB log files are definitely not normal and would generally indicate that some sort of problem is repeatedly being reported. The next time one of these larger log files is generated, can you send it to our SFTP server so that I can look over it? That way I can help you all track down what is causing the log files to grow so quickly in size.

    Our SFTP server connection info:

    host: drop.hannonhill.com
    username: transfer
    password: f1l3$4HH
    directory: files

    If you would prefer to place the log file some place where we can download it that would be fine as well.

    Let me know.

    Thanks!

    • Edit

12. 10 Posted by lauren.fraser on 27 Dec, 2013 09:01 PM

    

    Tim,

    Here is what my network admin just sent me:

    The file is currently uploading to drop.hannonhill.com/files

    It is named cascade.log.2013-12-26-citizensMemorial

    It is from yesterday and about half the size we were seeing, but still very large.

    • Edit

13. Support Staff 11 Posted by Tim on 31 Dec, 2013 02:28 PM

    

    Hi Lauren,

    Thanks for sending over that log file. It looks like you are running into this error repeatedly:
    

    Caused by: java.sql.SQLException: The DELETE statement conflicted with the REFERENCE constraint "FK_ASSETSTATS_ASSET". The conflict occurred in database "cascade_default", table "dbo.cxml_assetstats", column 'assetId'.
    

    This is an issue that should be corrected in 7.8. Can you confirm that you are running something prior to that? If you are, I would recommend upgrading to the latest version of the application as soon as possible and that should take care of the issue.

    The underlying problem doesn't affect functionality in the system. The main issue here is that it is causing a message to appear thousands of times in your log files as you all have noticed.

    Let me know if you have any further questions!

    Thanks

    • Edit

14. 12 Posted by lauren.fraser on 31 Dec, 2013 02:43 PM

    

    Tim,

    Thanks. We’re on 7.6 I’ll see if we can upgrade sooner rather than later.

    Thanks,

    Lauren

    • Edit

15. Support Staff 13 Posted by Tim on 31 Dec, 2013 02:46 PM

    

    OK, sounds good Lauren! I'll close the discussion for now, but don't hesitate to comment back if you still have problems with the log files after applying the upgrade.

    Take care.

    • Edit

16. Tim closed this discussion on 31 Dec, 2013 02:46 PM.