Submit Feedback
Legacy Knowledge Base
Published Sep. 10, 2025

Error: Unable to copy from file:/opt/liferay/osgi/modules/biz.aQute.remote.agent-6.4.0.jar

Written By

Jose L. Bango

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 starting the server, the following exception is printed in the logs: 
    2024-09-25 17:50:18.363 ERROR [main][ModuleReadHookImpl:88] Unable to copy from file:/path/to/osgi/modules/biz.aQute.remote.agent-6.4.0.jar to /path/to/osgi/state/org.eclipse.osgi/1460/0/bundleFile
    java.nio.file.NoSuchFileException: /path/to/bundles/osgi/modules/biz.aQute.remote.agent-6.4.0.jar
  • Why is this happening? Does it have any implications?

Environment

  • Liferay DXP 2024.Q2.10-2024.Q2.12
  • Liferay DXP 2024.Q3.1-2024.Q3.5

Resolution

  • The issue is caused due to an unintended content not properly deleted during the bundle creation.
  • It only happens the first time the bundle starts. This error should not affect the Liferay Portal operation and can be safely ignored.
  • As a workaround for non Docker environments, clearing  /osgi/state before starting the server avoids the issue.

Additional Information

Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?