Viewing a draft hangs
Asked by Charlie Davis:

In my Crucible instance, it seems every few hours I have to restart Crucible to resolve an issue.

It seems that after a review is created using FishEye smart commit, every once and awhile... it hangs maybe a thread or process in the background?

I can click around in FeCru just fine. View previous reviews, code changes, etc... but the new review is a Draft and when I try to view it, the web page "waits for response" infinitely.

This is the only error I get in the log

```
013-06-20 13:38:20,229 WARN  [qtp25337455-180 anager.updateDetails] fisheye HibernateUtil-withRetriableTransaction - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 5 more times
```


Answers:
author: Foong
body: Hi Charlie,

How many files are added to the review? Having too much files in the review will hung the review. Please use the workaround in this [KB](https://confluence.atlassian.com/display/FISHKB/Deleting+hung+reviews+manually) to delete the review and upgrade to FishEye/Crucible 2.10+ that have limit the number of files to 800.

comments: author: Charlie Davis
body: Hey Kah,

Sorry for the INCREDIBLY late response. :)

I'm currently having a review hang with one file. With a 4 character difference in XML.

I'm running FE/Crucible 3.1 as well.

SQL Database.

We currently wait for the hung reviews to "work" as we use smart commits but it'd be nice to figure out why they're hanging and if we can avoid it.


author: Charlie Davis
body: ```
2013-09-10 15:17:11,824 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 7 more times2013-09-10 15:17:19,825 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 7 more times2013-09-10 15:17:38,828 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 9 more times2013-09-10 15:18:02,831 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 6 more times2013-09-10 15:18:10,833 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 6 more times2013-09-10 15:18:29,835 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 8 more times2013-09-10 15:18:53,839 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 5 more times2013-09-10 15:19:01,840 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 5 more times2013-09-10 15:19:20,843 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 9 more times2013-09-10 15:19:44,847 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 7 more times2013-09-10 15:19:52,848 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 9 more times2013-09-10 15:20:11,851 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 4 more times2013-09-10 15:20:35,854 WARN  - Caught BatchUpdateException while executing:DefaultContentManager.updateDetails. Going to retry 4 more times
```


author: Piotr Swiecicki
body: Hi Charlie,

I'd like to help, would you consider raising this issue with Atlassian Support and provide thread dumps of JVM so we could inspect in detail? What database are you using, is it remote to FishEye server, is database server overloaded?

DefaultContentManager.updateDetails method should be very quick, there is relatively cheap DB interaction performed in there, so I can't see an obvious reason why it takes so long in your environment.

Kind regards,


author: Charlie Davis
body: Hey Kah,

Sorry for the INCREDIBLY late response. :)

I'm currently having a review hang with one file. With a 4 character difference in XML.

I'm running FE/Crucible 3.1 as well.

SQL Database.

We currently wait for the hung reviews to "work" as we use smart commits but it'd be nice to figure out why they're hanging and if we can avoid it.