troubleshooting-liferay

Diagnose an unstable Liferay runtime by running guided diagnostic sequences with ldev doctor and status commands, then inspecting logs to surface health signals and identify failure points before attempting fixes.

Safely reproduce a Liferay portal issue by using isolated git worktrees, which create a contained environment for production-like reproduction workflows without contaminating your main development setup.

Check OSGi bundle health and portal inventory in Liferay by running targeted diagnostic commands that inspect subsystem states, narrowing down the responsible module and validating suspected defects.

Local Liferay portal startup failures with OSGi errors often stem from unstable runtime states; inspect OSGi module status and runtime logs to isolate the failing subsystem and identify the root cause.

Yes, you can use ldev tools to troubleshoot Liferay worktree environments by executing diagnostic sequences and applying guardrails that enforce safe isolation during issue reproduction and analysis.

Before attempting fixes on an unstable Liferay runtime, perform structured analysis by gathering runtime health signals, reviewing logs, and checking portal inventory to ensure safe and accurate diagnosis.