We're getting below Exception when running aspose.pdf inside "tomcat-embed". This occurs even when there's no specific aspose.pdf processing within the sinlge web request.
It seems that the file aspose.pdf.jar\META-INF\services\java.nio.charset.spi.CharsetProvider references an invalid/unknown charset provider named com.aspose.ms.charsets.iso_8859_1.CharsetProvider. We assume, that this is probably caused by the obfuscation process. The referenced class name is the public one, while the implementation is hidden by obfuscation?
-----------------------------------------
Environment:
- Maven based build/toolchain
- tomcat-embed: 7.0.32
- spring: 3.2.1.RELEASE
- hibernate: 4.1.7.Final
- aspose.pdf: 4.3
- aspose.words: 11.8.0
-----------------------------------------
Exception:
Fatal: Error reading request, ignored
java.util.ServiceConfigurationError: java.nio.charset.spi.CharsetProvider: Provider com.aspose.ms.charsets.iso_8859_1.CharsetProvider not foundat java.util.ServiceLoader.fail(ServiceLoader.java:231)
at java.util.ServiceLoader.access$400(ServiceLoader.java:181)
at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:367)
at java.util.ServiceLoader$1.next(ServiceLoader.java:438)
at java.nio.charset.Charset$1.getNext(Charset.java:357)
at java.nio.charset.Charset$1.hasNext(Charset.java:370)
at java.nio.charset.Charset$4.run(Charset.java:591)
at java.nio.charset.Charset$4.run(Charset.java:585)
at java.security.AccessController.doPrivileged(Native Method)
at java.nio.charset.Charset.availableCharsets(Charset.java:584)
at org.apache.tomcat.util.buf.B2CConverter.<clinit>(B2CConverter.java:57)
at org.apache.tomcat.util.buf.ByteChunk.<clinit>(ByteChunk.java:102)
at org.apache.tomcat.util.buf.MessageBytes.<init>(MessageBytes.java:58)
at org.apache.tomcat.util.buf.MessageBytes.<init>(MessageBytes.java:36)
at org.apache.tomcat.util.buf.MessageBytes$MessageBytesFactory.newInstance(MessageBytes.java:685)
at org.apache.tomcat.util.buf.MessageBytes.newInstance(MessageBytes.java:78)
at org.apache.coyote.Request.<init>(Request.java:83)
at org.apache.coyote.AbstractProcessor.<init>(AbstractProcessor.java:53)
at org.apache.coyote.http11.AbstractHttp11Processor.<init>(AbstractHttp11Processor.java:265)
at org.apache.coyote.http11.Http11Processor.<init>(Http11Processor.java:55)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.createProcessor(Http11Protocol.java:165)
at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.createProcessor(Http11Protocol.java:103)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:569)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:310)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
at java.lang.Thread.run(Thread.java:722)
-----------------------------------------
There are some other posts describing similar problems in some other execution contexts and with UTF-7 CharsetProvider
- Provider com.aspose.ms.charsets.utf7.UTF7CharsetProvider not found
- the cardme is crushed with your library
- Conflict with spring framework