Error Reading Image File in Liferay Document Library
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
- I am getting the following error in the console log for an unidentified image:
ERROR [https-jsse-nio-443-exec-7][ImageImpl:69] Error reading image 54130
com.liferay.document.library.kernel.exception.NoSuchFileException:
{companyId=0, repositoryId=0, fileName=54130.gif, cause=java.io.FileNotFoundException:
C:\Liferay7.2\liferay-dxp-tomcat-7.3.10-ga1\liferay-dxp-7.3.10-ga1\data\document_library\0\0\54130.gif\1.0
(The system cannot find the path specified)}
Environment
- DXP 7.0
- DXP 7.1
- DXP 7.2
- DXP 7.3
- DXP 7.4
Resolution
- Copy and Rename one of the existing logo image files in the [Tomcat_Home]\data\document library\0\0\ folder to be the same as the file name it claims it cannot find. For example: 12345.gif
Additional Information
- Based on the file path and file name the system is essentially looking for a default Liferay image file that no longer exists. This happens sometimes as a result of upgrades that still have some memory of older versions of the site.
- This does not constitute any major concern and could be safely ignored, but of course, if you prefer to have no errors hanging over your bundle the resolution above is the way to go.
Did this article resolve your issue ?