How to Fix KOTS Deployment Stuck on ActiveMQ Pod

Published Date: December 11, 2025
Validated: Yes
Audience: Everyone
Products and Versions Covered:

• Jama Connect® version(s) 9.28.1
• Cloud/CVC
• Self-hosted
• Kubernetes Jobs: activemq-backup, activemq-restore

Summary 

During deployment or re-deployment of Jama Connect® 9.28.1, the deployment process triggers Kubernetes jobs for activemq-backup and activemq-restore.

If these jobs do not complete, the deployment of remaining Kubernetes resources is held up.

In some cases, the activemq-backup-xxxx pod may enter a Pending state while waiting for a PVC that does not exist. Deleting the underlying Kubernetes jobs allows the deployment to proceed.

Cause
The activemq-backup pod may remain pending due to a missing PVC, preventing the backup/restore job from completing and blocking the deployment of other resources.
 

Resolution

1. List the current Kubernetes jobs

   kubectl get jobs

2. Delete the backup and restore jobs

   kubectl delete job activemq-backup
   kubectl delete job activemq-restore

3. After running these commands:
   • The activemq-backup-xxxx pod and associated jobs will be deleted.
   • Deployment of remaining Kubernetes resources will continue normally.

Prevention

• Ensure PVCs are created and available before initiating backup/restore jobs in KOTS deployments.
• Monitor Kubernetes jobs during deployments to identify and resolve Pending pods early. 

Additional Resources

• Jama Connect User Guide - 9.28.x
• Success Programs
• Success Catalog
• Datasheets
• Request a Solution Offering or Training from the Success Catalog

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or ideas for improvement below.