Logging error for Apache POI after AEM 6.5.17 update | Community
Skip to main content
Martin-Nekula
Level 2
June 27, 2023
Solved

Logging error for Apache POI after AEM 6.5.17 update

  • June 27, 2023
  • 2 replies
  • 1894 views

Hello everyone,

after the upgrade to the current Service Pack, we are getting the following error on startup. It references the org.apache.poi.ooxml.POIXMLRelation class, so I think it regards the OSGi bundle wrapper for the Apache POI library (com.adobe.granite.poi). This we actually use in our applications to generate XSLX files.

 

 

Totally there are 4 Log4J related libraries, therefore I don´t understand why it cannot find the logging implementation.

 

The imported bundles of the POI library seem to be all right:

 

Is anyone else having the same issue?

 

Best Regards

Martin

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Martin-Nekula

After consulting via ticket this issue is really already taken care of and will be fixed in SP 18.

 

2 replies

aanchal-sikka
Community Advisor
Community Advisor
June 28, 2023

Hello @martin-nekula 

 

From the bundle's screenshot, all dependencies seem to be met. Are you noticing any issues while creating Excel files? Or is it just the log that you might be curious about?

Aanchal Sikka
Martin-Nekula
Level 2
June 28, 2023

The Excel files are created ok, it is really just the startup log error. I was wondering if anyone else is having this issue and has a solution, or if we should simply wait for next SP.

aanchal-sikka
Community Advisor
Community Advisor
June 28, 2023

@martin-nekula 

 

May be we can share the logs via a support ticket.

If Adobe has already noticed it, they can suggest the complexity. If they are unaware, they can plan for it.

 

In either scenario, it will benefit everyone.

Aanchal Sikka
Martin-Nekula
Martin-NekulaAuthorAccepted solution
Level 2
July 19, 2023

After consulting via ticket this issue is really already taken care of and will be fixed in SP 18.