[xep-support] Re: Exception in thread "main" java.lang.InternalError: fillbuf error

I think she said she tried this and it failed with "Provider com.icl.saxon.aelfred.SAXParserFactoryImpl not found."
I don't have experience with IXIASOFT and it has been a while since I've used the DITA-OT, but I'm surprised anyone is using either Aelfred or Crimson. Both parsers are quite old...I don't think either has been developed or updated in well over a decade. The JDK has a more up to date parser in it already. Maybe try replacing your
-Djavax.xml.parsers.SAXParserFactory=com.icl.saxon.aelfred.SAXParserFactoryImpl
with

-Djavax.xml.parsers.SAXParserFactory=com.sun.org.apache.xerces.internal.jaxp.SAXParserFactoryImpl
which should tell it to use the JDK's built in parser. That parser is a version of Apache Xerces. Personally I would use the latest Xerces, but that would require knowing how to install it into your IXIASOFT/DITA-OT environment, and the JDK version of it is probably fine.

On 09/02/2015 05:05 PM, Hans-Peter Carpenter wrote:> ‎Hi Rhonda,>> The problem with this is, that the jar file can be called foobar.jar, be on the classpath.... if it has ‎org.apache.crimson‎ in it you are in trouble.>> Use -‎Djavax.xml.parsers.SAXParserFactory=com.icl.saxon.aelfred.SAXParserFactoryImpl> Instead, as instructed.>> Regards,>> HP>> DISCLAIMER: I never had this issue, do not have org.apache.crimson, afaik.>>> Sent from my BlackBerry z30 smartphone.> Original Message> From: Rhonda Fitzgerald> Sent: Wednesday, 2 September 2015 19:03> To: Kevin Brown; RenderX Community Support List> Reply To: RenderX Community Support List> Subject: [xep-support] Re: Exception in thread "main" java.lang.InternalError: fillbuf error>>> Hi,>> This issue has resurfaced for us. In fact, it's been on again/off again for us since 2013 when I first posted this issue. It's strange because it seems somewhat random in that the PDF won't build, and then a couple of hours later, it will build -- with absolutely
no changes to the sources.>> We have one very large book that was building, and now it will not build due to these errors. I have tried everything I tried previously to "fix" this, but the issue persists. At the time when I first thought I fixed this issue, I just renamed the crimson.jar file shipped with xep to crimson_save.jar, my thinking was that perhaps it wouldn't use it if it couldn't find it. This did seem to fix the issue at the time, but perhaps it was just coincidental the errors went away, because, like I say, they seem somewhat random to me. I have searched the build machine and there are no files named crimson.jar anywhere on that machine. I have rebooted the build machine also.>> Back in 2013 you referred me to another thread on this which suggested that we specify which parser to use http://services.renderx.com/lists/xep-support/5185.html. Is this still the recommended/only fix for this? The person on this thread did say that he patched the crimson.jar file that shipped with xep to fix t
he issue for him. Is there a newer crimson.jar file, with the patch that I could try replacing in my xep install?>> Please advise.>> Thanks.> Rhonda Fitzgerald>> -----Original Message-----> From: Kevin Brown [mailto:kevin_AT_renderx.com]> Sent: Wednesday, September 18, 2013 11:50 AM> To: RenderX Community Support List> Cc: Rhonda Fitzgerald> Subject: Re: [xep-support] Re: Exception in thread "main" java.lang.InternalError: fillbuf error>> See http://services.renderx.com/lists/xep-support/5185.html>> Kevin Brown>> Rhonda Fitzgerald <rfitzger_AT_progress.com> wrote:>>> Also, it appears I didn't copy the entire error message, where there are references to RenderXEP at the bottom, which is why I though this may be RenderXEP related.>>>> [java] Exception in thread "main" java.lang.InternalError: fillbuf>> [java] at org.apache.crimson.parser.InputEntity.parsedContent(InputEntity.java:545)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1826)>> [java] at org.apache.crimson.par
ser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElem
ent(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507
)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.content(Parser2.java:1779)>> [java] at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1507)>> [java] at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:500)>> [java] at org.apache.crimson.parser.Parser2.parse(Parser2.java:305)>> [java] at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:442)>> [java] at com.renderx.xep.FormatterCore.render(Unknown Source)>> [java] at com.renderx.xep.FormatterImpl.render(Unknown Source)>> [java] at com.renderx.xep.FormatterImpl.render(Unknown Source)>> [java] at com.idiominc.ws.opentopic.fo.xep.Runner.run(Runner.java:100)>> [java] at com.idiominc.ws.opentopic.fo.xep.Runner.main(Runner.java:60)>>>> -----Original Message----->> From: Rhonda Fitzge
rald>> Sent: Wednesday, September 18, 2013 9:57 AM>> To: 'xep-support@renderx.com'>> Subject: Re: Exception in thread "main" java.lang.InternalError: fillbuf error>>>> Kevin,>>>> Thanks. I don't recall specifically installing crimson parser? Is there a way for me to determine where this came from?>>>> Rhonda>>>> ---------------------------------------------------------------------->>>> Message: 1>> Date: Tue, 10 Sep 2013 09:48:27 -0700>> From: Kevin Brown <kevin@renderx.com>>> To: RenderX Community Support List <xep-support@renderx.com>>> Subject: [xep-support] Re: Exception in thread "main">> java.lang.InternalError: fillbuf error>> Message-ID: <mncsvk2flaxjvi4b288bvfix.1378831707281@email.android.com>>> Content-Type: text/plain; charset="utf-8">>>> I may be seeing something wrong but the error is reported by crimson parser (which is not recommended) and not by RenderX XEP.>>>> Kevin Brown>>>> Rhonda Fitzgerald <rfitzger@progress.com> wrote:>>>>> _______________________________________________>>> (
*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support>>> (*) By using the Service, you expressly agree to these Terms of Service http://w>>> ww.renderx.com/terms-of-service.html>> -------------- next part -------------->> An HTML attachment was scrubbed...>> URL: <http://lists.renderx.com/pipermail/xep-support/attachments/20130910/7d28f3db/attachment-0001.html>>>>> ------------------------------>>>> _______________________________________________>> Xep-support mailing list>> Xep-support_AT_renderx.com>> http://lists.renderx.com/mailman/listinfo/xep-support>>>>>> End of Xep-support Digest, Vol 36, Issue 2>> ******************************************>>>> !DSPAM:87,5239b2a49851385397852!>>>>>> _______________________________________________>> (*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support>> (*) By using the Service, you expressly agree to these Terms of Service http://w>> ww.renderx.com/terms-of-service.html> ____________________________________
___________> (*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support> (*) By using the Service, you expressly agree to these Terms of Service http://w> ww.renderx.com/terms-of-service.html>> _______________________________________________> (*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support> (*) By using the Service, you expressly agree to these Terms of Service http://w> ww.renderx.com/terms-of-service.html

_______________________________________________(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support(*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/terms-of-service.html
Received on Wed Sep 2 15:58:23 2015