Home → Bug Reports →

Can't delete a destination

• Edit

bwmyers

16 Jul, 2012 06:18 PM

Maybe this isn't a bug, maybe I am not doing something right. Here is the issue:

When I go to delete a destination I get the following application error:

An error occurred during deletion: could not delete: [com.hannonhill.cascade.model.dom.Destination#90e5c7c8c0a8000b0149ee25208d5fc7]; nested exception is org.hibernate.exception.ConstraintViolationException: could not delete: [com.hannonhill.cascade.model.dom.Destination#90e5c7c8c0a8000b0149ee25208d5fc7]

See attached file. Any thoughts? Thanks, Bradley

• desterror.png 18.2 KB

1. Support Staff 1 Posted by Tim on 16 Jul, 2012 06:29 PM

   

   Hi Bradley,

   It looks like there may be something wrong with this particular Destination. Can you attach your tomcat\logs\cascade.log file to this discussion? It should hopefully contain more information regarding the error.

   Thanks

   • Edit

2. 2 Posted by bwmyers on 16 Jul, 2012 08:58 PM

   

   See attached for log. Our version number is: 7.0 - b56e8

   A bit of information about how I was able to generate this error:

   I have a mobile site built in jquery mobile that we are bundling into an app. Some of the features on the mobile web site need to be removed and a few features need to be added to the app that aren't part of the mobile site. That being said I copied the mobile site and then configured it using the mobile sites assets (blocks, xslt..etc). So what I have now is a TT.APP and TT.MOBILE site that are identical in structure and layout.

   On a side note I went in and was able to delete the Destinations for TT.MOBILE fine. This seems to be an issue with deleting copied site destinations.

   Appreciate your help. -Bradley

   • cascade.log 221 KB
   • Edit

3. 3 Posted by bwmyers on 16 Jul, 2012 09:15 PM

   

   Just found another issue, when I try to publish the site (2 total, one for live & one for testing). In this case I want to delete the live destination for the TT.APP and the staging destination for TT.MOBILE.

   I went in and disabled the live destination and tried to publish the TT.APP site to the staging server. I didn't get a successful publish message so I tried publishing it again and got a warning message saying the file is already set to be published. That was about a half hour ago and as of yet nothing has been published.

   • Edit

4. Support Staff 4 Posted by Tim on 17 Jul, 2012 01:58 PM

   

   Bradley,

   Thanks for attaching that log file. The problem is that when you are attempting to Delete the Destination it is causing a constraint violation in the database.

   I tried to reproduce the issue a few different ways:

   1) Copied a Site which had Destinations...then tried to delete the Destinations from the new Site (this worked as expected)
   2) Configured a Destination in 'site A' to publish on a schedule...copied 'siteA' to 'siteB'...attempted to remove the Destination from 'site B'. (this worked as expected as well)

   Can you tell me if the original Destination is set to be published on a schedule? If so, do you know if it happened to be publishing when you created the Copy of the Site?

   • Edit

5. 5 Posted by bwmyers on 17 Jul, 2012 04:32 PM

   

   No its not on a schedule.

   • Edit

6. Support Staff 6 Posted by Tim on 17 Jul, 2012 08:57 PM

   

   Hi Bradley,

   One of my developers was able to reproduce this issue by publishing a Site to multiple Destinations and - while the Site was being published - attempting to Delete one of those Destinations.

   I went in and disabled the live destination and tried to publish the TT.APP site to the staging server. I didn't get a successful publish message so I tried publishing it again and got a warning message saying the file is already set to be published. That was about a half hour ago and as of yet nothing has been published.

   Did anything get published yet? How are you currently determining whether or not assets were published? For example, are you refreshing your browser? Are you checking the actual time stamps of those files on the web server?

   If you still have not received a publish report for the publish that was triggered earlier, please attach your most recent cascade.log file and I'll be happy to look over it.

   Thanks

   • Edit

7. 7 Posted by bwmyers on 17 Jul, 2012 10:39 PM

   

   I am looking at the time stamp plus trying to publish the file again and it says "This asset has already been queued for publish."

   I could delete the site and start over but I already made a bunch of changes. Trying to keep from doing that but if its something that can't be fixed then I understand.

   I haven't received a publish message yet and the file still hasn't published. See the attached log file. I tried republishing the asset just before 3 az time.

   Thanks again for your help.

   • cascade.log 97.8 KB
   • Edit

8. Support Staff 8 Posted by Tim on 17 Jul, 2012 10:42 PM

   

   Hi Bradley,

   Thanks for attaching the latest log file. I see some messages like:

   2012-07-17 00:26:38,419 INFO  [LocalDataSourceJobStore] Handling 3 trigger(s) that missed their scheduled fire-time.
   2012-07-17 00:27:38,412 INFO  [LocalDataSourceJobStore] Handling 4 trigger(s) that missed their scheduled fire-time.
   2012-07-17 00:28:38,421 INFO  [LocalDataSourceJobStore] Handling 1 trigger(s) that missed their scheduled fire-time.
   2012-07-17 00:29:38,413 INFO  [LocalDataSourceJobStore] Handling 3 trigger(s) that missed their scheduled fire-time.
   2012-07-17 00:30:38,404 INFO  [LocalDataSourceJobStore] Handling 1 trigger(s) that missed their scheduled fire-time.
   

   that make me wonder if our 3rd party scheduling library (which triggers publish jobs) may be in a bad state. Can you try restarting Cascade Server when you have the chance and then let me know if you are able to publish that Site without error?

   • Edit

9. 9 Posted by bwmyers on 17 Jul, 2012 11:16 PM

   

   That seemed to fix it. You were correct in spotting the scheduled task but the task wasn't for the sites I mentioned. Different site, same server, different path/url. I don't know if that helps. When you asked I thought you were looking for any site specific tasks.

   After the restart I was able to successfully delete the destination.

   Thanks again for your help. Let me know if you need anything else to help with this issue. Might just have been a case of scheduling blues.

   -Bradley

   • Edit

10. Support Staff 10 Posted by Tim on 18 Jul, 2012 02:45 PM

    

    Ah, OK - great to hear! So, I think what happened was that the Destination was still being published as you were attempting to delete it (and the reason it took so long to publish - or actually never finish at all - is because the scheduling library happened to get into a bad state). Once you restarted, the scheduler was likely able to resume and this allowed for the jobs to be moved out of the publish queue (and for you to remove the Destination).

    Thanks for the upgrade Bradley! Have a great one.

    • Edit

11. Tim closed this discussion on 18 Jul, 2012 02:45 PM.