×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
I have had quite a bit of fun trying to get a smallish Java program to
behave decently under the Classic JVM as it is very slow at first
invocation (a lot of classes needing to be initialized) plus after being
left alone for a while, plus - I think - if garbage collection hits
while processing.
We have now essentially done what we within reason can do, and it is
still not satisfactory, so we are now considering switching to the new
J9 one (IBM Technology something). I did some experiments earlier and
we found that the java.library.path property had changed form plus we
had some issues with the native jt400 forgetting we just sent a CHGLIBL
command, which is why we chose to stay on the Classic JVM, especially
since our own development system is V5R3 which doesn't have the new
stuff (upgrade in the horizon, not applicable right now).
Well, that decision may be reversed now. In order to avoid nasty
discoveries up to a deadline I'd really like to hear others experiences
of "interesting" differences or tales like "no problems at all even with
jt400 foobar voodo". I am already aware that adopted authority is not
supported which is ok.
I'd appreciate any help
/Thorbjørn
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
