Trying to integrate groupdocs comparison jar in our project, after adding jar and building the project, getting below error while running the app. Kindly guide us to resolve this.
Cause3: java.io.IOException: Unsupported size: 25415654 for JarEntry META-INF/MANIFEST.MF. Allowed max size: 16000000 bytes. You can use the jdk.jar.maxSignatureFileSize system property to increase the default value.
We could not reproduce this issue at our end. Which IDE you’re using? It would be great if you share the sample application (and steps to reproduce the issue) with us to reproduce the issue. Please compress the application in a ZIP format (exclude license file) and upload here.
Hi @atir.tahir , thanks for checking this.
We are using intellij IDE and bazel project. Trying to integrated it with salesforce core application as we are in the process of procuring the license. It would not be possible to share the application. Kindly let us know if you have any suggestions that could potentially fix this.
Thanks.
@sarfraz.ahmad
We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.
Issue ID(s): COMPARISONJAVA-1672
You can obtain Paid Support Services if you need support on a priority basis, along with the direct access to our Paid Support management team.
We are already working on this issue. As soon as the fix is available, we’ll notify you. However, a workaround could be found here on GitHub.
Thanks Atir for updates.
The workaround you suggested isn’t feasible in our case as updating env variables can possibly impact other services running inside core app.
Request you to share the ETA for the above fix your team is working on. It would really be helpful.
Thanks
We are further investigating this ticket. You’ll be notified as soon as we have an ETA of fix/release.
Hi @atir.tahir,
Is there any further updates on this?
I am providing below complete stack trace of the issue we are facing which includes multiple cause of failure. Please have a look if they are related.
Cause1: java.lang.reflect.InvocationTargetException
Cause1-StackTrace:
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:568)
at system.init.tasks.AppStartupTaskWithJavaClassesWithInitMethod$JavaInitFuture.call(AppStartupTaskWithJavaClassesWithInitMethod.java:46)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
... 4 shared with parent
Cause2: java.util.ServiceConfigurationError: javax.imageio.spi.ImageWriterSpi: Error accessing configuration file
Cause2-StackTrace:
at java.base/java.util.ServiceLoader.fail(ServiceLoader.java:586)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.parse(ServiceLoader.java:1180)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.nextProviderClass(ServiceLoader.java:1213)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNextService(ServiceLoader.java:1228)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.hasNext(ServiceLoader.java:1273)
at java.base/java.util.ServiceLoader$2.hasNext(ServiceLoader.java:1309)
at java.base/java.util.ServiceLoader$3.hasNext(ServiceLoader.java:1393)
at java.desktop/javax.imageio.spi.IIORegistry.registerApplicationClasspathSpis(IIORegistry.java:185)
at java.desktop/javax.imageio.spi.IIORegistry.<init>(IIORegistry.java:113)
at java.desktop/javax.imageio.spi.IIORegistry.getDefaultInstance(IIORegistry.java:134)
at java.desktop/javax.imageio.ImageIO.<clinit>(ImageIO.java:66)
at common.util.DynamicImageData.getRaster(DynamicImageData.java:123)
at common.util.DynamicImageData.init(DynamicImageData.java:115)
... 11 shared with parent
Cause3: java.io.IOException: Unsupported size: 34543685 for JarEntry META-INF/MANIFEST.MF. Allowed max size: 16000000 bytes. You can use the jdk.jar.maxSignatureFileSize system property to increase the default value.
Cause3-StackTrace:
at java.base/java.util.jar.JarFile.getBytes(JarFile.java:804)
at java.base/java.util.jar.JarFile.getManifestFromReference(JarFile.java:419)
at java.base/java.util.jar.JarFile.getManifest(JarFile.java:406)
at java.base/sun.net.www.protocol.jar.URLJarFile.isSuperMan(URLJarFile.java:177)
at java.base/sun.net.www.protocol.jar.URLJarFile.getManifest(URLJarFile.java:145)
at java.base/java.util.jar.JarFile.maybeInstantiateVerifier(JarFile.java:724)
at java.base/java.util.jar.JarFile.getInputStream(JarFile.java:844)
at java.base/sun.net.www.protocol.jar.JarURLConnection.getInputStream(JarURLConnection.java:187)
at java.base/java.util.ServiceLoader$LazyClassPathLookupIterator.parse(ServiceLoader.java:1172)
We are already investigating this issue with priority. You’ll be notified as there’s any update.
Hi @atir.tahir,
It would be really appreciable if you can share updates on the progress of above fix or any ETA on the same.
Thanks @atir.tahir for updates.
Please note, as per shared stack trace above we have a limit of 16MB on maxSignatureFileSize, could you please help create a new jar with Manifest.mf file less than. 16MB and share that with us ?
We are further investigating this scenario. You’ll be notified in case of any update.
hi Atir, This bug has been open from last 15 days. We have been in discussion with your sales team and got to understand that this was on priority queue, since we have already obtained licenses for paid support. Looking at the issue, it doesn’t seem to be so complicated that it would take 15 days or more to resolve. Can you please give an update by the end of day today as this is a very high priority feature for us and we are currently at risk of not being able to deliver this feature in the current release. This is making us doubt on the ETA of fixes to be delivered, I would take it up separately with your management but currently would appreciate any inputs apart from we are currently working on it. Thanks!!
We are going to release the fix soon. You’ll be notified as the release is available to download.