Re: Java and cleanup from exception

... worst case, the Thread is dead, because it hangs. Other requests are not
touched by this. This Thread will hang (causing this RPG Client to hang)
until the ClientJob ends (then CEE4RAGE) will sent an exit message and the
session is destroyed and the garbage Collector will do the rest. If it would
be a Requirement (just put it to the project page), it would be no problem to
implement a configurable timeout, or a setTimeout(int seconds) procedure.

D*B

Am Mittwoch 01 September 2010 19:17 schrieb Dennis Lovelady:

Oh, I get it. Thanks. So (merging with Scott's evaluation of what I was
trying to stipulate) if I pass a *NULL object reference to a java function,
what happens to the JVM? How are you making that JVM work differently from
the one that's used in an interactive or normal batch job? What happens to
the other jobs that are expecting response from that job?

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"An invasion of armies can be resisted, but not an idea whose time has
come."
-- Victor Hugo

with AppServer4RPG Java and RPG are comletely decoupled.
The RPG Programm uses fireEvent(request) to send a message to a java
EventHandler (this must be written to your needs), in this EventHandler
(its
pure Java) Exceptions are handled and the results are sent back.
AppServer4RPG provides the Context for the EventHandler, manages the
DataQs to
communicate with the rpg clients, provides Multithreading with a
seperate
Thread for every Request and handles a Session Context for persistant
Data
which has to live longer than one Request.


D*B
--
This is the RPG programming on the IBM i / System i (RPG400-L) mailing
list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.