issue saving assets in production cloud hosted instance
I keep getting the following error when saving an asset. This is the cloud-hosted instance managed by Hannon Hill.
An error occurred during editing: The transaction could not be completed: org.springframework.dao.CannotAcquireLockException: Hibernate operation: Could not execute JDBC batch update; SQL [insert into cxml_foldercontent (name, lockId, isCurrentVersion, versionDate, metadataId, permissionsId, workflowId, isWorkingCopy, parentFolderId, relativeOrder, cachePath, isRecycled, recycleRecordId, workflowComment, draftUserId, draftAssetFactoryId, siteId, prevVersionId, nextVersionId, originalCopyId, workingCopyId, displayName, title, summary, teaser, keywords, description, author, startDate, endDate, reviewDate, metadataSetId, expirationNoticeSent, firstExpirationWarningSent, secondExpirationWarningSent, expirationFolderId, maintainAbsoluteLinks, xmlId, structuredDataDefinitionId, pageConfigurationSetId, structuredDataId, pageStructuredDataVersion, shouldBeIndexed, shouldBePublished, lastDatePublished, lastPublishedBy, draftOriginalId, contentTypeId, assetType, id) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 'PAG', ?)]; Lock wait timeout exceeded; try restarting transaction; nested exception is java.sql.BatchUpdateException: Lock wait timeout exceeded; try restarting transaction
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Tim on 31 May, 2016 06:33 PM
Hi,
Thanks for the report. This is a known issue that we have implemented a fix for in Cascade 8. These particular messages are rare, but when they occur, they can cause temporary issues saving across the application (which is obviously no good). While the behavior should subside within minutes, I'll be happy to see if we can fix things more quickly for you by restarting the application. If you'd like for us to do so, just let me know and I can go ahead and do that.
I apologize for the inconvenience and I'll wait to hear from you.
Thanks
2 Posted by ediego on 02 Jun, 2016 01:55 PM
the issue seems to have resolves itself. thanks.
Now that you mention it, is there a planned release date for Cascade 8 ??
Support Staff 3 Posted by Tim on 02 Jun, 2016 01:58 PM
Glad to hear that things cleared up in your instance, Emil. There is no planned release date for Cascade 8, but we're really close to a beta release and we expect the final version to be made available shortly after that. The time frame will depend on the feedback we get during QA and beta testing.
Let me know if you need anything else.
Thanks!
4 Posted by ediego on 02 Jun, 2016 02:06 PM
ok, thanks. If you are looking for people to participate in the beta, please let me know. I'd love to participate in the QA process.
Support Staff 5 Posted by Tim on 02 Jun, 2016 05:34 PM
Sounds good, Emil! We'll definitely be looking for your feedback during beta testing. I imagine we'll put out some sort of announcement when it's available, so be on the lookout over the next several weeks.
Have a good one!
Tim closed this discussion on 02 Jun, 2016 05:34 PM.