It's all about appropriate use and appropriate JVM choice. (32-bit is my favorite culprit.)

Also kicking off hundreds or thousands of Java commands at once, might cause issues.

Controlling them in a handful of batch job threads not so bad.

Our experiences apparently differ, so just keep doing what works for you in your environment.

Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com

-----------------------------
message: 5
date: Tue, 23 Jan 2018 10:20:23 +1300
from: Evan Harris <auctionitis@xxxxxxxxx>
subject: Re: Java extensions directory vs Excel generation

There's nothing "cup almost empty" about just stating a fact.

I can see how just kicking off multiple separate java instances gets rid of the class path issue, so i have no problem with your solution, but the JVM startup for each of those instances is an expensive and unavoidable side effect.

On Tue, Jan 23, 2018 at 9:37 AM, Richard Schoen < Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Well that would be the cup almost empty way of looking at it.

Don't knock it until you've tried it and actually deployed production
processes with it ?

Or you can.....

Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.