Chris@0: <?php
Chris@0: 
Chris@0: namespace Drupal\Tests\dblog\Functional;
Chris@0: 
Chris@0: use Drupal\Core\Database\Database;
Chris@0: use Drupal\Tests\BrowserTestBase;
Chris@0: 
Chris@0: /**
Chris@0:  * Tests logging of connection failures.
Chris@0:  *
Chris@0:  * @group dblog
Chris@0:  */
Chris@0: class ConnectionFailureTest extends BrowserTestBase {
Chris@0: 
Chris@0:   public static $modules = ['dblog'];
Chris@0: 
Chris@0:   /**
Chris@0:    * Tests logging of connection failures.
Chris@0:    */
Chris@0:   public function testConnectionFailureLogging() {
Chris@0:     $logger = \Drupal::service('logger.factory');
Chris@0: 
Chris@0:     // MySQL errors like "1153 - Got a packet bigger than 'max_allowed_packet'
Chris@0:     // bytes" or "1100 - Table 'xyz' was not locked with LOCK TABLES" lead to a
Chris@0:     // database connection unusable for further requests. All further request
Chris@0:     // will result in an "2006 - MySQL server had gone away" error. As a
Chris@0:     // consequence it's impossible to use this connection to log the causing
Chris@0:     // initial error itself. Using Database::closeConnection() we simulate such
Chris@0:     // a corrupted connection. In this case dblog has to establish a different
Chris@0:     // connection by itself to be able to write the log entry.
Chris@0:     Database::closeConnection();
Chris@0: 
Chris@0:     // Create a log entry.
Chris@0:     $logger->get('php')->error('testConnectionFailureLogging');
Chris@0: 
Chris@0:     // Re-establish the default database connection.
Chris@0:     Database::getConnection();
Chris@0: 
Chris@0:     $wid = db_query("SELECT MAX(wid) FROM {watchdog} WHERE message = 'testConnectionFailureLogging'")->fetchField();
Chris@0:     $this->assertTrue($wid, 'Watchdog entry has been stored in database.');
Chris@0:   }
Chris@0: 
Chris@0: }