Re: Java and cleanup from exception

[Dieter Bender <dieter.bender@xxxxxxxxxxxx>]

... I don't use this "embedded Java" in RPG at all, I always put one JVM to a 
Batchjob, serving multiple RPG Clients via DataQ.  IMHO this approach has 
multiple advantages:
- no startup punishment
- better scalability, than starting JVMs for many Jobs
- no need to put everything to the system classpath
I have written open Source AppServer4RPG (hosted at SourceForge) it has a RPG 
Part with a procedure  fireEventP, sending a Request with a name and 
Requestdata ro the prestarted JVM. You would have to write a Java 
RequestHandler (for every Request Name).
In the meantime there is a complete application as example available (ArdGate, 
an universal database driver - with this you can access every database with 
embedded SQL)

D*B

Am Mittwoch 01 September 2010 16:19 schrieb Dennis Lovelady:
> For years, I have been writing programs that utilize RPG's interface with
> Java for functions like (especially) creation of spreadsheets, creation of
> charts and the like.  For the same years, I have found that when Java
> errors occur when testing those functions (obviously due to external
> influences like sunspots - not my code! ;) the interactive job is virtually
> useless to Java.  Cannot start a new Java session, and cannot recover the
> old one.
>
> > From my experience, JBAB55C results in any attempt to use Java after a
>
> failure, often accompanied by an amazing number of MCH* errors.
>
>
>
> What do others do to clean up from this so they don't have to sign off and
> back on every time the sun has a mild hiccup?  I'm sure this is something I
> should have addressed all those years ago, but here I am now.
>
>
>
> Dennis E. Lovelady
> AIM/Skype: delovelady      MSN: fastcounter@xxxxxxxxxxxx
>  <http://www.linkedin.com/in/dennislovelady>
> www.linkedin.com/in/dennislovelady --
> "Always do right. This will gratify some people and astonish the rest."
>        - Mark Twain