RE: Overhead/downsides to JVM in each job (was: JVM properties -angst)

["Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>]

> When it is likely that the RPG app which employs java classes will be
> called while servicing a web based request then the overhead of JVM
> startup is not necessarily much of an issue where each thread of the
> HTTP server persists to service many requests

Agreed. Whether it's in a app server like websphere, or used server-side
via RPG in a CGI environment the JVM startup is a non-issue.

> For versioning, I set this environment variable at *SYS level
> QIBM_RPG_JAVA_PROPERTIES =  '-Djava.version=1.4;'   

Hmmm... I suppose we could do that, would it be version 1.5 or 5.0? :)

> I would suggest that green screen JVM use is horses for courses.

This is green screen. When a programmer wants to use a specific command
we're calling a remote web-service to open a ticket in Remedy (issue
tracking system) to track the usage request. Since many programmers
could be using this command we decided it was better to centralize the
JVM to one task than have each programmer have a JVM active.

> A simpler design is always easier to implement...

Universal rule of computing!!!! :) But in this case a single background
JVM w/Data Q communication may actually be simpler (and better). 

-Walden

--  
Walden H Leverich III 
Tech Software 
(516) 627-3800 x3051 
WaldenL@xxxxxxxxxxxxxxx 
http://www.TechSoftInc.com
 
Quiquid latine dictum sit altum viditur. 
(Whatever is said in Latin seems profound.)