Kareem Zidane

We're hosting Adminer on a server to give easy access to many users (students) to avoid having them install and configure it and some of them have reported recently arbitrary timeout issues while using it as a result of the server taking too long to respond. We still haven't figured out a way to replicate the issue yet and we'll dig deeper into that but we were just curious to ask if there are any known limitations that Adminer has on the number of simultaneous users or connections? Thank you!

Thank you!

If there's a mistake in the server's URL, any further requests to access Adminer will be blocked until the request that's trying to connect to the wrong server is killed. This is because PHP locks session data to prevent concurrent writing to the same session and Adminer doesn't close the session before trying to connect to the database server. Adding session_write_close before calling connect seems to fix the issue but not sure if it breaks anything else.

If there's a mistake in the server's URL, any further requests to access Adminer will be blocked until the request that's trying to connect to the wrong server is killed. This is because PHP locks session data to prevent concurrent writing to the same session and Adminer doesn't close the session before trying to connect to the database server. Adding session_write_close before calling connect` seems to fix the issue but not sure if it breaks anything else.

If there's a mistake in the server's URL, any further requests to access Adminer will be blocked until the request that's trying to connect to the wrong server is killed. This is because PHP locks session data to prevent concurrent writing to the same session and Adminer doesn't close the session before trying to connect to the database server. Adding session_write_close before calling [connect](https://github.com/vrana/adminer/blob/master/adminer/include/auth.inc.php#L165)` seems to fix the issue...

If there's a mistake in the server's URL, any further requests to access Adminer will be blocked until the request that's trying to connect to the wrong server is killed. This is because PHP locks session data to prevent concurrent writing to the same session and Adminer doesn't close the session before trying to connect to the database server. Adding session_write_close before calling [connect](https://github.com/vrana/adminer/blob/master/adminer/include/auth.inc.php#L165) seems to fix the issue...

If there's a mistake in the server's URL, any further requests to access Adminer will be blocked until the request that's trying to connect to the wrong server is killed. This is because PHP locks session data to prevent concurrent writing to the same session and Adminer doesn't close the session before trying to connect to the database server. Adding session_write_close before calling connect seems to fix the issue but not sure if it breaks anything else.