RE: system-wide JVM (threads) Was: Friendly co-existance

On 07/06/2004 at 11:56:32 AM, java400-l-bounces@xxxxxxxxxxxx wrote:
> From: Fred Kulack
> 
> Hmmm....
> Indeed, would be pretty cool.
> But, the usual answer for this type of request would be something like
> "use threads", right?

I'm not sure what you're saying here, Fred.  What I want is to be able
to start an application or call a class from RPG and in either case use
a JVM that is already started.  I would then have access to all the
objects in that JVM (which I could share among jobs through a static
member in a class).
--- end of excerpt ---

I guess what I'm trying to understand is that if you're really stuck on 
the "job" or "application" constructs,
and where does threading sit in relationship to something that might be a 
solution for you?

Would it be sufficient for you to run a new thread (instead of a new job) 
in your existing application,
have it attach itself to the already existing JVM (also in the same job) 
and thereby communicate with 
the already running Java code and objects being used by the "first" 
thread? 
Then, repeat as necessary to some knee in the curve of scaling or 
management graph..

Or is this not really an option in your case because you really have the 
need for multiple JOBs to
do the main work?



"The stuff we call "software" is not like anything that human society 
  is used to thinking about. Software is something like a machine, and 
  something like mathematics, and something like language, and 
  something like thought, and art, and information... 
  but software is not in fact any of those other things."
Bruce Sterling - The Hacker Crackdown

Fred A. Kulack - IBM eServer iSeries - Enterprise Application Solutions
ERP, Java DB2 access, Jdbc, JTA, etc...
IBM in Rochester, MN  (Phone: 507.253.5982   T/L 553-5982)
mailto:kulack/us.ibm.com   Personal: mailto:kulack/magnaspeed.net
AIM Home:FKulack  AIM Work:FKulackWrk 
MSN Work: fakulack/hotmail.com (replace email / with @)