Jama Connect Interchange: License Expired Error – “Thu Jan 01 00:00:00 GMT 1970”

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

Jama Connect®
Self-hosted
Jama Connect Interchange™
JCI Module: jci-exe-svc, jci-config-svc

Summary

You may be unable to run integrations even though your license is active. In the logs of the jci-exe-svc container, you may see:

INFO  | e.ExecutionService | License has expired. Expiration date is Thu Jan 01 00:00:00 GMT 1970. Exiting.

This occurs when the license file format or placement is incorrect, causing JCI to misinterpret an otherwise valid license.

Cause

The JCI license is sensitive to formatting and file attributes. Certain Linux commands or manual edits can alter the license file, preventing the service from reading it correctly.

Resolution

Obtain the license file

Download the license from your email.
Avoid creating a new text file or copying the license content manually, as this can corrupt formatting.
Save the file as: connect_license.txt.

Copy the license to JCI containers

Use scp or another secure method to transfer the file to the self-hosted instance.

Transfer the license to containers using the -a flag to preserve file attributes:

sudo docker cp -a connect_license.txt config-svc-interchange:/static-files/
sudo docker cp -a connect_license.txt exe-svc-interchange:/static-files/

Verify container status

Some containers may restart after copying the license.
Check stability using:
```
watch docker ps
```
Ensure both jci-config-svc and jci-exe-svc containers report a stable status.

Prevention

Confirm the license with Jama Support to ensure it is correct and contains all necessary information before copying.
Avoid manual edits or the recreation of the license file on the host machine.
Use the -a flag when copying to containers to preserve file attributes.

Additional Resources

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

Related to