Commit timeout

When a code review contains many files, or large files, or both, committing the review within P4 Code Review can take some time. The default configuration, within the SWARM_ROOT/data/config.php file:

A configuration change only takes effect when the configuration cache has been reloaded. You must be an admin or super user to reload the P4 Code Review config cache. Navigate to the User id dropdown menu, select System Information, click the Cache Info tab, and click the System Information.

If changes to the config.php file might have caused the P4 Code Review web interface to become unresponsive, remove the problematic changes from the config.php file, then clear the configuration cache by running this command:
rm -f /opt/perforce/swarm/data/cache/module-config-cache.php

<?php
    // this block should be a peer of 'p4'
    'reviews' => array(
        'commit_timeout'  => 1800, // 30 minutes
    ),

The commit_timeout key is expressed in seconds. If a commit operation takes longer than this limit, it is terminated. It is likely that a terminated commit requires administrator intervention to complete the commit using another client.