Legacy Knowledge Base
Published Sep. 10, 2025

Getting 'unsatisfied references' error after JAR deployment

Written By

Anushka Tiwari

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.

Issue

When creating a service builder project and after deploying the Jars files, it shows the unsatisfied references'' in the GOGO shell.

Steps to reproduce:

  • Start the server.
  • Deploy the JAR file.
  • Navigate to the Control Panel > Configuration > Gogo shell.
  • Enter 'lb', and can see that the module is in an active state.
  • Then enter this command: ds:unsatisfied
    Expected behavior: The error should not be displayed on the UI.
    Observed behavior: Getting below output:
Output
Bundle {id: 1034, name: com.test.unpaid.bond.web, version: 1.0.0}
Declarative Service {id: 4345, name: com.test.unpaid.bond.web.portlet.TestUnpaidBondWebPortlet, unsatisfied references:
{name: _fooLocalService, target: null}

Environment

  • Liferay DXP 7.1

Resolution

  • The header Liferay-Spring-Context: META-INF/spring is not present in the bundle JAR file and is missing.
  • Add the header to thebnd.bndfile of the module and build the module again.
  • Then, deploy the created JAR file. The error will not be visible.

Additional Information

Did this article resolve your issue ?

Legacy Knowledge Base