Hi Kevin,
We are using DITA Open Toolkit integrated with IXIASOFT DITA CMS Output Generator. The error is occurring in the XEP portion of the DITA OT log:
transform.fo2pdf.xep:
[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.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.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)
[java] Java Result: 1
It is same error I was getting back in 2013, when you referred me to this post as the fix for this. See http://services.renderx.com/lists/xep-support/5185.html.
I will try removing the renamed crimson_save.jar file from the build machine an see if that helps.
However, I am working with IXIASOFT to figure out how to specify the parser used by XEP in the IXIASOFT configuration files, which was the solution provided by Alexei in the above post which says this:
The simplest way to resolve the problem is to tell Java to use a specific XML Reader.
Add the following property to the XEP execution command:
-Djavax.xml.parsers.SAXParserFactory=com.icl.saxon.aelfred.SAXParserFactoryImpl
It will force usage of Saxon Aelfred XML parser.
But, we are getting a DITA OT error after doing this:
BUILD FAILED
XML parser factory has not been configured correctly: Provider com.icl.saxon.aelfred.SAXParserFactoryImpl not found
So, before we go far down this path, I just want to make sure the solution provided 2 years ago is still the correct solution to implement.
BTW We are using Java build 1.7.0_51-b13.
Thanks,
Rhonda
-----Original Message-----
From: Kevin Brown [mailto:kevin@renderx.com]
Sent: Wednesday, September 02, 2015 2:19 PM
To: Rhonda Fitzgerald; 'RenderX Community Support List'
Subject: RE: [xep-support] Re: Exception in thread "main" java.lang.InternalError: fillbuf error
Rhonda:
I would be a little lost. It you look at the stacktrace for the error, you would see:
[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.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)
Which is an error in Crimson, not RenderX. Does this fillbuf error report the same error trace?
I see from an old message you renamed crimson.jar to crimson_save.jar.
Is that still there? If yes, perhaps you should remove it because maybe the solution you are using is loading any .jar in that path.
Also, what exactly is it that you are running -- or better said, how is it that you run RenderX? Are you calling the .bat? Something else?
Kevin Brown (650) 327-1000 Direct
(650) 328-8008 Fax
(925) 395-1772 Mobile
skype:kbrown01
kevin@renderx.com
sales@renderx.com
http://www.renderx.com
-----Original Message-----
From: Rhonda Fitzgerald [mailto:rfitzger@progress.com]
Sent: Wednesday, September 02, 2015 10:01 AM
To: Kevin Brown <kevin@renderx.com>; RenderX Community Support List <xep-support@renderx.com>
Subject: RE: [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 the 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@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@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.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.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 Fitzgerald
>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/7d
>28f3db/attachment-0001.html>
>
>------------------------------
>
>_______________________________________________
>Xep-support mailing list
>Xep-support@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
Received on Wed Sep 2 11:36:08 2015
This archive was generated by hypermail 2.1.8 : Wed Sep 02 2015 - 11:36:13 PDT