xep-support: [xep-support] Re: Maximum Java memory

From: Kevin Brown <kevin@renderx.com>
Date: Tue Jan 27 2015 - 15:26:44 PST

One thing you can do to try and diagnose is look at the FO or the error
message:

file:/C:/DocLibrary/MXEngineOperationServiceBook/temp/pdf/oxygen_dita_temp/C
onfiguration/OpenTopic/cfg/common/artwork/warning.png

Does that file exist? Should it be there? Should it be somewhere else?
All RenderX knows is that the DITA toolkit passed in this:

<fo:external-graphic src="
url('file:/C:/DocLibrary/MXEngineOperationServiceBook/temp/pdf/oxygen_dita_t
emp/Configuration/OpenTopic/cfg/common/artwork/warning.png ')"/>

So all RenderX can say is the such-and-such a file does not exist.

Kevin

-----Original Message-----
From: Bill Bushnell [mailto:Bill.Bushnell@PACCAR.com]
Sent: Tuesday, January 27, 2015 3:08 PM
To: kevin@renderx.com; RenderX Community Support List
Subject: RE: [xep-support] Re: Maximum Java memory

Thanks Kevin,
Then how do I get the note element symbol in the PDF output. Is RenderX
having trouble navigating to two different directories for images? I could
change the location of the note symbol folder (C:\Program
Files\oXygen\frameworks\dita\img) to my project images folder but I don't
know how to tell RenderX\Oxygen where they're at. Even note element symbols
in elements that are not a conref to a collection library are not being
found.

~ Bill

-----Original Message-----
From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf Of
Kevin Brown
Sent: Tuesday, January 27, 2015 11:15 AM
To: 'RenderX Community Support List'
Subject: [xep-support] Re: Maximum Java memory

Exactly Bill.

There is no memory error or you would not get any PDF. With 384MB memory you
should be OK doing a book of 500+ pages.
The only error (which is not a fatal error) is that it cannot find the image
and that is why is says:

" ... of type null"

Null meaning it cannot determine the type of image because it cannot find it
or it is corrupt/garbage.

Be careful in your Java settings for memory also. You cannot set memory to
anything greater that 1280MB in Windows, Linux and a little higher in *nix
safely if you are on 32bit Java.
Only 64bit java will allow you to get beyond that barrier, that is a Java
contiguous memory limitation for all Java.

Kevin Brown
RenderX

-----Original Message-----
From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf Of Bill
Bushnell
Sent: Tuesday, January 27, 2015 10:58 AM
To: RenderX Community Support List
Subject: [xep-support] Re: Maximum Java memory

Thank you Hans. I appreciate the quick response to my inquiry.

I changed to setting from -Xmx1500m to -Xmx2048m and then transformed.
Transform resulted in the same error.
Tried -Xmx3048m and same results.
The error hasn't changed:

[echo] Maximum Java memory: -Xmx384m

In About:
JVM Memory Used: 84MB (3%) Total: 2709MB PermGen: 57MB/256MB

I am thinking that Kevin Brown's suggestion may be correct, that the images
aren't being be found for some reason.
The note element gets the images from this folder: C:\Program
Files\oXygen\frameworks\dita\img

Other images in the book are in a folder off of the project root, called
"images." And those come in just fine.
The collection library where the note elements are stored in the root.
The PDF generates but the note symbol is a red X.

~ Bill

-----Original Message-----
From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf Of
Hans-Peter Carpenter
Sent: Tuesday, January 27, 2015 10:07 AM
To: RenderX Community Support List
Subject: [xep-support] Re: Maximum Java memory

Hi Bill,

You need to increase the Xmx JVM parameter which defines the amount of
memory your Java process can use.

See the following document for how to do just that:

http://www.oxygenxml.com/doc/ug-author/index.html#topics/set-parameters-for-
application-launchers.html

Regards,

HANS CARPENTER

Tech Writer

http://www.redwood.com

RunMyJobs: Process Automation in the Cloud

This message may contain confidential or legally privileged information. In
the event of any error in transmission, unauthorized recipients are
requested to contact the sender immediately and do not disclose or make use
of this information. No warranties or assurances are made or given as to
the accuracy of the information given or in relation to the safety of this
e-mail and any attachments. No liability whatsoever is accepted for any
consequences arising from this e-mail.

If I don't document something, it's usually either for a good reason, or a
bad reason. In this case it's [certainly for] a good reason. :-)

Larry Wal

From: Xep-support [xep-support-bounces@renderx.com] on behalf of Bill
Bushnell [Bill.Bushnell@PACCAR.com]

Sent: Tuesday, January 27, 2015 6:01 PM

To: xep-support@renderx.com

Subject: [xep-support] Maximum Java memory

I am transforming using PDF - RenderX and get this error "Maximum Java
memory." The DITA topics are in a bookmap, which transforms just fine to Web
Help. I am using Oxygen 16.1. The error occurs when it starts converting
some PNG symbols in a note element, which are conrefed in different topics.

transform.fo2pdf.xep:

[echo] Maximum Java memory: -Xmx384m

[java] EXCEPTION: Failed to create image
file:/C:/DocLibrary/MXEngineOperationServiceBook/temp/pdf/oxygen_dita_temp/C
onfiguration/OpenTopic/cfg/common/artwork/warning.png of type null

[java] EXCEPTION: Failed to create image
file:/C:/DocLibrary/MXEngineOperationServiceBook/temp/pdf/oxygen_dita_temp/C
onfiguration/OpenTopic/cfg/common/artwork/caution.png of type null

_______________________________________________
(*) 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

!DSPAM:87,54c7dfd110101620313461!

_______________________________________________
(*) 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 Tue Jan 27 15:24:11 2015

This archive was generated by hypermail 2.1.8 : Tue Jan 27 2015 - 15:24:11 PST