|
> From: Bramley, Stu > > I'm sorry, that went right over my head (doesn't take much!) - are you > saying that the alternative is to have batch server jobs with their own > JVM > creating 'shared' instances of Java objects and then have client RPG > programs queue processing requests in data queues that the server jobs > read > off and return results/pointers? Exactly! If you need persistence between calls, you'd have to create a session object and then pass an identifier back and forth with each call, but a server job is the only way I know of to force the use of a specific JVM. It would be nice to be able to "attach" to a JVM that was already running anywhere in the system. We've been asking for this forever, but the folks at IBM insist it's too hard to do. Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.