Tenant Context Leaks After DB Connection Exhaustion (Laravel Octane + Multitenancy)

[MiguelGonc]

Context:

I'm using Laravel + Octane + Spatie Multitenancy with a session-based tenant switcher in middleware. The middleware calls Tenant::makeCurrent() using a tenant ID stored in the session.

The Issue:
When the app exhausts PostgreSQL connections (e.g., due to many slow queries or transaction failures), the app/octane crashs and users sometimes begin to see data from another tenant/user after the database becomes available again.

This appears to be a tenant context leak — tenant state is being shared between requests.

I don't know if this is a multi-tenancy or octane related issue.

This is not a bug easy to catch localy.

Does anyone can help me?

Thank You

[shirokovnv]

Hello, @MiguelGonc

Have you tried to put MultiTenancy services into octane config section Warm / Flush Bindings ?

Also, may be this can help:

laravel-multitenancy/src/MultitenancyServiceProvider.php

Lines 36 to 48 in 19a65d1

	protected function detectsLaravelOctane(): static
	{
	if (! isset($_SERVER['LARAVEL_OCTANE'])) {
	app(Multitenancy::class)->start();
	return $this;
	}
	Event::listen(fn (OctaneRequestReceived $requestReceived) => app(Multitenancy::class)->start());
	Event::listen(fn (OctaneRequestTerminated $requestTerminated) => app(Multitenancy::class)->end());
	return $this;
	}

If you are using different environment to detect, that your application served by OCTANE.

Let me know, if that helps you.

[MiguelGonc]

Hi @shirokovnv

Sorry for the delay in responding, I already had those changes in the code, however the problem persists, but at this moment I'm unsure because it seems to me that it's not just the MultiTenancy that's having problems, but the user's session itself that's being switched to another user's. It's proving to be a complicated problem to solve because I can't replicate it locally.