Searching for reviewers in OJS 3.3.0.4 and 3.3.0.5 takes too long

OJS 3.3.0.4 and 3.3.0.5
Description of issue: Reviews stage. Have any users experienced a problem finding reviewers in the review stage? In our case, the actual loading of the Add Reviewer form takes too long (more than a minute) and the search Locate a reviewer takes several minutes or crashes. The known reviewer user is not found.

Error log: [22-Apr-2021 07:25:27 America/Chicago] ojs2: 404 Not Found

image

image

image

Hi,

We are also facing the same issue. We just upgraded on last weekend.

Please let us know if anyone facing the same or any solution.

image

Error log:-

[21-Apr-2021 10:06:12 UTC] PHP Fatal error: Uncaught PDOException: SQLSTATE[HY000]: General error: 2013 Lost connection to MySQL server during query in journals/lib/pkp/lib/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php:115
Stack trace:
#0 journals/lib/pkp/lib/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php(115): PDOStatement->execute(NULL)
#1 journals/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(370): Doctrine\DBAL\Driver\PDOStatement->execute()
#2 journals/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(664): Illuminate\Database\Connection->Illuminate\Database{closure}(Object(Illuminate\Database\Query\Expression), Array)
#3 journals/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php(745): Illuminate\Database\Connection->runQueryCallback(Object(Illuminate\Database\Query\Expression), Ar in journals/lib/pkp/lib/vendor/laravel/framework/src/Illuminate/Database/Connection.php on line 671

Hi All,

Any Update on this issue, we are stuck and not able to add a reviewer. It’s urgent for us.

Hello community,

We have recently updated to 3.3.0-11 and in one of our journals takes to long to load the “Add reviewer” window

We already verify if there were too much spam users and changed all tables to InnoDB but it still takes about 5 minutes to load

Has somebody passed thorugh this?
Thanks in advance

I remember we have solved this issue. It was because our database tables were in the MyISAM format. There should be InnoDB.