Unable to connect to an Adobe Commerce integration environment (SSH/performance issues)
If you’re unable to connect to an Adobe Commerce integration environment or experiencing sluggish performance, the issue might be due to resource exhaustion from long-running processes. These problems can be resolved by disabling unnecessary cron jobs and following integration environment best practices.
Description description
Environment
- Product: Adobe Commerce on Managed Services
- Environment Type: Integration (Development)
Issue/Symptoms
In integration environments with limited resources, long-running or resource-heavy processes (e.g., Magento cron jobs or consumers) can exhaust system capacity, resulting in:
- Blocked SSH sessions
- Slow deployments
- Overall system instability
Resolution resolution
Note: Adobe recommends disabling crons in integration environments and running them on demand only.
Try the following steps to solve the issue:
-
Use SSH to identify resource-heavy cron jobs:
ps aux | grep cron # Lists running cron processes -
Disable unnecessary cron jobs (integration environments should not run cron continuously):
./vendor/bin/ece-tools cron:disable # Disables all Magento cron jobs in the current cloud environment.Note: Running
ece-tools cron:disableonly affects the current environment state. After each deployment, cron jobs are re-enabled by default. To keep crons disabled in Integration environments, configure this directly in the crons: section of your.magento.app.yaml. -
Run cron manually only when required.
For example:
php bin/magento cron:run # Manually executes all scheduled Magento cron jobs. -
Follow integration best practices.
- Avoid continuous automated tasks (indexers, consumers, payment syncs, etc.).
- Use integration environments for short-lived functional testing and development, not load or performance testing.
- Promote code to staging or production for full-scale testing.
- For more details refer to Integration environment in the Commerce on Cloud Guide.