![]() But the windows standalone version works fine. storeclasspath:server.jks -storeclasspath:server.jks. Same issue still exists with davmail-6.0.0-3375 - with the setup64 version, in spite of Java 64 being installed. I even reverted to the tried and tested turn it off and on again technique with no : Parameter msg must not be emptyĪt .(Code39Bean.java:184)Īt .ConfigurableBarcodeGenerator.generateBarcode(ConfigurableBarcodeGenerator.java:174)Īt .loader.ImageConverterBarcode2G2D$Graphics2DImagePainterBarcode.paint(ImageConverterBarcode2G2D.java:122)Īt .(PDFImageHandlerGraphics2D.java:99)Īt .(AbstractIFPainter.java:249)Īt .(AbstractIFPainter.java:205)Īt .(AbstractIFPainter.java:170)Īt .(AbstractIFPainter.java:319)Īt .(PDFPainter.java:289)Īt .(IFRenderer.java:1319)Īt .AbstractRenderer.renderInlineViewport(AbstractRenderer.java:1034)Īt .AbstractPathOrientedRenderer.renderInlineViewport(AbstractPathOrientedRenderer.java:836)Īt .(IFRenderer.java:863)Īt .AbstractRenderer.renderInlineArea(AbstractRenderer.java:877)Īt .(IFRenderer.java:927)Īt .AbstractRenderer.renderLineArea(AbstractRenderer.java:845)Īt .AbstractRenderer.renderBlocks(AbstractRenderer.java:704)Īt .AbstractRenderer.renderBlock(AbstractRenderer.java:758)Īt .(IFRenderer.java:999)Īt .AbstractRenderer.renderBlocks(AbstractRenderer.java:689)Īt .AbstractPathOrientedRenderer.renderReferenceArea(AbstractPathOrientedRenderer.java:759)Īt .AbstractRenderer.renderBlock(AbstractRenderer.java:744)Īt .(IFRenderer.java:812)Īt .AbstractRenderer.renderBlock(AbstractRenderer.java:737)Īt .AbstractRenderer.renderFlow(AbstractRenderer.java:591)Īt .AbstractPathOrientedRenderer.renderFlow(AbstractPathOrientedRenderer.java:789)Īt .AbstractRenderer.renderMainReference(AbstractRenderer.java:568)Īt .AbstractRenderer.renderBodyRegion(AbstractRenderer.java:433)Īt .AbstractRenderer.renderRegionViewport(AbstractRenderer.java:380)Īt .(IFRenderer.java:738)Īt .AbstractRenderer.renderPageAreas(AbstractRenderer.java:345)Īt .AbstractRenderer.renderPage(AbstractRenderer.java:318)Īt .(IFRenderer.java:587)Īt .RenderPagesModel.renderPage(RenderPagesModel.java:193)Īt .RenderPagesModel.checkPreparedPages(RenderPagesModel.java:174)Īt .RenderPagesModel.addPage(RenderPagesModel.java:146)Īt .AbstractPageSequenceLayoutManager.finishPage(AbstractPageSequenceLayoutManager.java:316)Īt .PageSequenceLayoutManager.finishPage(PageSequenceLayoutManager.java:243)Īt .PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:147)Īt .AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)Īt .DelegatingFOEventHandler.endPageSequence(DelegatingFOEventHandler.java:114)Īt .fo.FO2StructureTreeConverter.endPageSequence(FO2StructureTreeConverter.java:184)Īt .(PageSequence.java:139)Īt .FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:362)Īt .FOTreeBuilder.endElement(FOTreeBuilder.java:190)Īt .TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1102)Īt .endElement(AbstractSAXParser.java:609)Īt .scanEndElement(XMLDocumentFragmentScannerImpl.java:1782)Īt .$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2967)Īt .next(XMLDocumentScannerImpl.java:602)Īt .next(XMLNSDocumentScannerImpl.java:112)Īt .scanDocument(XMLDocumentFragmentScannerImpl.java:505)Īt .11Configuration.parse(XML11Configuration.java:842)Īt .11Configuration.parse(XML11Configuration.java:771)Īt .parse(XMLParser.java:141)Īt .parse(AbstractSAXParser.java:1213)Īt .ansform(TransformerIdentityImpl.java:485)Īt nFOP(mn2pdf.java:292)Īt nvertmn2pdf(mn2pdf.java:225)Īt 2pdf.main(mn2pdf. If you happen to have specified your trust store location as the same as your keystore in the Spring Boot configuration, you'll likely get the trustAnchors parameter must be non-empty message when starting the application. I've tried updating the CA certificates, both sudo update-ca-certificates -f and sudo apt install ca-certificates-java -reinstall, neither of which solves the problem. This leads me to the conclusion that it is Ubuntu related rather than gradle/openjdk/oracle related. First, Java looks for the TrustStore in two locations (in order): JAVAHOME/lib/security/jssecacerts JAVAHOME/lib/security/cacerts We can overwrite the default location with the parameter. This is irrespective of gradle version, java version (both openjdk and oracle 8 and 9 have the fault) and shadowjar version. Let's now have a look at a TrustStore location and format in Java. If you happen to have specified your trust store location as the same as your keystore in the Spring Boot configuration, you'll likely get the trustAnchors parameter must be non-empty message when starting the application. > : Unexpected error: : the trustAnchors parameter must be non-empty The problem is due to the way that Tomcat deals with the trust store. ![]() ![]() gradlew I get the following error: * What went wrong:Įrror resolving plugin ![]() Trying to set up a development environment, when I run gradle or.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |