Re: html2pdf4i was-->Re: RPGCGI - Convert HTML page to PDF

Aaron,

It seems that when the JVM needs starts with the headless property, it must run some sort of PASE routine, which must initiate a startup for the PASE environment for the job.
This only became apparent later when users of a totally unrelated application within the same job began reporting a system error that PASE had already been loaded.
It was apparent that their existing production application had been designed to run a routine via QP2SHELL.
I believe I tested that this had nothing to do with the PDF class itself by simply invoking any java class with the JVM headless property set to true.
If the JVM was loaded within the job before the existing app was requested then the error would occur, thus breaking an existing production app.
A data queue solution resolved both this and the JVM load performance hit.

Peter


-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Aaron Bartell
Sent: Tuesday, 2 March 2010 8:26 a.m.
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] html2pdf4i was-->Re: RPGCGI - Convert HTML page to PDF

The devil is usually in the detail of an integration into existing

production that performs well.

So true. This would be much better if a data queue layer were put in front
of it and have it run in a single batch job on the AS400 (which might be
what I end up doing for my customer).

Be warned about running headless java in the same job that may need to load

a PASE routine.

How does java.awt.headless affect anything other than the Java runtime? I
don't know if I have run into the issue you are alluding to.

Aaron Bartell
http://mowyourlawn.com
http://mowyourlawn.com/blog/


On Mon, Mar 1, 2010 at 12:48 PM, Peter Connell <
Peter.Connell@xxxxxxxxxxxxxxxxx> wrote:

Sounds pretty much like the install for the purchased PD4ML product except
images don't need a qualified domain.
Like many things, getting a prototype to run is often straight forward
enough. The devil is usually in the detail of an integration into existing
production that performs well.
Be warned about running headless java in the same job that may need to load
a PASE routine.

Peter